DNS Dilenma

[Dan]

Sorry for the crosspost ... our servers are 2000, not
2003 ...

Situation

MyCompany.com named their AD MyCompany.com

The problem is when users locally want to browse
MyCompany.com, AD and DNS spins in circles amongst the DCs
and it does not resolve locally for users on the LAN.

Any suggestions?

 

[Kevin D. Goodknecht [MVP]]

In

Sorry for the crosspost ... our servers are 2000, not
2003 ...

Situation

MyCompany.com named their AD MyCompany.com

The problem is when users locally want to browse
MyCompany.com, AD and DNS spins in circles amongst the DCs
and it does not resolve locally for users on the LAN.

Any suggestions?

Can the site be accessed by www.mycompany.com?

I took this from a post earlier this week.
This is probably the second most asked question in this group. Internally
whatever.com must resolve to the IP addresses of domain controllers that
have File Sharing enabled.
You can set up a site in IIS on your DCs for whatever.com and have IIS
redirect the request to www.whatever.com that is the best you can do.
Changing the behavior of DNS to give out IP addresses of the website instead
of DCs will cause GPOs
to fail and replication errors because they will be looking to the webserver
for the SYSVOL DFS share at \\whatever.com\SYSVOL