Link to home
Start Free TrialLog in
Avatar of dshaney
dshaney

asked on

Should my company's internal domain be renamed?

My company's internal domain name is structured like this:

internal.company.com

The company's website, which is hosted by a third party, is structured like this:

company.com

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!

Thanks
SOLUTION
Avatar of Ernie Beek
Ernie Beek
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial