adding win 2000 server domain controller, bind dns
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Windows 2000 domains do a lot of stuff in their DNS records that go beyond what most people usually use. The best way to see it is simply to add the Microsoft DNS server (from the win2k disk) to your primary domain controller and then setup your bind server to act as a secondary dns server for the domain (which works very well).
If you don't want to do that ... I can give you some hints about the DNS and Windows 2000.
Basically Windows 2000 domains completely depend on DNS to find important services such as LDAP, PRIMARY DOMAIN CONTROLLER, and all that jazz.
Here is some example lines from a Windows 2000 domain ready bind file.
And this goes on and on ... It also enters what look like SID's in some of the records for the machines.
that's the reason why I ended up just letting the Windows 2000 Server handle its own domain's DNS file which gets exported to the bind server. I think you might be able to setup it up on the Windows 2000 PDC and then convert your secondary record on your bind server to a primary and the windows server will be fine.
You might also trysetting the linux server as primary server but allowing the Windows 2000 PDC to update the zone file for the domain. This should allow it to write its services and other information to the zone.
The "by the book" way would be just to create a subdomain of your real domain and make that the windows 2K domain.
Sure your windows machines would have ugly names like ...
machinename.win2k.domain.com but you can CNAME them some shorter names you if you want and when it comes to file sharing they will still answer to \\machinename without any problems.
Just remember to run the win2k domain in mixed mode so you can add samba machines if you want or pre-win2k machines.
In case you're wondering I had to learn all this win stuff doing a very mixed office scene. I work in radio where you end up with a huge hodge podge of machines ... a lot of them running everything from mac to dos to XP and I have thrown a whole bank of linux machines on top to usher in the stable backbone and web services for it. In my particular situation i ended up running two groups of DNS servers ... one for the private network and DMZ's and one for the public internet needs.