I have servers named like server.prod.example.com, and I regularly log into them as server.prod. Recently, these hostnames started resolving to 127.0.53.53.
It turns out that ICANN recently enabled the .prod TLD. In addition, every request that goes to the .prod nameservers get resolved to 127.0.53.53 instead of coming back as NXDOMAIN, which would allow resolution to continue to work properly. (I'm guessing the point behind this is to let people know that their stuff will break worse before those start resolving to something real.)
How can I avoid having to type in my domain name for every host like this?
Is this still biting you occasionally? I couldn't find a list of new TLDs and when they were added, so I set one up myself: https://twitter.com/newgtldannounce
Best Answer
When you see internal domains suddenly resolve to
127.0.53.53you have a namecollision and ICANN is trying to tell you that you urgently need to fix your DNS configuration.If it would return NXDOMAIN like you suggested, you are correct, it would continue to work - for now.
It would also leak your internally intended DNS query to outside parties.
Worse, in the future someone could register
server.prodand cause you much more trouble.See here for more information https://icann.org/namecollision or run:
As to how to resolve this: Depends on the use case, I probably would just add them to
.ssh/configwith the short names. Or start using the FQDNs really.