[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: "Eric A. Hall" <ehall@ehsco.com>
Cc: dnsop@cafax.se
From: Mark Andrews <Mark.Andrews@nominum.com>
Date: Thu, 27 Apr 2000 03:37:53 +1000
In-Reply-To: Your message of "Wed, 26 Apr 2000 09:33:01 MST." <39071A3D.8DFAC220@ehsco.com>
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.

	No.  Then ALL the listed servers would be pounded apon as
	required by NOTIFY to support stealth servers.

	Mark
> 
> -- 
> Eric A. Hall                                            ehall@ehsco.com
> +1-650-685-0557                                    http://www.ehsco.com
--
Mark Andrews, Nominum Inc. / Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@nominum.com

Home | Date list | Subject list