Windows 2003 and Unix DNS

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Currently I have a network running NT 4.0 with WINS only, but use a UNIX DNS
server. The plan is to upgrade to Windows 2003/AD, but the Unix DNS server
still needs to be in place. The plan is to call our new forest root domain
the same name that the Unix DNS server is the authoritive server for that
domain. Any suggestions. Would like the the DNS to be AD integrated with the
rest of the upgraded NT domains, but still use the Unix server.

Thanks,

Mike

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

That is possible - you can delegate all of the AD-related subdomains to
AD-integrated DNS servers.

http://support.microsoft.com/kb/q255913/

A slightly cleaner option is to make the forest root a child domain of your
Unix root so you only have to maintain one delegation but that introduces an
extra label into your hierarchy which may be cumbersome.

For best results try to use AD-integrated DNS servers as authorities for
your AD namespace.

"Mike B." <Mike B.@discussions.microsoft.com> wrote in message
news:01AC9300-2104-466E-8685-9A3526C15716@microsoft.com...
> Currently I have a network running NT 4.0 with WINS only, but use a UNIX
> DNS
> server. The plan is to upgrade to Windows 2003/AD, but the Unix DNS
> server
> still needs to be in place. The plan is to call our new forest root
> domain
> the same name that the Unix DNS server is the authoritive server for that
> domain. Any suggestions. Would like the the DNS to be AD integrated with
> the
> rest of the upgraded NT domains, but still use the Unix server.
>
> Thanks,
>
> Mike

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Hi,

I did it like the URL link you posted. I did option 4 to delegate
_underscore zone on both UNIX and Windows. All of our Windows clients
are still pointing to UNIX BIND server.

I have a strange problem, If i turn OFF forwarder in UNIX BIND server,
Windows clients are able to join the new Windows 2k3 AD (by entering
DNS FQDN like "abc.com" as the root domain in UNIX BIND) without any
problem.
But if i turn ON the forwarder in UNIX BIND server, none
of the Windows clients are able to join the new W2K3 AD (it said cannot
find the SRV records etc). It looks like UNIX BIND server treat the SRV
request as out of zone request and forward to the external DNS servers.


It works fine while Forwarder OFF but we have to turn forwarder ON in
UNIX BIND.

Any idea why is doing that?
Thanks.


Jeff Westhead [MSFT] wrote:
> *That is possible - you can delegate all of the AD-related subdomains
> to
> AD-integrated DNS servers.
>
> http://support.microsoft.com/kb/q255913/
>
> A slightly cleaner option is to make the forest root a child domain
> of your
> Unix root so you only have to maintain one delegation but that
> introduces an
> extra label into your hierarchy which may be cumbersome.
>
> For best results try to use AD-integrated DNS servers as authorities
> for
> your AD namespace.
>
> "Mike B." <Mike B.@discussions.microsoft.com> wrote in message
> news:01AC9300-2104-466E-8685-9A3526C15716@microsoft.com...
> > Currently I have a network running NT 4.0 with WINS only, but use a
> UNIX
> > DNS
> > server. The plan is to upgrade to Windows 2003/AD, but the Unix
> DNS
> > server
> > still needs to be in place. The plan is to call our new forest
> root
> > domain
> > the same name that the Unix DNS server is the authoritive server
> for that
> > domain. Any suggestions. Would like the the DNS to be AD
> integrated with
> > the
> > rest of the upgraded NT domains, but still use the Unix server.
> >
> > Thanks,
> >
> > Mike *



--
us_matrix
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message446413.html