I am aware that best practices currently dictate that my Windows AD Domain name should be a subdomain of a purchased, globally unique namespace (ie ad.namespace.com). That's just fine and dandy.
My question is, what are the potential security vulnerabilities introduced if our public domain registration lapsed and someone squatted the domain name out from under us (bad guys now own namespace.com)? Could they leverage some DNS voodoo to compromise our internal network back at ad.namespace.com? Could an uninformed end-user be tricked into doing something they shouldn't or leaking sensitive private domain info by visiting a malicious website occupying our squatted web address? Is there any remote AD authentication vulnerability resulting from bad guys owning our root level domain name?
I will probably earn ire for saying it, but it just seems safer to have the private AD domain occupy a separate namespace that is inaccessible from the internet, like whatever.local. I know this is hated. Someone please put my mind at ease. I have sent a few days trying to research this question, but I can't find anyone else sharing my concern about the potential compromise of a root level domain name. Maybe I'm just being nuubi. Thanks in advance.