Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

zzzz.io

Post reply on HN
Print view View original

41–50 of 73 posts

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

#41

Post by annnnd »

toni wrote: post #38
reflexing wrote: post #36

Earlier quoted context omitted.

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/

What does "not accessed" mean? One could write a script that would log in every month or so, click around (very carefully of course ;) ) and logout. How would they know the difference?

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

#42

Post by zrail »

stevekemp wrote: post #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…

Have you seen LuaDNS? It sounds sort of what you're talking about, and they let you set up vanity servers if you want.

http://www.luadns.com/

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

#46

Post by stevekemp »

zrail wrote: post #42
stevekemp wrote: post #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…

Have you seen LuaDNS? It sounds sort of what you're talking about, and they let you set up vanity servers if you want. http://www.luadns.com/

Yes I looked at several companies looking to see who I could use as a back-end, LuaDNS jumped out because I've an interest in Lua, but it seemed more like they'd be a competitor than a back-end provider.

That said I think I pretty much shelved the idea when I considered how hard it would be to get paying customers.

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

#47

Post by [deleted] »

kopf wrote: post #20
nmc wrote: post #14

> DynDNS replacement I would disagree. This may look like a replacement from the end-user's point of view, but 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. Either you are just proxying someone else's service, or you are running your own on (supposedly) limited resources. Am I wrong? Moreover, I heard from DynDNS…

> 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…

[deleted]

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

#48

Post by kbar13 »

[deleted] wrote: post #47
kopf wrote: 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…

[deleted]

security vulns are not in and of itself (themselves?) indicative of the usability/quality of the software.

If someone were to finger all the nameservers in the world, I would bet that BIND has a large user share.

A good alternative is NSD from the team that also makes unbound.

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

#49

Post by laumars »

kopf wrote: post #20
nmc wrote: post #14

> DynDNS replacement I would disagree. This may look like a replacement from the end-user's point of view, but 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. Either you are just proxying someone else's service, or you are running your own on (supposedly) limited resources. Am I wrong? Moreover, I heard from DynDNS…

> 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…

Nice resource. Just last month I set up Bind9 on a spare VM for the same reasons (albeit just for personal use).

Is this project something you'd consider releasing the source code for (obviously I'm happy to write my own code if needs be but there's no point in me reinventing the wheel if you already have this sitting on a public git repo)

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

#50

Post by toni »

annnnd wrote: post #41
toni wrote: post #38

Earlier quoted context omitted.

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/

What does "not accessed" mean? One could write a script that would log in every month or so, click around (very carefully of course ;) ) and logout. How would they know the difference?

As a matter of fact, that's what I was doing to bypass DynDNS limitations: running a PhantomJS script via cron once every week to login, click around and logout. But it is a tiny hassle anyway. Much better to stick around with a service that does not have these annoyances.
Post reply on HN