I`m facing kind of a challenge. At the moment we have BIND and windows DNS within our corporate network.
I would like to get rid of windows DNS and switch completely over to BIND, but since DNS is so intertwined with AD this is not an option since it probably introduces more problems then it solves So my next option was to delegate all the windows specific subdomains (i.e. _tcp.example.com, _udp.example.com, _sites.example.com, _msdcs.example.com etc.) to windows DNS for dynamic updates and let the main domain, .example.com, reside on BIND. After setting up BIND and windows DNS and removing the main domain entry from the windows DNS servers, leaving only the windows specific subdomains, and pointing the dns resolvers of windows to the BIND servers the windows clients were unable to register themselves within DNS and AD properly. It seems the clients register themselves in the main zone file of the domain, which resides on BIND. Since I don`t want all dynamic updates from windows clients polluting my main zone file, but still want one primary DNS serving the main domain instead of two, BIND and windows, what it is the best option if there is one. Any advise would greatly be appreciated. Cheers, Arnoud _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
