My company's internal domain name is structured like this:
The company's website, which is hosted by a third party, is structured like this:
This generates a bunch of port 137 Netbios and 445 Microsoft DS traffic from the workstations to the third party website host (mail is also hosted externally). I don't see where performance is being harmed, but I block that traffic at the firewall for security reasons and because it is useless. I think if the mail and website were ever hosted internally, the current naming structure would make sense, but should the internal domain name be named something different as a best practice in our current scenario? I know it would stop the 137/445 traffic to the webhost anyway!