Issues with static and dynamic IP address (using WINS and DNS)

[Luis Toro]

We have HPUX and Windows servers on our network (I am responsible for the sysadmin of the UX servers). Here's the issue I'm having with the WINS/DNS/Active Directory folks: All HPUX servers have static entries in DNS (forward and reverse). I'm not technical in this space, but it seems that although the windows servers also have static IPs (client desktops are dhcp), they have the capability of dynamically updating WINS and/or DNS. So whereas I have to go through a manual effort to get a new HPUX server in DNS (which in and of itself ensures some checks and balances), on the windows side the update is automatic. As a result, we have had the following problem: reverse lookups pointing to wrong hostnames. Doesn't happen often, but once is one time too many. Is there a way to prevent windows from doing an automatic update, without affecting the client side, which certainly requires it.
Thanks

[Ivan Krastev]

You can use different pool, not listed in dhcp for Unix servers. Just reserve some IP's for servers and remove it from dhcp clients and automatic updates. In that case you should add DNS records manually.


regards,
ivan

[Steven E. Protter]

Shalom,

I know of no way to make Windows systems stop doing dynamic WINS or DNS. You can alleviate the problem by building a central DNS server, preferably on your most reliable HP-UX box.

One zone record for your domain can contain reverse lookups, even for the dynamically assigned ip addresses being used by windows.

This solution still lets your network have DHCP.

The same thing could be done with a central Windows DNS server, however its much harder to configure. Real sysadmins, e.g. Unix admins don't use GUI's. Most of the time anyway.

SEP

[Luis Toro]

thanks for your replies.