Windows Forum

Ask something
Discussion Locked

DNS Configuration

0 helpful
6 replies

by richard

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have recently started migrating our NT Domain to Windows 2000 Active Directory. Before Windows 2000 we did not run a DNS server on our internal network depending on WINS for network resolution and external DNS for Internet resolution. Our website hosting is outsourced and when we set up the AD/DNS on our internal network we selected the same domain name that is used externally for our website. Now that the AD and DNS environment has been set up we are unable to resolve the website by namefrom the internal network. If we enter the IP address it comes up immediately. Is this an inherent problem with using the same domain name for our internal network or is there a simple configuration change that will resolve this problem? Thanks.

6 replies

by timwalsh

In your DNS, enter a new host record for your web server. Assuming your URL is something like www.yourdomain.com, enter the host name as www and eneter the IP address of the web server.

Hope this helps.

by avswamy

ms says that while creating a internal domain it shouldn't be the same as external domain u have to add a prefix to it the create a internal domain eg:corp.domain.com, nothing wrong with other things.

for remaining things, is it only server in urnetwork then r u network is created a private or given all public ip, if u required i can design for ur network send me the details.

by thewulfe

The problem with using the same internal and external domain name is the duplication of records. All records that are created externally have to be created internally. The reason why is because when an internal client queries for any yourcompanyname.com resource it is first sent to the internal dns server.

Since the internal DNS server is authoritative for the yourcompanyname.com zone it responds based on whatever records it has, it will not forward the query.

Hope that helps

by richard

We have configured forwarders to handle the issue you describe. If the domain query is not resolved internally then the request is sent to the external DNS servers. As you said, the internal DNS is authorative for mycompany.com. The previous recommendation of adding a new host record with the web IP resolved the issue.

This discussion is closed to new replies.