Live data from Hacker News

Show HN: zzzz.io, a free DynDNS replacement I created on the weekend

zzzz.io

31–40 of 73 posts

Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend

#31
post #20

Earlier quoted context omitted.

> it does not address the real issues of DNS management: space to store all zone data, bandwidth to support requests flow, resources to handle the load. You're absolutely right! However, as you said, it solves the user's problem from their point of view. The main reason I started this project was that other dyndns alternatives (whether they be proxies or "fully-fledged" operations) have rather ugly domain names, in m…

You could've used FreeDNS (freedns.afraid.org) with your own domain. They do this for years.

Doesn't FreeDNS deactivate your account if you don't log into their website for a couple of months, just like DynDNS did?

Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend

#32
Looks good.

I've been pondering git-dns.io for a while - storing DNS in git and using hooks to trigger rebuilds. Unfortunately most of the DNS resellers are expensive, and using Amazon means your hosted domains get given "random nameservers", which complicates the setup for somebody importing lots of domains.

I'd love to be able to say "Use a/b/c.git-dns.io" for the nameservers, but all the resellers of DNS make you pay a lot of cash up-front for vanity nameservers, which I think would make the thing unprofitable.

(Running bind/tinydns on three toy virtual machines around the world would work - but DNS-servers are traditionally a DoS magnet, so I know I'd get taken down sooner or later if I went down that path.)

Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend

#34
For anyone looking into free DynDNS alternatives: I have tested several of the established alternatives without success. I then looked into some of the newcomers and ended up choosing http://duckdns.org. The setup was super easy and the service has been absolutely reliable so far.

Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend

#35

Personally I use CloudFlare's API to achieve the same, using a small sh-script that I run in cron: https://gist.github.com/larrybolt/6295160

I also did a similar one in Python for duckdns.org: https://gist.github.com/shaunpud/0d72f2d23a4ddd0fbab6

Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend

#36
post #31

Earlier quoted context omitted.

You could've used FreeDNS (freedns.afraid.org) with your own domain. They do this for years.

Doesn't FreeDNS deactivate your account if you don't log into their website for a couple of months, just like DynDNS did?

No, it's Dyn's and No-IP's thing.

Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend

#38
post #31

Earlier quoted context omitted.

Doesn't FreeDNS deactivate your account if you don't log into their website for a couple of months, just like DynDNS did?

No, it's Dyn's and No-IP's thing.

From FreeDNS news page[1]:

"2012-03-29 18:20:33, 2 years ago: Free accounts not accessed at least once every 6 months will be considered dormant and unloaded from memory."

What does "dormant" mean here? Do they delete your DNS records? It might not be as draconian as what DynDNS was doing, but certainly a barrier you should consider.

[1]: http://freedns.afraid.org/news/

Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend

#40
Perhaps an alternative is pagekite ( https://pagekite.net/ ) an opensource (Python) tunneling service. It's also more avanced then this one.

And yes, it can modify your localhost:9999 to mydomain:80. Why is that usefull? My ISP blocks ports upto 8999, so i wouldn't run a webserver / ftp / smtp / ... without paying extra for unlocking those ports :)

Post reply on HN