Putting 192.168 addresses in public DNS
On my home LAN I have a dozen or so PCs, servers, and VMs. I use a domain for all my home stuff and rather than setting up DNS at home, it occurred to me I could just put A records with 192.168.* records in my registrar's DNS.
So if I look up tentaclehentaiserver.mydomain.com it would come back as 192.168.1.15. Obviously, you can't get to it unless you're on my LAN.
It seems weird but I am having a hard time thinking of a downside. Running my own DNS at home isn't hard but then I have to make it redundant, etc. and set it up as a recursive server since I'd have to point clients at it. Right now I'm just copying a host file around, and sometimes when a family member wants to go to our home web server they have to type in the IP address or edit their local hosts, etc.
The only exposure I can think of is that if someone managed to do a zone transfer, they'd have a list of all the servers in my house, though my registrar's DNS doesn't allow zone transfers.
I'm sure RFC1918 entries weren't necessarily meant to be in public DNS but...what does it really hurt?
For LET support, please visit the interim support desk.
Over the past few months we have been met with many challenges within the moderation business. Some that have not been overcome.