Forwarding for unknown addresses

From: Nathan Coraor (anonymous_at_discussions.microsoft.com)
Date: 09/21/04 

Date: Tue, 21 Sep 2004 13:04:38 -0700

I'm having a problem with the domain DNS server not
forwarding requests for our reverse domain to our main DNS
servers. This server acts as a forwarder - it only knows
about domain members that auto-update the zone, the rest
of the requests it is supposed to forward to the
forwarders. These forwarders know the rest of the DNS
information for our top domain and IP block.

For the Forward Lookup Zone, it forwards requests OK.
This is because our Windows domain is a subdomain of our
full domain name (i.e. win.whatever.com), so requests for
somethingelse.whatever.com will be sent on to the
forwarder. However, for the Reverse Lookup Zone, it
doesn't forward requests that are not in the zone.

Let's say the RLZ is 192.168.x.x Subnet. There's a domain
member:

  foo.win.whatever.com == 192.168.5.20

And some other host, that's not a domain member:

  bar.whatever.com == 192.168.5.21

If I look up foo.win.whatever.com, the server will tell me
192.168.5.20. If I look up bar.whatever.com, it will tell
me 192.168.5.21, since it forwards the non
win.whatever.com request to a main DNS server.

If I look up 192.168.5.20, the server will tell me
foo.win.whatever.com, because it has that information in
it's own tables. However, if I look up 192.168.5.21, it
replies that the address does not have a name, since it
believes it is the authoritative DNS server for
192.168.x.x. The desired action, however, is to forward
this request to the true main DNS server.

Is there any way to get it to forward these requests that
it does not know, even if it considers itself
authoritative for the zone?

Thanks in advance,
--nate

Relevant Pages

  • Re: Forwarding for unknown addresses
    ... > forwarding requests for our reverse domain to our main DNS ... This server acts as a forwarder - it only knows ... > win.whatever.com request to a main DNS server. ...
    (microsoft.public.win2000.dns)
  • Re: Forwarding for unknown addresses
    ... > forwarding requests for our reverse domain to our main DNS ... This server acts as a forwarder - it only knows ... > For the Forward Lookup Zone, ... > win.whatever.com request to a main DNS server. ...
    (microsoft.public.win2000.dns)
  • Re: Track DNS Requests
    ... > look at a cache of requests. ... Technically this is more a cache of responses than requests since ... DNS server had to ask other servers. ...
    (microsoft.public.windows.server.dns)
  • Re: Cannot access internal website - 502 proxy error
    ... LAN's NIC of ISA 2004 already point to internal DNS server and our DNS ... Set up ISA2k4 so that it can resolve your domain DNS requests through your ... NIC of ISA 2k4) and I config proxy on their IE. ...
    (microsoft.public.isa)
  • Re: zone transfer
    ... be registered to DC DNS server,stand alone DNS server and secondary DNS ... > all client requests are UDP while Zone transfers use TCP, ...
    (microsoft.public.win2000.dns)
Loading