4 ms·
Just use home.arpa from https://tools.ietf.org/html/rfc8375 https://tools.ietf.org/html/rfc8375 with a custom DNS server or host file. Or one of the many dynami
by gbrayut 8y ago
Just use home.arpa from https://tools.ietf.org/html/rfc8375 https://tools.ietf.org/html/rfc8375 with a custom DNS server or host file. Or one of the many dynamic DNS systems.
- Aeolun 8y agoSure, because a custom DNS server is easy to set up.
- icedchai 8y agoIt's actually pretty easy. I was able to set one up when I was a teenager, almost 25 years ago, in the early days of the commercial Internet. It is even simpler now.
- ivlad 8y agoYes, it is.
- justinclift 8y agoDepends on your skill set. If you're ok with *nix, then PowerDNS is pretty simple to work with: https://github.com/PowerDNS/pdns https://github.com/PowerDNS/pdns It's also fairly complete, used in production by some pretty big ISPs. For a light weight approach instead, Dnsmasq is good: http://www.thekelleys.org.uk/dnsmasq/doc.html http://www.thekelleys.org.uk/dnsmasq/doc.html It's what most home routers (and lots of other stuff) embed. :)
- Aeolun 8y agoOk, fair enough. It’s fairly simple to set up. It’s just a bit of a pain to maintain if the only thing you care about is connecting to server nr 192.168.0.x I could certainly do it, but there’s 5 services in my house I’d care to connect to, and remembering 1-5 is just as easy as giving them all names. The marginal gains are very low.
- justinclift 8y agoOh, I very much agree. For very small local networks in a flat address space, manually remembering stuff works ok. Personally I tend to throw the more stable IP addresses in /etc/hosts, as that's simple too. :)
- vetinari 8y agoEver heard of dnsmasq? Comes with many home routers. Puts a dns entry for each host that gets it's ip address via dhcp, plus your static mappings.