• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 370
  • Last Modified:

DNS name resolution issue

I have two DNS server, is also a global catalog server both in different forest, so
DC1 = FOREST 1, domain name = domain-1.com
DC2 = FOREST 2, domain name = domain-2.com
I have a primary AD integrated zone for domain-1.com in DC1 &
I have a primary AD integrated zone for domain-2.com in DC2
I added domain-1.com as secondary zone in DC2 &
I added domain-2.com as secondary zone in DC1

I have one host A record called “me >” in domain-1.com
My WS is residing in domain-2.com when I try to resolve – nslookup me ; I don’t get IP associated with it.

How can I make this configuration work so I am able to resovle the name to IP and IP to name using the secondary dns.
3 Solutions
make sure the computer you are using that is doing the nslookup has both DNS servers configured in the tcp/ip properties.
dmf415, he doesn't need both DNS servers configured if he has both zones on both servers (excepting of course that it's good to have redundancy)

Try pinging "me.domain-1.com" instead of just pinging "me"

If that works, configure the DNS suffix search order on the client to domain-2.com, domain-1.com.

You will then be able to ping "me" without the suffix.

Also, to resolve IP to name, you will need a reverse DNS zone for the address space.

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Jeremy WeisingerSenior Network Consultant / EngineerCommented:
Draxonic is correct. You'll need to setup the DNS suffix search list on all the computers. You can do this through group policy. http://technet.microsoft.com/en-us/library/bb847901.aspx

The problem here is that you are trying to look up a DNS record for 'me.domain-1.com' by typing 'me'
When resolving individual names/addresses, the system automatically ads the correct domain name to the end of it to create a FQDN.

As you are performing the lookup on the DNS server that looks after the domain 'domain-2-com' you are effectively looking for a record called 'me.domain-2.com' which doesn't exist, instead of me.domain-1.com

Either add the secondary DNS suffix as advised above or add a DNS record for me to the domain-2.com DNS and point it to the IP of me.domain-1.com
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
"...or add a DNS record for me to the domain-2.com DNS and point it to the IP of me.domain-1.com"

I wouldn't recommend doing this for two reasons:
1) The administrative overhead of manually creating DNS records for all computers in the other domain and there would be the potential for confusion as to where the computer is administered

2) Computer names would need to be unique across both domains and thus also increasing the administrative burden.
immipathan, were we able to answer your question?
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now