W2K DNS and HP TCPIP Services for OpenVMS

[Trace Trembath]

I have the following configuration;

Master DNS running on a W2K Server machine (SP3). Slave DNS running on TCPIP Services for OpenVMS V5.1 machines with OpenVMS V7.2-1.

I only have 2 zones defined on the W2K master. A forward and a corresonding reverse zone.

I am noticing that every 40-70 minutes the serial number on the forward zone is incremented and the OpenVMS slaves then transfer the zone data. The serial number on the reverse zone does not get updated and so doesn't get transferred to the slaves.

I've compared the SOA records on the W2K server between the forward and reverse zones and they both look the same.

Does anyone know what might be causing the serial number for the forward zone on the W2K machine to keep incrementing and causing these "EXTRA" zone transfers to the slaves?

Many thanks for any and all responses!

[Willem Grooters]

I'm no Windows expert, so I stick to a hint ;-)....
Have you defined DHCP on the W2K side? It might be this updates DNS and will therefore trigger update of version, and because of that, transfer to slaves (since the version number on the slave is lower than the master's)

Willem

[Trace Trembath]

Thanks, but DHCP is not installed on that system. Or any system on that network. It's a very small isolated network.

[Trace Trembath]

I think I've found the answer.
The Netlogon service needs to have the DNS service started first. So I've set the Netlogon process to be dependent on the DNS service and all seems to be working at the moment. Haven't exhaustively tested everything but things are looking good now.