Google has received approval for the .prod gTLDThis news is probably a few months old now, but I wasn't paying attention to these things and only just now tracked down a corner case mystery surrounding IP address 127.0.53.53.
Basically, if you are a small company with internal-only DNS names that end in .prod, you need to assign someone to look into this
right now. It might not be too late to complain if this is going to be painful.
For example, you might have an internal DNS that resolves names like "www.prod" to an inside-the-VPN IP address for the production network and "www.beta" or "www.dev" to an inside-the-VPN IP address for the dev network. When the .prod gTLD goes live, how does that affect you?
To be fair, if you're going to have serious problems the instant .prod goes live as a gTLD, you're probably already seeing them as "anyarbitraryname.prod" resolves to 127.0.53.53, and will until at least some time in December.
However, do people in your company automatically assume that any .prod name is an internal IP? Do you think they could be fooled by an email that said "Hey, I ported over a fun internal thing we used to have at Google; check out
http://memegen.prod/ -- It uses your LDAP username/password for authentication."? Because when the new gTLD goes live, suddenly .prod will no longer mean "inside your company"; it'll mean "inside the company for certain specific names, but generally whatever someone buying a DNS name from Google wants it to mean."