Domain Controller/Webpage conflict

[Maria Maniaci]

Hope someone can help...

I have set up a W2K file server to administer a brand new
domain. The actual server machine's name is (for the sake
or arguement) "football.warriors.wayne.edu". However the
name of the *domain* the server controls is
simply "warriors.wayne.edu."

Our network runs on dhcp. I added a few test machines to
the new domain, putting the ip address of the new server
in as the primary dns entry on the test machines, and
using one of the campus' dns servers as the secondary
entry under dns.

The department has a webpage hosted on an entirely
seperate machine across campus which is mapped to the
name "www.warriors.wayne.edu."

All is well, the test machines can see the server, access
active directory, etc, with one glitch. Apparently there
is a conflict between having the domain
names "warriors.wayne.edu," and having a webpage
named "www.warriors.wayne.edu," because the test machines
can reach any page on the internet *except* our webpage.

Any ideas for resolving this short or redoing the server
and renaming the domain?

 

[Steven L Umbach]

Add a static entry to your Active Directory dns server for your
www.warriors.wayne.edu server. As far as your Active Directory clients are concerned
your AD dns is authoritative for the warriors.wayne.edu and if the www address is not
found there, the name resolution process stops. --- Steve

http://www.microsoft.com/serviceproviders/whitepapers/split_dns.asp