Bind

  • Thread starter Thread starter David Dionne
  • Start date Start date
D

David Dionne

Hey, im looking for an interoperability guide for bind/dhcp and AD.

all of our nameservers are bind 9.x and run on solaris as well as our dhcp
servers.

im looking for guidance on unix dhcp/ddns and Active Directory
interoperability...got a unix shop here and we're begining the process of
embracing Wintel.

thx
 
I heard that this was a great resource for Unix folks looking to make the
transistion.....did i hear wrong?
 
Actually it's alot easier to use MS DNS/DHCP services. It's much easier to
configure, the DNS and DHCP APIs work together, and easy to administer and
it just works. Even works together with WINS, that is if you have an
enterprise environment where they need Network Neighborhood to work across
subnets. Plus, Secure Updates work with MS DDNS/DHCP. There is no
interoperability between Unix and MS on this as of yet because the TSIGs
don't work together.

Many have chosen to use Unix. There are some tricks to get it to work, if
you want to continue to use your Unix resources. I'm just suggesting it's
way easier to use MS services for this, especially with AD.

Here's a couple links on BIND interoperablity.

Configuring Berkeley Internet Name Domain (BIND) to Support Active
Directory:
http://www.microsoft.com/technet/tr...net/prodtechnol/iis/deploy/depovg/cfgbind.asp

Support WebCast Microsoft Windows 2000 DNS and UNIX BIND DNS
Interoperability:
http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wc022602/wcblurb022602.asp

I don't have any links on 3rd party DHCP, but as long as it supports Option
081, then DDNS thru DHCP will work for client registration. Legacy client
registration will work with MS DHCP since it supports it for those clients.
I don't believe this will work with Unix' DHCP service, at least I haven't
heard, unless someone else posts otherwise. I'm also aware that MetaIP and
QIP work well too..

Here's some info on DDNS/DHCP interoperability:

Using DNS servers with DHCP:
http://www.microsoft.com/windows200...ver/help/sag_DHCP_imp_InteroperabilityDns.htm

Hope that helps out.

--
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
 
I don't have any links on 3rd party DHCP, but as long as it supports
Option 081, then DDNS thru DHCP will work for client registration.
Legacy client registration will work with MS DHCP since it supports it
for those clients. I don't believe this will work with Unix' DHCP
service, at least I haven't heard, unless someone else posts
otherwise. I'm also aware that MetaIP and QIP work well too..

The ISC DHCP can do proxy DNS registration.

One feature I like in the ISC server that MS lacks is the ability to not
reply right away, but to respond only when the request retry counter
reaches a configured value. This is useful for a backup server that
shouldn't hand out addresses unless the primary is down. This keeps dynamic
addresses from ping-ponging between two servers based on which replied
faster on a given day.
 
As long as the unix bind server supports ddns and is configured to accept
updates from the domain controllers and from the unix dhcp server, you
shouldn't have any problems. If you need more specific guidance, we will
need more details.
 
Back
Top