We have a BIND server which is authoritative for zone "company.com". After some
years we implemented Microsoft AD with its own DNS server in its own
zone "ad.company.com". The Microsoft server is authoritative for
"ad.company.com"
Now we want clients that have the BIND server as their configured DNS
server to be able to resolve hosts in the "ad.company.com" zone. I
thought this was done by configuring a forward zone "ad.company.com" on the BIND
server, alternatively use the "forwarders" option. However, neither of these methods seem to work.
Is there something I am missing here?
Kind regards,
Rutger Blom
Type forward won't work for a sub-zone of something you are already
authoritative for. I take it that you have not created a proper delegation
for "ad.company.com" from "company.com", nominating the Microsoft server
(really just one?), or you wouldn't have the problem in the first place.
So why not? If it's because the "ad.company.com" zone is meant to be private,
consider using views in BIND.
--
Chris Thompson
Email: ce...@cam.ac.uk
- Kevin
I'm no BIND expert as you noticed.
Is there some documentation on how to create a proper delegation? The "ad.company.com" domain does not need to be kept private so no need for views.
Rutger
>>> Chris Thompson <ce...@hermes.cam.ac.uk> 07-11-09 21:27 >>>
On Nov 9 2007, Rutger Blom wrote:
>Hello,
>
>We have a BIND server which is authoritative for zone "company.com". After some
>years we implemented Microsoft AD with its own DNS server in its own
>zone "ad.company.com". The Microsoft server is authoritative for
>"ad.company.com"
>
>Now we want clients that have the BIND server as their configured DNS
>server to be able to resolve hosts in the "ad.company.com" zone. I
>thought this was done by configuring a forward zone "ad.company.com" on the BIND
>server, alternatively use the "forwarders" option. However, neither of these methods seem to work.
>
>Is there something I am missing here?
Type forward won't work for a sub-zone of something you are already
RFC 1034
4.2.2. Administrative considerations
[snip]
As the last installation step, the delegation NS RRs and glue RRs
necessary to make the delegation effective should be added to the parent
zone. The administrators of both zones should insure that the NS and
glue RRs which mark both sides of the cut are consistent and remain so.
You *copy* the NS RRset from the child zone to the parent.
You *copy* any glue address (A/AAAA) records for the nameservers
to the parent zone.
Mark
> >>> Chris Thompson <ce...@hermes.cam.ac.uk> 07-11-09 21:27 >>>
> On Nov 9 2007, Rutger Blom wrote:
>
> >Hello,
> >
> >We have a BIND server which is authoritative for zone "company.com". After s
> ome
> >years we implemented Microsoft AD with its own DNS server in its own
> >zone "ad.company.com". The Microsoft server is authoritative for
> >"ad.company.com"
> >
> >Now we want clients that have the BIND server as their configured DNS
> >server to be able to resolve hosts in the "ad.company.com" zone. I
> >thought this was done by configuring a forward zone "ad.company.com" on the
> BIND
> >server, alternatively use the "forwarders" option. However, neither of these
> methods seem to work.
> >
> >Is there something I am missing here?
>
> Type forward won't work for a sub-zone of something you are already
> authoritative for. I take it that you have not created a proper delegation
> for "ad.company.com" from "company.com", nominating the Microsoft server
> (really just one?), or you wouldn't have the problem in the first place.
> So why not? If it's because the "ad.company.com" zone is meant to be private,
> consider using views in BIND.
>
> --
> Chris Thompson
> Email: ce...@cam.ac.uk
>
>
>
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_A...@isc.org
>Hello,
>
>We have a BIND server which is authoritative for zone "company.com". After some
>years we implemented Microsoft AD with its own DNS server in its own
>zone "ad.company.com". The Microsoft server is authoritative for
>"ad.company.com"
>
>Now we want clients that have the BIND server as their configured DNS
>server to be able to resolve hosts in the "ad.company.com" zone. I
>thought this was done by configuring a forward zone "ad.company.com" on the BIND
>server, alternatively use the "forwarders" option. However, neither of these methods seem to work.
>
>Is there something I am missing here?
There are at least two solutions. The one I would recommend is to
have your BIND servers slave all of the AD zones. That way, your
customers who use BIND as their DNS will get the answers to their
queries without having to have their queries sent to another DNS
server. One word of caution - you need to configure your AD DNS
to allow zone transfers, and, if you have MS DNS Servers on multiple
Domain Controllers (AD-intergrated zones with multi-master), choose
ONLY ONE server to be the master for the BIND slaves. You probably
will need to put the BIND slave servers into the AD zones in NS
records. For more details, check the archives of this list.
----------------------------------------------------------------------
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory Phone: +1 (630) 252-7277
9700 South Cass Avenue Facsimile:+1 (630) 252-4601
Building 222, Room D209 Internet: BSFi...@anl.gov
Argonne, IL 60439-4828 IBMMAIL: I1004994
Thanks again!
Rutger
>>> Barry Finkel <b19...@britaine.ctd.anl.gov> 07-11-12 16:27 >>>