Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2163
  • Last Modified:

Help needed with DNS conditional forwarders

I have two domains in which I am going to migrate some users across from source to target domain.

The trust doesnt work two-way because of a DNS issue with the target being able to resolve to the source domain.

From the source, I can ping all servers on the forwarded domain via server name. But I cant do the same from the target to the source.

Source domain is windows 2008 environment, domain and functional level both 2003 (cant upgrade)

Target domain is windows 2008 R2, domain and functional level bothh 2008 R2.

Target can ping source via IP. No problem with connectivity.

I add the domain.local to the conditional forwarder, enter the address 192.168.0.3 (and yes that server can ping that IP) but it cant resolve it, wont validate. Dont know how to fix this!

If I enter a host file, works perfect.

Can someone please steer me in the right direction? Doesn't make sense to me why the conditional forwarder can not validate the domain controller in the source domain.
0
Network_Padawan
Asked:
Network_Padawan
  • 5
1 Solution
 
PapertripCommented:
Target can ping source via IP. No problem with connectivity.
Is that the only connectivity test you did?  Did you try to telnet to port 53?
0
 
Network_PadawanAuthor Commented:
yes i can telnet port 53 on that server
0
 
Network_PadawanAuthor Commented:
when i run dcdiag /fix, i get the following errors

Dynamic registration or deletion of one or more DNS records associated with DNS domain 'au.nepean.internal'. failed. These records are used by other computers to locate this server as a domain controller or as an Ldap server.

Name resolution for the name _VLMCS._TCP timed out after none of the configured DNS servers responded.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
Dusan_BajicCommented:
Check if DNS server in target domain has zone source.local (or whatever source domain name is) in its Forward lookup zones.
0
 
Network_PadawanAuthor Commented:
Hey, okay ive narrowed it down to a windows 2008 R2 issue or the server network card issue. I hooked up my windows 7 laptop to the network (the same one the R2 server is on) and by placing the domain.local dns server details on my card, I can resolve all servers on domain.local.

Cant do this for the two R2 servers on the network.

Is there a bug somewhere on r2? Could it be sending malformed packets?
0
 
Network_PadawanAuthor Commented:
Okay figured it out. The DC's were VM's on VMworkstation. Converted them across to an ESXi 4.1 Host and it worked all of a sudden, no other reason.

Seems to have been a network bug with Vm workstation.

Resolved.
0
 
Network_PadawanAuthor Commented:
Adding to knowledge base as this took me 3 days to resolve. Im sure others will come across this also.
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

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