OK, at work I've done active directory with Windows Server 2003 and a Linux/Bind9/DHCP3 server integration two ways. DNS delegated to the Windows server, and DNS integrated on the Linux server with the Windows server providing updates. In both cases the setup was something along the lines of the Internet domain being "your.company.work" and the active directory domain being "ad.your.company.work" (Don't rush out and try to register a .work domain - it's just for examples.) I'd recommend for simplicity's sake delegating the zone to the Windows server. It is a little easier to configure, and offers much better security for the primary zone. After struggling with some of the online directions for using a BIND server with active directory - setting up four or six sub zones with glue records everywhere, I find that it is actually quite easy to do with a single sub zone for the active directory domain. If anyone is interested, I can demo at a meeting. Microsoft was kind enough to send me an evaluation version of Server 2003 last year, and I haven't even cracked the seal on the mailer yet. Would be an excuse to do so, just to make sure the CD works. :) Cheers, James ------------------------------------ This is the Juneau-LUG mailing list. To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx with the word unsubscribe in the subject header.