-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At some point hitherto, John Abreau hath spake thusly: > Nathan Meyers writes: > > > No large-scale networks here - just locally cached DNS records that go > > AWOL, but only when referring to Linux hosts. There's no easy fix for the > > suckitude of Windows, but maybe this particular problem is more tractable. > > > > I recall a few years ago someone discovered a bug in Access that would > subtly corrupt its data. MS-DNS could easily have a similar bug where its > zone data occasionally gets flaky. Such a bug would be more likely to > be triggered in a large-scale network, but it wouldn't necessarily > *require* a large-scale network to trigger the bug. As I said earlier, I've seen exactly this behavior with W2k clients before, where the DNS and DHCP servers were all running Linux. I'm reasonably certain this is a client-side bug, and not related to the DNS running on W2k servers in the slightest. As for why it only affects clients trying to get to Linux boxes, I believe this is because those machines do not participate in an NT/2K domain, and have no WINS information to fall back upon. Have no factual data to back that up, but it seems logical... - -- Derek Martin ddm@pizzashack.org - --------------------------------------------- I prefer mail encrypted with PGP/GPG! GnuPG Key ID: 0x81CFE75D Retrieve my public key at http://pgp.mit.edu Learn more about it at http://www.gnupg.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9imjRdjdlQoHP510RAjeTAJ9/2exAfdz1ralSWDsiMZIv6YBytwCffcj1 mfYipSqbEu9OR9AHPrR/qEs= =r2xE -----END PGP SIGNATURE-----