OT: Windows and reverse lookup and DHCP

[Simon Waters]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On a network that lost reverse lookup due to routing problems, various
*nix things had to wait for time-outs or barfed due to lack of the
reverse lookup depending on their level of paranoia.

However some of the Windows machines were apparently completing DHCP
handshake with the DHCP server on booting, and then ignoring the address
proferred and picking one in the zero administraion IP range.

Anyone know why some Windows clients do this? I'm just curious, as I
hadn't seen it before, so assume it is a new feature (my Windows admin
days were almost past), or an option somewhere....

Yes, the reverse lookup zone is now local to the ethernet, so far less
likely to vanish, but I didn't believe DNS to be vital to DHCP
operation, and it is an unwanted dependency as far as I'm concerned.
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/otVnGFXfHI9FVgYRAopdAKCw5kx9DYUGjaoSvgAbwChJLw/qkQCgqBlR
7KZOhzZS/g2CvZT3SjDEF7w=
=MGXK
-----END PGP SIGNATURE-----