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.
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.
make sure the computer you are using that is doing the nslookup has both DNS servers configured in the tcp/ip properties.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@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
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
"...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.
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?
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.