I appreciate all the links, guys.
All I need is for the BIND machine to able to point clients to the
appropriate DCs. It is a single application, so I don't need a lot of
functionality. Based on the webcast, I think my best bet is zone delegation
for _udp, _tcp, _msdcs, etc. That way I can keep the data on the Windows
DNS boxes.
>I apologize that this message is somewhat off-topic. We have a proprietary
>system that is running BIND 9.1.3 and I need to populate this server with
[quoted text clipped - 3 lines]
>
> Blake
> I appreciate all the links, guys.
>
[quoted text clipped - 3 lines]
> delegation for _udp, _tcp, _msdcs, etc. That way I can keep the data
> on the Windows DNS boxes.
Blake,
You mean delegation for the AD namespace? E.g. domain.com is your Internet
domain name, and you use ad.domain.com for your AD DNS domain name? If that
is what you mean, yes, that's a good choice. Makes it easier
administrative-wise. You can also choose a private name, such as domain.net,
which of course is not one you would be using on the Internet.
Ace
Blake - 27 Jul 2005 15:52 GMT
We have been running MS DNS in our production environment for years with no
problems.
Our network people have put a small number of clients on a subnet that can
only get to a single server. That server runs BIND and resolves everything
to itself. The problem is the clients need to be able to log onto the
domain. I would like to simply delegate the subdomains:
_udp.ourdomain.edu
_tcp.ourdomain.edu
_sites.ourdomain.edu
_msdcs.ourdomain.edu
Once these clients jump through a hoop, they go on our production network
and our regular AD integrated DNS on Windows 2000. All I need is a single
domain logon per client, then they get on the regular network. So I need
the absolute minimum on the BIND box so that the clients can log onto the
domain the first time.
Thanks
Blake
> In news:uBQUq6qkFHA.764@TK2MSFTNGP14.phx.gbl,
> Blake <blake_duffey@NOSPAM.hotmail.com> stated, which I then commented on
[quoted text clipped - 16 lines]
>
> Ace
Ace Fekay [MVP] - 27 Jul 2005 19:26 GMT
> We have been running MS DNS in our production environment for years
> with no problems.
[quoted text clipped - 17 lines]
> Thanks
> Blake
I see. How about conditional forwarding for "ourdomain.edu" namespace to the
internal Windows DNS server? BIND supports conditional forwarding. Unless of
course the BIND server is hosting the ourdomain.edu namespace, which
forwarding wouldn't work the delegation would be the key.
Also, if the BIND server doesn;t host ourdomain.edu, you can create a
secondary on that server. If it is a public nameserver, I wouldn't put any
internal data on it, delegated or not and would rather opt to place another
separate DNS server (not part of a domain) that has a secondary zone just to
serve your domain clients.
Ace
Ace