Non-Authoritative DNS

[Jake McDermott]

Folks -

I have a situation on my hands where I need my Win2K DNS server to
resolve a few names for a domain, but not be authoritative for that
domain...

So let's say foo.com is hosted by my ISP. I have an internal route to
some hosts on foo.com that have non-public addresses. how can I tell my
Win2K DNS server to not be authoritative for foo.com, only resolve those
20 or so internal hosts, and if it does not have a record for that host,
to look it up using normal methods instead of stopping completely and
saying there is no record? (IE, go out to my ISP and check there if it's
not locally.)

I don't want to maintain a complete copy of foo.com on our internal DNS
server if I can at all avoid it.

Thanks!

 

[Danny Sanders]

You will need to add a www record on your internal DNS server pointing to
the website IP address.
That way your AD DNS server can remain authoritive for the foo.com and the
www record will point http requests to the correct IP address.

hth
DDS W 2k MVP MCSE

 

[Jake McDermott]

Hmm. My ISP hosts foo.com..and what they have is fine for external
users, but for internal users, I need a few hosts to resolve to
something different. We have a AD DNS server only. If I add in a new
zone for foo.com, it assumes that is it authoritative...and will assume
that if the host is not in its database for foo.com, then it doesn't
exist...instead of passing the query on in case it exists outside our
network...

I want the machine to resolve some hosts for foo.com, but pass any
requests it can't find a match for on to our ISP...that way, I don't
have to maintain two copies of foo.com...just the full copy on our ISP,
and a subset of 20 hosts strictly for internal users...

 

[Kevin D. Goodknecht [MVP]]

In

Hmm. My ISP hosts foo.com..and what they have is fine for external
users, but for internal users, I need a few hosts to resolve to
something different. We have a AD DNS server only. If I add in a new
zone for foo.com, it assumes that is it authoritative...and will
assume that if the host is not in its database for foo.com, then it
doesn't exist...instead of passing the query on in case it exists
outside our network...

I want the machine to resolve some hosts for foo.com, but pass any
requests it can't find a match for on to our ISP...that way, I don't
have to maintain two copies of foo.com...just the full copy on our
ISP, and a subset of 20 hosts strictly for internal users...

This is so easy to do you'll go duh!

Make the zone the FQDN of the host you want it to resolve to then create a
blank host record in the zone with the IP of the host you want resolved.
Here is your example:
Create a forward lookup zone named www.foo.com in the zone one host
(same as parent folder) A <hostipaddress>

Now, all other names in foo.com will be forwarded except www.foo.com, it
will resolve to the IP you gave to the blank host.

 

[Jake McDermott]

That's so crazy, it might just work. I'll give it a try! XD

WOuld really like to find an alternative that doesn't clutter up my DNS
tool, though...but if this is the only way to do it...believe me, I'm
all over it. The alternative is to keep a DNS proxy up and running....yeeg.

Thanks!

 

[Kevin D. Goodknecht [MVP]]

In

That's so crazy, it might just work. I'll give it a try! XD

WOuld really like to find an alternative that doesn't clutter up my
DNS tool, though...but if this is the only way to do it...believe me,
I'm
all over it. The alternative is to keep a DNS proxy up and
running....yeeg.

The only other alternative is to make the zone foo.com and add the records
for www or what ever in the public zone.