ping to name not working in one domain

[Aek]

We arer having name resolution issues in our DR site.

We have Root Domain - ROOT.COM
We have Site A Domain - SiteA.Root.com
We have a DR Site B - SiteB.Root.com

If I am on Domain Controller in Site A
and run a ping <servername>, ping -a <IP> both work fine. Names of server resolves fine, I can ping by name, IP; all is fine in Domain A.

Issue: But, when I am on Domain Controller in Site B Domain (DR site) and run:
- ping <Servername> (does not work)
- ping <IP Address> (works fine)
- ping -a <IP Address> (returns IP, not name of server)

What am I missing in my DR Site?? How do I resolve this?
Not sure if it helps, but there also seems to be a lag/ slowness in the DR domain.

 

[Aek]

Additional info:

On the Site B Domain Controller, I can ping itself by name, I can ping other DCs by name, it appears there are 2 WINS Servers in the domain (I know they are Wins servers because they are included in DNS entries for WINS Lookup), these 2 servers cannot be ping-ed by name, and also ping -a <IP> does not return the name of those servers.

 

[ITPangaeaArchitect]

What OS (one each side)?

Are you running secondary zones or forwarders?

-Brandon Wilson
MCSE:Security00/03
MCSA:Messaging00
MCSA:Security03
A+

 

[Aek]

forwarders
AD integrated zones

I ran a dcdiag /test: connectivity on the domain controller in DomainB and the RPC test to "ping via IP failed" in pinging the DCs in Domain B, but it could ping all other DCs in Domain A fine.

Something is not right in DomainB configuration or the DC configurations in Domain B.

netdiag /testNS did not show any errors.

 

[ITPangaeaArchitect]

Ok is this one forest (parent/child), or is it two dissimilar domains in separate trees?

-Brandon Wilson
MCSE:Security00/03
MCSA:Messaging00
MCSA:Security03
A+

 

[Aek]

one forest: primary domain - domaina.com
- 2 tree domains:
siteA.domaina.com SiteB.domaina.com

The thing is that SiteB is actually a DR domain. Not sure why that was created because the org could just have put 2-3 DCs i nthe Dr site, and that would have taken care of the DR issues, but by design they have a new domair for DR and there is something not right in the name resolution in that domain. Slowness, cannot ping, RDP by name etc.

 

[ITPangaeaArchitect]

Ok I gotcha. So first things first...forget anything youve read about how Windows 2003 fixes the DNS islanding issues for DCs that existed in Windows 2000 when they pointed to themselves....either way it goes, the "DNS island prevention" configuration across your enterprise will also help to constrain replication topology and name resolution traffic across any WAN connections you may have...plus, the fix only applies to when the server is already up and running, and doesnt really apply to reboots of the DCs, which can cause a system startup to go reeeeeal slow if the services dont start in a specific order....

I am going to assume there are at least 2 DCs per domain in my explanations (btw, I do have an in-depth FAQ on this site we're on for how to properly configure DNS for AD and DCs...ok let me rephrase that, I just hunted for the link and apparently it was removed at some point and I wasn't notified). I created it under my last screen name of ADGod on here (same account, I just renamed it to my current screen name) if you want to try searching for it...

Actually before we really go into a long explanation of any type to work out and config issues, I need to find out whther or not your zones are being hosted in ForestDnsZones (aka, hosted on the forest root DCs, and sub-domain delegated to child domain DCs)....or if the zones are replicated only within the local domain and are owned by the DCs of the specific domain (aka, DomainDnsZones)

Knowing this will help me in pre-emptively deciding if we are dealing with a configuration issue, or an actual problem to troubleshoot within DNS itself...



-Brandon Wilson
MCSE:Security00/03
MCSA:Messaging00
MCSA:Security03
A+

 

[Aek]

Thanks for the reply.

Sory for the naivity, but since I did not design or setup the domain structure, what am I looking for here?

Do I need to check something in the DNS management console on the forest DCs and the child domain DCs in both the sites?

I guess I am lost on "is my zone hosted on the forestdnszones"

 

[ITPangaeaArchitect]

do a query through ldp, adsi script, or adsiedit.msc against "CN=ForestDnsZones,DC=domain,DC=com" and against "CN=DomainDnsZones,DC=domain,DC=com"
See which one has records in it.

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (

http://it-pangaea.com)