[34059] in North American Network Operators' Group
RE: How common is lack of DNS server diversity?
daemon@ATHENA.MIT.EDU (Roeland Meyer)
Sat Jan 27 18:02:22 2001
Message-ID: <9DC8BBAD4FF100408FC7D18D1F092286039BA4@condor.mhsc.com>
From: Roeland Meyer <rmeyer@mhsc.com>
To: "'Havard.Eidnes@runit.sintef.no'" <Havard.Eidnes@runit.sintef.no>,
Roeland Meyer <rmeyer@mhsc.com>
Cc: bmanning@vacation.karoshi.com, joshua@roughtrade.net,
nanog@merit.edu
Date: Sat, 27 Jan 2001 14:40:39 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Errors-To: owner-nanog-outgoing@merit.edu
Then, how do you intelligently talk about the other entities I bring =
up?
BTW, I didn't invent some of this. The semantic need exists and because =
of
resistance to further definition, folks are making their own semantics =
to
fill the vacume. You really ought to look at what MSFT uses for DDNS
semantics, it is a nightmare. The reason that they came up with their =
own,
is because there were no pre-existing semantics that would cover the
concepts. MHSC, ORSC, and I suspect uDNS, had to do the same thing. One
resultant is, that we have conflicting semantics.
ref: what I said about routing around the problem.
Denial is not a river in Egypt and won't make the problem go away.
> -----Original Message-----
> From: Havard.Eidnes@runit.sintef.no
> [mailto:Havard.Eidnes@runit.sintef.no]
> Sent: Saturday, January 27, 2001 2:29 PM
> To: rmeyer@mhsc.com
> Cc: bmanning@vacation.karoshi.com; joshua@roughtrade.net;
> nanog@merit.edu
> Subject: Re: How common is lack of DNS server diversity?
>=20
>=20
>=20
> > <Root server> ::=3D Any DNS server that has final authority for a
> > <domain tier/level>;
>=20
> That's what's commonly referred to as an "authoritative name
> server" for the zone in question.
>=20
> I'll side with Bill M: a "root DNS name server" serves the root
> zone, aka. ".".
>=20
> Regards,
>=20
> - H=E5vard
>=20
