primary name server (mname) field data

[Mark_Andrews at isc.org]

> 
> --rJwd6BRFiFCcLxzm
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> On Thu, Nov 28, 2002 at 10:17:01AM +1100, Mark.Andrews at isc.org wrote:
> >=20
> > > This is covered regularly here. DDNS clients use the MNAME field value
> > > to send updates to, and by default BIND masters/slaves don't send NOTIFY
> > > messages to hosts in the MNAME field.
> >=20
> > 	Well anyone that implements NOTIFY shouldn't be sending to a
> > 	NS that is the same as the MNAME.
> 
> I don't get it - are you just saying "BIND is correct"? Nobody said
> otherwise.=20
> --=20
> Nate Campi   http://www.campin.net=20
> 
> "Good breeding consists in concealing how much we think of ourselves and=20
> how little we think of the other person." - Samuel Clemens

	I'm saying that it is a property of the protocol.  BIND
	just implements the protocol.  Too many things that are
	properties of the protocol keep getting attributed to BIND.
	The above paragraph reads like this is BIND specific when
	it isn't.

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org