Is there an FAQ somewhere that details how to configure the inbuilt DHCP/DNS and the remote client to allow a remote user on the end of a dialup somewhere to update back to the Windows server, bearing in mind that the remote client will not be a part of the Windows domain ?
As long as the zone isn't Active Directory integrated, you shouldn't have any problems--there's absolutely NO kind of DDNS security on Win2k, so any win2k/xp machine that has the same domain suffix and points its primary DNS at your DNS server will be able to register both an A record and a PTR record for itself. If you'r eassigning addresses via DHCP, the machine will register the A record, and the DHCP server will register the PTR record.
There are (obviously!) potential problems with this, but presuming you're on a non-routable network, I'd say the risk is minimal.
If your zone is AD integrated, the machine will have to authenticate itself before its allowed to register. This wouldn't work in your scenario above.
SDNSPLUS from JHSOFT supports Dynamic dns with many clients softwares.
It runs on just about anything and can do 2000/2003 AD records, root Internet DNS, and dynamic DNS. I have replaced my windows 2003 DNS with this, it is much faster and more flexible, and still have all the security I need
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.