[120331] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: DNS question, null MX records

daemon@ATHENA.MIT.EDU (Brian Dickson)
Wed Dec 16 15:45:55 2009

From: Brian Dickson <Brian.Dickson@concertia.com>
To: Mark Andrews <marka@isc.org>, Joe Abley <jabley@hopcount.ca>
Date: Wed, 16 Dec 2009 16:44:54 -0400
In-Reply-To: <200912162020.nBGKKf6u066979@drugs.dv.isc.org>
Cc: "'nanog@nanog.org'" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

I realize we're a bit off-topic, but to be tangential to the original topic=
, and thus barely relevant:

(Presuming the "sink.arpa." thing succeeds, big presumption I realize...)

So, how about using sink.arpa. as a(n) MNAME?

Or perhaps, one of the hosts listed in AS112?

Maybe a new AS112 entry that resolves to one of the IP addresses mentioned =
already (127.0.0.1 and friends)?
(Too bad there isn't a reserved IP address that definitively goes to /dev/n=
ull locally. Or is there?)

Does an MNAME really need to be fully qualified?

Cute idea:  use the "search" of non-fully-qualified names, to direct bad UP=
DATE traffic to a very local server, e.g. "ns1" (no dot).

It would also be nice to have a place-holder in DNS that "resolves" (in the=
 loose sense) to an appropriate pre-defined "thing", like the default names=
erver for a client, or "yourself" for a resolver.

But I digress. :-)

Brian

-----Original Message-----

> When I attempted to document a similar idea (using an empty label in the =
=3D
> MNAME field of an SOA record in order to avoid unwanted DNS UPDATE =3D
> traffic) the consensus of the room was that the idea was both =3D
> controversial and bad :-)
>=20
> http://tools.ietf.org/html/draft-jabley-dnsop-missing-mname-00

Well UPDATE traffic is supposed to go to the nameservers listed in
the NS RRset prefering the MNAME if and only if the MNAME is a
nameserver.  Lots of update clients don't do it quite right but
there are some that actually send to all the nameservers.

Setting the MNAME to "." does not actually address the problem.

Mark

> Joe
>=20
>=20
--=20
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org



home help back first fref pref prev next nref lref last post