Solved

Help needed with DNS conditional forwarders

Posted on 2011-09-21
7
2,016 Views
Last Modified: 2012-05-12
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
Comment
Question by:Network_Padawan
  • 5
7 Comments
 
LVL 21

Expert Comment

by:Papertrip
ID: 36577953
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
 

Author Comment

by:Network_Padawan
ID: 36578143
yes i can telnet port 53 on that server
0
 

Author Comment

by:Network_Padawan
ID: 36578198
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
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 7

Expert Comment

by:Dusan_Bajic
ID: 36579105
Check if DNS server in target domain has zone source.local (or whatever source domain name is) in its Forward lookup zones.
0
 

Author Comment

by:Network_Padawan
ID: 36584298
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
 

Accepted Solution

by:
Network_Padawan earned 0 total points
ID: 36585125
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
 

Author Closing Comment

by:Network_Padawan
ID: 36708163
Adding to knowledge base as this took me 3 days to resolve. Im sure others will come across this also.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
This script can help you clean up your user profile database by comparing profiles to Active Directory users in a particular OU, and removing the profiles that don't match.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

778 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question