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 > 10.240.42.110” 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.
LVL 1
immipathanAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
DraxonicConnect With a Mentor Commented:
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.


0
 
dmf415Commented:
make sure the computer you are using that is doing the nslookup has both DNS servers configured in the tcp/ip properties.
0
 
DraxonicConnect With a Mentor Commented:
Also, to resolve IP to name, you will need a reverse DNS zone for the address space.

http://support.microsoft.com/kb/323445
0
NEW Internet Security Report Now Available!

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out this quarters report on the threats that shook the industry in Q4 2017.

 
Jeremy WeisingerConnect With a Mentor Senior 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
0
 
SteveCommented:
@immipathan

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
0
 
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.
0
 
DraxonicCommented:
immipathan, were we able to answer your question?
0
 
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.
0
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.

All Courses

From novice to tech pro — start learning today.