Perhaps I'm missing something, but what exactly is appealing about this service and/or is new and innovative? It's trivial enough to put a web interface in front of BIND or djbdns to replicate this behavior to where I'm trying to understand why this got ranked highly? I am by no means bashing the creator of this service nor the service itself - I'd just like to understand what additional value is being provided here that does not already exist?
That's pretty interesting. Somewhat like DDNS, but not as useful?<p>I don't know if I want an ipq.co address, but I just realized - could I use my own DNS hosting (through slicehost, linode, whatever) to assign domain names to arbitrary IP addresses?<p>Like, if I own garlicgargle.com, and I have another system with a static IP, does that mean I can just assign salty.garlicgargle.com to that IP and it works fine? Sorry for the basic question, I guess I don't understand doing much with DNS beyond the common tasks.
I am not sure how I feel about this. A domain name implies ownership of the site.<p>It's kind of like reverse domain hijacking.<p>See,
<a href="http://hackernews.ipq.co/" rel="nofollow">http://hackernews.ipq.co/</a><p>Am I missing something?
I get an error when trying to create a record with an email address - "doesn't look like an email address".<p>Tried it with an ISP email address, and a gmail address.
I'm not really sure what I would use this for. It's nice to have DNS for a box at home, but those aren't usually on a static IP. If my IP is dynamic, I'd probably go with a service like DynDNS which keeps my DNS record updated as the IP address changes.
I can dig it. It's useful when tossing up a web server on a cloud host that assigns an ugly external host name and I'd rather address it by a cleaner host name.