Site VPN DNS Issues

[gregarican]

I already have one site-to-site VPN between our site (siteA.local) and another (siteB.local). Everything works fine. I have an AD trust, DNS resolution, etc. Now I added a site-to-site VPN between our site (siteA.local) and a different site (siteC.local). Here's the rub:

I can resolve DNS to reach to siteC.local from our site. For example, if I ping siteCBox.siteC.local from siteA.local everything is fine. But the reverse isn't true. When I remote into siteC.local and try to ping something like siteABox.siteA.local it appears as if siteC.local is appended their DNS suffix to the ping attempt. So my test is looking to resolve DNS for siteABox.siteA.local.siteC.local, which obviously fails:

I added DNS forwarding on siteC.local's DNS Server so that any attempts to resolve DNS for siteA.local will look to siteA.local's DNS server. But still no luck. This DNS forwarding worked for siteA.local to siteB.local, for siteB.local to siteA.local, and for siteA.local to siteC.local. But siteC.local isn't honoring this. I went in and checked the Advanced TCP/IP properties for DNS on the siteC.local DNS server and tried adding DNS suffix searching for siteA.local. Still no luck.

Any suggestions? I can't add the trusted domains between siteA.local and siteC.local since siteC.local can't resolve DNS correctly. I mirrored the DNS setup like siteA.local and siteB.local, which work. Can't seem to tackle this one :-(

 

[gregarican]

Please disregard. Looking at the setup at siteC.local they had local DNS running but the DNS server didn't have itself listed as a DNS server in its TCP/IP Networking properties for DNS. I added itself as the first DNS server then the Internet DNS servers as secondaries, flushed the cache and we appear to be good to go!