• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Active Directory setup with external DNS

Agamar

Golden Member
We are about to set up a AD domain, and I was needing to know if anybody has tried it while running a Unix bind server for DNS. We are currently using Bind 8.2.3 on a Redhat 6.2 server. Would it be easier for me to let Win2k be the DNS server, and point that DNS server to the Unix server as an "upstream" DNS server? Anybody have any good web sites for tips on this subject?
 
Im not positive but I think you need BIND 9 for this. I dont mess with BIND >4 or AD, so dont take my post as gospel 😉
 
4.9.7 and earlier BIND are incompatible with Wink 2k. After 4.9.7 BIND started accepting dynamic updates.

Windows 2000 will also not accept zone updates from Bind 9.x. Win 2k DNS servers limit the acceptance of TCP zone transfer (AXFR) messages to a maximum of 16 KB. BIND version 9.x may send TCP AXFR messages that are greater than 16 KB.; therefore, the zone transfer does not work.
 
Dynamic updates are not critical for running AD. But support of SRV records definitely is...make sure your version of BIND supports these.
 
I am pretty sure Bind 8.2.3 supports both Dynamic updates and SRV records. I am just worried about the interoperability between the AD and my version of bind. I am wondering if I should let my DC be a cachine DNS server also.
 
Thanks Saltin, I knew you would know the answer 🙂

Ive got a semi-related question for you though. I have heard Windows uses tcp 53 for dns lookups instead of udp 53, do you know if this is correct? Just curious really.
 
Back
Top