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

DNS resolution Problem from hosts of one forest to another


There are 2 AD configured separately in different forest. I need users authenticated using 1 AD to be able to resolve DNS through AD 2  which are containing separate entries. AD1 and AD2 are able to resolved there DNS but not there hosts.
0
oppofwar
Asked:
oppofwar
  • 4
  • 3
  • 2
1 Solution
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
what happens if you ping full hsot name?

ping hostname.domain.com

?

probably your domains have no information in DNS suffix order. Create a GPO in each domain and define FQDN list for those domains.

In the first add

domain1.com (its domain)
domain2.com (remote domain)

in the second domain add

domain2.com (its domain)
domain1.com (remote domain)

Regards,
Krzysztof

0
 
oppofwarAuthor Commented:
I have entred the DNS entry in Forwarders , AD server is able to resolve to one another  But the Domain members are not able to resolve it
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
KenMcFCommented:
iSiek, is correct. After reading your question agian it sounds like you are having problems with shortname resolution. Adding a domain suffix to your computers will fix this and using a GPO is the easiest way..
0
 
oppofwarAuthor Commented:
Isiek they are not able to resolve using FQDN also
0
 
KenMcFCommented:
If they are not able to resolve FQDN then the conditional forwarders should have fixed that. Are you running 2003 or 2008 for your DNS servers? If 2003 you will need to add them on each server unless you add them to the application partition.
Is there a firewall between the servers?
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
Check Ken's suggestion and additionally type in command-line

nslookup hostnameDomainA.fqdn
nslookup hostnameDomainB.fqdn

and check if DNS server resolved those names.

Krzysztof
0
 
oppofwarAuthor Commented:
The problem has been resolved . There was a need for creation of stub zone.
0
 
oppofwarAuthor Commented:
On both  server DNS Stub zone was created for DNS resolution .
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.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now