To:
dns op wg <dnsop@cafax.se>
From:
Michael Milligan <milli@acmebw.com>
Date:
Mon, 25 Feb 2002 00:44:02 -0700
Sender:
owner-dnsop@cafax.se
User-Agent:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020214
Subject:
Re: spurious updates
Randy Bush wrote: > so why are all these spurious updates in my logs? many hundreds a day. > > 28-Jan-2002 17:41:57.596 update: info: client 63.196.106.137#27581: updating zone 'psg.com/IN': update failed: LT-MURRAY.psg.com/A: 'RRset exists (value dependent)' prerequisite not satisfied (NXRRSET) > 28-Jan-2002 17:41:57.765 security: error: client 63.196.106.137#27584: update 'psg.com/IN' denied > 28-Jan-2002 17:42:09.114 security: error: client 209.190.8.131#44326: update 'psg.com/IN' denied > 28-Jan-2002 17:42:19.144 security: error: client 209.190.8.131#44331: update 'psg.com/IN' denied > 28-Jan-2002 17:44:31.118 security: error: client 196.6.129.83#1180: update forwarding denied > 28-Jan-2002 17:47:06.549 security: error: client 209.190.8.131#44336: update 'psg.com/IN' denied > 28-Jan-2002 17:47:08.570 security: error: client 209.190.8.131#44340: update 'psg.com/IN' denied Too bad you really are supporting dynamic update. Otherwise, the minor SOA change below would work wonderfully to tell W2K clients to "go away", almost surely the source of these update attempts. Mr. Kwan says it shouldn't cause W2K any problems... and it hasn't far as I can tell. ;-) Of course, it only works because W2K doesn't quite follow RFC 2136 Section 4. $ORIGIN psg.com. @ IN SOA localhost hostmaster.psg.com. 200201281 86400 3600 2592000 1440 localhost A 127.0.0.1 Regards, Mike -- Michael Milligan - Verisign Global Registry - mmilligan@verisign.com