Upgrading to 2003 server. Question about DNS and WINS
Currently we are running NT4 as our domain controllers and Linux as the main faile server, dns and dhcp server.
I know that once we go to 2003 the active directory is dns based.
I would like to keep our existing DHCP server and DNS server running on Linux.
I dont mind having the domain controllers using their own DNS server and have them set to forward to the Linux machine.
How much of a problem is that going to cause?
Can 2003 SBS server still run a WINS server for backward compatibility?
I know that once we go to 2003 the active directory is dns based.
I would like to keep our existing DHCP server and DNS server running on Linux.
I dont mind having the domain controllers using their own DNS server and have them set to forward to the Linux machine.
How much of a problem is that going to cause?
Can 2003 SBS server still run a WINS server for backward compatibility?
ASKER
What propegates the entries into the AD DNS for the clients?
Currently on our linux machine it is the DHCP server which updates the A, PTR and CNAME records in the DNS.
If it is the client or the AD server which updates the DNS in the windows network then both systems should be able to run at the same time as they both update different domains.
The AD domain will be something like companyname.local and the windows DNS will forward all other requests to the linux DNS server.
The Linux DNS/DHCP server keeps companyname.co.uk updated and this contains a lot of static entries for test servers etc... There is split-dns configured so vpn users still get the public IP address of the servers.
DHCP server will need to be reconfigured to specify the AD DNS server to the windows clients instead of the Linux one.
Does that all sound reasonable?
Currently on our linux machine it is the DHCP server which updates the A, PTR and CNAME records in the DNS.
If it is the client or the AD server which updates the DNS in the windows network then both systems should be able to run at the same time as they both update different domains.
The AD domain will be something like companyname.local and the windows DNS will forward all other requests to the linux DNS server.
The Linux DNS/DHCP server keeps companyname.co.uk updated and this contains a lot of static entries for test servers etc... There is split-dns configured so vpn users still get the public IP address of the servers.
DHCP server will need to be reconfigured to specify the AD DNS server to the windows clients instead of the Linux one.
Does that all sound reasonable?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks I have no issues with using windows for the DNS server and forwarding to Linux.
Its really just the Linux DHCP server that I want to keep using.
Its really just the Linux DHCP server that I want to keep using.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
DHCP can run from Linux, too, if you make sure that the SBS is handed out as DNS server to the domain members.
If your Linux DNS is supporting Dynamic DNS updates and SRV resource records, you could even use the Linux DNS exclusively.
And, yes, W2k3 still supports WINS.
10 DNS Errors That Will Kill Your Network
http://redmondmag.com/features/article.asp?EditorialsID=413
Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382
Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/?kbid=825036