[63118] in North American Network Operators' Group
Re: Annoying dynamic DNS updates (was Re: someone from attbi please contact me ...)
daemon@ATHENA.MIT.EDU (Jason Lewis)
Sat Sep 27 20:05:45 2003
Date: Sat, 27 Sep 2003 20:03:39 -0400 (EDT)
From: "Jason Lewis" <jlewis@packetnexus.com>
To: <sean@donelan.com>
In-Reply-To: <Pine.GSO.4.44.0309271921240.27158-100000@clifden.donelan.com>
Cc: <nanog@merit.edu>
Reply-To: jlewis@packetnexus.com
Errors-To: owner-nanog-outgoing@merit.edu
When will entities that implement "solutions" that cause damage on a
global scale be held accountable? The Dynamic DNS problem with Windows
boxes makes me think someone thought it would be a good idea, but didn't
really think it through. The Verisign wildcard decision seems to be along
the same lines. I doubt anyone thought there would be a class action
lawsuit when the made the change.
It reminds me of the Netgear and U of Wisconsin time server SNAFU.
http://www.cs.wisc.edu/~plonka/netgear-sntp/
jas
>
> On Sat, 27 Sep 2003, Paul Vixie wrote:
>> noc@ and abuse@ are ignoring me as usual, so i'm spamming nanog@ in
>> hopes of locating attbi clue. i need somebody who can educate one of
>> your customers who is dns-updating me.
>
> ATT Broadband was sold to Comcast a while ago. There is no more attbi
> clue.
>
> If you find someone, add these to the list of misconfigured Windows
> users trying to "update" other people's DNS servers.
>
> acl "bogon" {
> // Annoying dynamic DNS updates from this address
> 68.39.224.6;
> 68.38.156.178;
> 68.38.152.156;
> 68.38.158.209;
> };
>
>>
>> PS. why is this so hard?
>>
>
> Are you talking about the kitchen sink protocol called DNS, or trying to
> contact another ISP, or the sociological difficulties of educating the
> general public how to configure very complicated "personal" computers
> and software without making a mistake?
>
> Why is dynamic DNS update enabled by default on some operating systems?
