[ID 866145 daemon.error] client 123.123.123.123#1799: update denied

[Kevin Darcy]

hillman at polaris.net wrote:

> Barry,
> Thanks for your response.  Is this normal even when that IP address
> has nothing to do with us?  I've been seing several IPs show up in the
> logs--none of them are related to us in any way.  The DNS server
> that's producing the error that I displayed below acts as primary for
> some domains, secondary for others.  There are only two other DNS
> servers that we deal with and both are inside our own network.

Yes, it's "normal", although mystifying. I get tons of update attempts from
unrelated clients for things like jeep.com and mopar.com and even
far-less-well-known domains like fivestar.com. I have no idea how these clients are
being configured with our domain names...


- Kevin

> On 10 Jul 2001 10:12:07 -0700, Barry Margolin <barmar at genuity.net>
> wrote:
>
> >In article <9ifb4t$3iu at pub3.rc.vix.com>,
> >Josh Hillman <hillman at polaris.net> wrote:
> >>What causes this message to come up all over the place in the logs for
> >>BIND 9.1.3?:
> >>
> >>named[15620]: [ID 866145 daemon.error] client 123.123.123.123#1799:
> >>update denied
> >
> >The machine at IP address 123.123.123.123 tried to perform a dynamic
> >update.  Since you don't have them in your allow-update list (the default
> >list is empty), the attempted update was denied and the attempt was logged.
> >
> >It's probably a Windows machine.  When they get their address via DHCP they
> >try to add it to DNS.