[63135] in North American Network Operators' Group
RE: Annoying dynamic DNS updates (was Re: someone from attbi please contact me ...)
daemon@ATHENA.MIT.EDU (Vivien M.)
Sun Sep 28 18:05:26 2003
From: "Vivien M." <vivienm@dyndns.org>
To: "'Brian Bruns'" <bruns@2mbit.com>, <nanog@merit.edu>,
"'Paul Vixie'" <vixie@vix.com>
Date: Sun, 28 Sep 2003 18:04:14 -0400
In-Reply-To: <001c01c3860b$d43aee60$1b80b93f@2mbit.com>
Errors-To: owner-nanog-outgoing@merit.edu
> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On=20
> Behalf Of Brian Bruns
> Sent: September 28, 2003 6:00 PM
> To: nanog@merit.edu; Paul Vixie
> Subject: Re: Annoying dynamic DNS updates (was Re: someone=20
> from attbi please contact me ...)
>=20
> How about just configuring your BIND to return errors when=20
> his queries against your server? He has got to be using you=20
> as either a primary or secondary name server. That would=20
No, that's not how it works... (at least, the Win2K/XP-style of this)=20
It works based on the system's hostname. If you set your Windoze =
hostname to
blah.domain.com, then the server in domain.com's SOA is going to get =
blasted
with all those RFC 2136 updates.
In your case, I'm guessing your customers had (automatic DNS =
configuration
through DHCP? PPP?) a hostname in your domain, so that's actually why =
the
updates went your way, not because you were their primary/secondary DNS =
in
their DNS config.
Vivien
--=20
Vivien M.
vivienm@dyndns.org
Assistant System Administrator
Dynamic DNS Network Services
http://www.dyndns.org/=20
