Looks neat, good!
And I like the phrase "Get Yours Now" on the top page.
Thanks for making it free.
Show HN: zzzz.io, a free DynDNS replacement I created on the weekend
61–70 of 73 posts
Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend
#62A bit confused. Is this for tunneling localhost like ngrok ( https://ngrok.com/ )?
No, localtunnel or ngrok will tunnel a local port (such as for instance 127.0.0.1:80) to a public domain name (alias.ngrok.com). This only redirects an alias to your ip address (alias.zzzz.io -> wan-ip-address). The big difference is when you are inside your local network behind the router, or at work behind a firewall simple accessing the wan-ip won't reach your machine, unless you do port-forwarding (which isn't al…
Ah, OK. Thanks for the explanation. I wish there was some compromise where I could tunnel a local port in such a way that didn't require a server.
Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend
#63"created on the weekend" is not very reassuring. Why would you tout that (if you wanted users vs showing off)?
Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend
#64Earlier quoted context omitted.
[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.
[deleted]
Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend
#65Earlier quoted context omitted.
No, localtunnel or ngrok will tunnel a local port (such as for instance 127.0.0.1:80) to a public domain name (alias.ngrok.com). This only redirects an alias to your ip address (alias.zzzz.io -> wan-ip-address). The big difference is when you are inside your local network behind the router, or at work behind a firewall simple accessing the wan-ip won't reach your machine, unless you do port-forwarding (which isn't al…
Ah, OK. Thanks for the explanation. I wish there was some compromise where I could tunnel a local port in such a way that didn't require a server.
And I didn't even mention how some ISP's block ports below 1024 (thus ssh, ftp and web standard ports cannot be used to accept incoming connections even if you are connected to the WAN or did the port forwarding correctly).
That pretty much is (or was, not sure how most games currently handle networking) the main frustration of setting up a game server at home for your friends at their homes.
One solution back then was to use Hamachi to create a "virtual lan network". Btw for some use-cases you could even use "ssh -L :: @" with a server, and certainly nowadays you can get a vps at 12$/year (nothing fancy, but good enough for tunnelling ports).
Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend
#66Earlier quoted context omitted.
IPv6 mobile address portability attempts to keep your IPv6 address constant as you move around different wireless access points or LANs within a company or ISP network. It doesn't provide a globally static address or way to provide a static hostname. Even with a static or mostly static IPv6 address the ability to have a dual stack dynamic hostname where both the v4 (that changes a lot) and the v6 (which might change…
Mobile IP in IPv6 is very much meant to keep your stable, global address working while you roam around the global Internet. The route optimization mechanism means your packets can travel directly between the mobile node's care-of address and the other guy if they both support MIP, so no need to be even on the same continent. Sadly MIP is mostly dead, though there seems to be a somewhat up to date (2013) Linux impl of…
those of us championing LISP are definitely working on it.
Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend
#67this related to or based on http://www.hopper.pw ?
Nope
Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend
#68Perhaps 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 :)
I'm afraid pagekite addresses a different problem to zzzz.
Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend
#69"created on the weekend" is not very reassuring. Why would you tout that (if you wanted users vs showing off)?
I don't want to sound off-hand, but - what are you worried about?
The application is basically a thin layer in front of AWS's Route 53. All user data is stored safely and securely.
Are you just as suspicious of popular applications that sprang up from hackdays?
Re: Show HN: zzzz.io, a free DynDNS replacement I created on the weekend
#70Will you ban a client if it posts updates on a regular cycle? I got banned from dyndns because I wrote my own client and put it into cron. (I think it's actually smart they banned me, since it was a huge waste of time to update with no new info)
I'll be keeping an eye on logs and AWS expenditure to see if this becomes a problem. :)
I'm not one to jump to the nuclear option of banning clients outright - if I notice behaviour that's harmful and needs to be corrected, I'll email the individuals concerned and talk them through how to use the service more efficiently, while also improving my own documentation on the website (which I admit isn't as thorough as I'd like).