Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

Reverse DNS not forwarded?

$
0
0

Hi!

In our Active Directory there are of course DNS Servers (currently three, to be exact). These resolve forward and reverse just fine for our internal domain.

I added a few conditional and general forward DNS servers, but it seems to not work correctly:

We are connected to the Internet via cable and to a bigger datacenter via direct connection. We use stuff from the Internet and from this datacenter. I added Googles public DNS server 8.8.8.8 and 8.8.4.4 as the first two into the general forward list and added the DNS servers of the connected datacenter on the third and following positions. I also added some forward lookup zones for the domains of that datacenter to forward requests to the datacenter DNS servers.

When I do a reverse DNS lookup for an IP in the datacenter I always get non-existent domain on my clients (which only have our domain DNS servers set in their config). If I now put one of the datacenter DNS servers on the first position the reverse lookup works, but their dns gives me no working result on public domain names.

The DNS eventlog posts only the updates form another trusted domain, no errors or warnings at all.

I enabled the debug log of the DNS server and when a client asks the DNS server for the reverse lookup I see it asks Google for an answer, Google replies (UDP Rcv 8.8.8.8         8d4d R Q [8381   DR NXDOMAIN]) and then my server answers my client. But I get the non-existent domain from the Google response, shouldn't my DNS server ask all the other DNS servers if they new anything about this internal IP (Class A, 10.x.x.x) of the Datacenter?

Config:
2 Windows Server 2008R2 and 1 2003 R1 DNS Servers
Domain is on 2003 level
Recursion is enabled

Best Regards,

Christian Arnold



Viewing all articles
Browse latest Browse all 5877

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>