name resolution from local primary & parent

[Art OMalley]

We are trying to get name resolution from a parent domain
while having created our own primary of the parent to
support hosts that the parent doesn't care about.

We were able to do this on NET ID DNS but have been
unsuccessful with Win2K DNS after duplicating the parent
domain's SOA & NS records we've been using in NET ID.

We do not wish to be a secondary of the parent. We just
want a few of our hosts being resolved with the parent's
domain FQDN and foward any queries for resolution of other
parent domain's hosts on to their DNS servers.

The parent doesn't have issue with what we're doing as our
naming scheme prevents duplication.

Thanks in advance,

Art

 

[William Stacey]

I don't understand the issue. If you have another primary, just add any
records you require in that zone. I assume from your description you don't
care about SRV records, just A records?
Please expand more on the problem if possible.
--wjs

 

[Ace Fekay [MVP]]

We are trying to get name resolution from a parent domain
while having created our own primary of the parent to
support hosts that the parent doesn't care about.

We were able to do this on NET ID DNS but have been
unsuccessful with Win2K DNS after duplicating the parent
domain's SOA & NS records we've been using in NET ID.

We do not wish to be a secondary of the parent. We just
want a few of our hosts being resolved with the parent's
domain FQDN and foward any queries for resolution of other
parent domain's hosts on to their DNS servers.

The parent doesn't have issue with what we're doing as our
naming scheme prevents duplication.

Thanks in advance,

Art

I'm not familiar with "Net ID" DNS. Can I assume it's a 3rd party DNS
service that runs on a Windows machine?

As far as I see it, if you don't care about the records, (as William said
too about not caring about the SRV records), why not just create the zone
and manually just enter records that you only want to resolve?

If the zone name is different than what you have in your own DNS, maybe
forwarding to it may be easier, depending on what you're trying to do.

Please do elaborate a little more.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Art O'Malley]

Ace and William -

Thanks for your replies.

Net ID DNS is a 3rd party DNS service running on Unix (supported now by
Nortel). We want to retire this DNS, so it will no longer be used to
forward requests to the parent domain.

We only care about A records, but after manually creating the zone for the
parent domain, queries for hosts, not included in our Win2K Primary zone,
are not getting resolved by the parent's domain SOA.

It's as if the queries are not getting forwarded to the parent, but when we
connect with NSLOOKUP from the Win2K DNS to the parent's DNS, we get
resolution just fine.

Art

 

[Ace Fekay [MVP]]

In

Ace and William -

Thanks for your replies.

Net ID DNS is a 3rd party DNS service running on Unix (supported now
by Nortel). We want to retire this DNS, so it will no longer be used
to forward requests to the parent domain.

We only care about A records, but after manually creating the zone
for the parent domain, queries for hosts, not included in our Win2K
Primary zone, are not getting resolved by the parent's domain SOA.

It's as if the queries are not getting forwarded to the parent, but
when we connect with NSLOOKUP from the Win2K DNS to the parent's DNS,
we get resolution just fine.

Art

If I read this right, if the zone name that's being queried are the same, it
won't forward it since it's authorative for the zone. You'll have to ensure
on the W2k DNS that all the info that users need to query are manually
entered.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory