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.
Network_PadawanAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Network_PadawanConnect With a Mentor Author 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
 
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
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
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
 
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:
Adding to knowledge base as this took me 3 days to resolve. Im sure others will come across this also.
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.