[157375] in North American Network Operators' Group
Re: DNS hostnames with a duplicate CNAME and A record - which should
daemon@ATHENA.MIT.EDU (William Herrin)
Wed Oct 17 16:01:25 2012
In-Reply-To: <CABgOHgs7Da6xMo5Zx4+a72hqPYpdMeautr+1=pTM06FPUi-sPw@mail.gmail.com>
From: William Herrin <bill@herrin.us>
Date: Wed, 17 Oct 2012 16:00:49 -0400
To: Landon Stewart <lstewart@superb.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, Oct 17, 2012 at 3:25 PM, Landon Stewart <lstewart@superb.net> wrote:
> The problem is that we have some zones that have records with the same
> hostname that have both a CNAME as well as an A record, MX record, SOA
> record and/or NS record. Is there an easy answer for what should be
> removed? I'm inclined to say that the CNAME should be removed in all these
> cases but I can't find any definitive information on this and after doing
> some tests it doesn't always seem straightforward.
If you have a CNAME record for a particular name, you should not have
any other record of any type for that same name. Which you should
remove depends on the details of the particular circumstance. If you
really mean "identical to that other name with respect to all records
and record types" then there's nothing inherently wrong with the
CNAME. If you don't, then you shouldn't use a CNAME there.
Regards,
Bill Herrin
--
William D. Herrin ................ herrin@dirtside.com bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004
