[63165] in North American Network Operators' Group
Re: Annoying dynamic DNS updates (was Re: someone from attbi please
daemon@ATHENA.MIT.EDU (Owen DeLong)
Mon Sep 29 12:32:16 2003
Date: Mon, 29 Sep 2003 09:26:57 -0700
From: Owen DeLong <owen@delong.com>
To: jlewis@packetnexus.com, sean@donelan.com
Cc: nanog@merit.edu
In-Reply-To: <4354.192.168.120.34.1064707419.squirrel@192.168.120.81>
Errors-To: owner-nanog-outgoing@merit.edu
The difference is that Netgear admitted responsibility and worked with
UW to cope with the issue. Further, Netgear has funded UW in it's
cleanup efforts and generally stepped up to the plate. As much as I don't
care for Netgear's products, they did show decent corporate responsibility
when UW was able to escalate to the appropriate management at Netgear.
Micr0$0ft, on the other hand, has consitently said "You just have to cope
with whatever we do to you, and, it's your problem." This is a very
different corporate attitude. In my opinion, that attitude deserves to
be severely punished.
Owen
--On Saturday, September 27, 2003 8:03 PM -0400 Jason Lewis
<jlewis@packetnexus.com> wrote:
>
> 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?
>
>
>
