CC:
dnsop@cafax.se
From:
"Eric A. Hall" <ehall@ehsco.com>
Date:
Wed, 26 Apr 2000 09:33:01 -0700
Sender:
owner-dnsop@cafax.se
Subject:
Re: root server load and dynamic updates.
> com SOA A.ROOT-SERVERS.NET hostmaster.internic.NET > net SOA A.ROOT-SERVERS.net hostmaster.internic.net > org SOA A.ROOT-SERVERS.NET hostmaster.internic.NET > in-addr.arpa SOA A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET What would be the ramifications of setting MNAME to a bogus name? If MNAME is only used for DDNS, then setting it to a bogus name would prevent updates from hammering on A. Obviously, any system can be misconfigured, so if using a bogus MNAMA would prevent misconfigured systems from attempting to update these zones, it might be worth exploring as a long-term option for all affected zones. Like co.uk. could be configured with bogus MNAME data, and so forth, if it works to prevent updates from misconfigured users. -- Eric A. Hall ehall@ehsco.com +1-650-685-0557 http://www.ehsco.com