New Domain in a new Forest and DNS 1

[astaylor]

I have added a new domain in a new forest. I would like to be able to get to servers in another domain on our LAN. i assume i'm having a dns issue because i can ping those servers by IP but not by name. So far all i have done is dcpromo the server with active directory integrated dns. I would like to be able to get to servers on the other domain by name, so what should i do to solve this. The new server is sitting in a different subnet, just fyi.

Thanks,


-drew

 

[lhuegele]

If the different domains have their own DNS servers, what you should do is make sure that you create secondary zones on each other's DNS servers so that any changes to one DNS server is reflected in the other DNS server.

Good luck,

 

[astaylor]

hmmm, is it possible to do this without touching the domain that is already in place (in production). This new domain that i created is primarily for testing.

-drew

 

[nevets2001uk]

On your testing domain you could perhaps place a forwarder in DNS to the DNS Server of the production domain? This will forward any unknown DNS lookups to that server which will be able to resolve them.

Steve G (MCSE / MCSA:Messaging)

 

[astaylor]

Steve,

I am not that familiar with dns. Do you mean add a forward lookup zone? or just a forwarding setting somewhere?

Thanks,

-drew

 

[nevets2001uk]

This Microsoft link has the basic steps outlined...

http://technet2.microsoft.com/windowsserver/en/library/d2b0bb80-0eb8-40a3-8454-6e683403c36f1033.mspx

Steve G (MCSE / MCSA:Messaging)

 

[astaylor]

I added the forwarder but still not working. I can still ping by ip but not by name. I can however ping by "computername.domainname.com". I know there is a way to append the domain suffix to names within an xp machine or a member server, but how can this be done on an domain controller.

-drew

 

[nevets2001uk]

I must confess I thought the forwarder would work as I'm sure I did something similar in my VPC environment a while ago to get DNS working. I haven't messed around with suffixing before but I think you can set up suffixing in the same place as on an XP box.

Two other suggestions... Firstly you could take a look at using nslookup in the command line to test if your DNS server is configured correctly and returning the correct results from your queries.

As a backup you could consider adding the IP and HOSTNAMES to the hosts file located in WINDOWS\SYSTEM32\Drivers\Etc folder (for each DC / Server in the test environment), which will work as a temporary measure. It's only suitable if you are wanting to contact a small number of servers and workstations in the production network, otherwise it's a big manual job.

Steve G (MCSE / MCSA:Messaging)

 

[astaylor]

The hosts file did the trick! It will work for my test environment just fine, but i agree that would not work on a large scale level. Thanks for your help.

-drew