From: Johannes Erdfelt <johannes@erdfelt.com>
To: "Michael H. Warfield" <mhw@wittsend.com>, linux-kernel@vger.kernel.org
Subject: Re: DNS goofups galore...
Date: Thu, 8 Feb 2001 19:43:33 -0500 [thread overview]
Message-ID: <20010208194332.Y23514@sventech.com> (raw)
In-Reply-To: <95ulrk$aik$1@forge.intermeta.de> <Pine.LNX.4.10.10102081346001.16513-100000@innerfire.net> <95v8am$k6o$1@cesium.transmeta.com> <20010208183232.A1642@alcove.wittsend.com> <3A833005.5C8E0D81@transmeta.com> <20010208185449.B1642@alcove.wittsend.com> <3A83335A.A5764CD7@transmeta.com> <20010208190823.B1640@alcove.wittsend.com> <3A8335BB.F3166F1@transmeta.com> <20010208193120.C1640@alcove.wittsend.com>
In-Reply-To: <20010208193120.C1640@alcove.wittsend.com>; from Michael H. Warfield on Thu, Feb 08, 2001 at 07:31:20PM -0500
On Thu, Feb 08, 2001, Michael H. Warfield <mhw@wittsend.com> wrote:
> But, wait a minute. CNAME -> CNAME is a "must not". MX -> CNAME
> is a "should not". The "should not" leaves it to be implimentation
> dependent and not an outright ban. Sooo...
Actually, I had this conversation recently. I checked a variety of
places and I couldn't find an RFC that said CNAME -> CNAME is a "must
not". In fact I found this snippet in rfc1912 which seems to imply that
it is legal:
Also, having chained records such as CNAMEs pointing to CNAMEs may
make administration issues easier, but is known to tickle bugs in
some resolvers that fail to check loops correctly. As a result some
hosts may not be able to resolve such names.
*shrug*
JE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-09 0:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 13:06 DNS goofups galore Matti Aarnio
2001-02-08 13:35 ` Mr. James W. Laferriere
2001-02-08 17:43 ` Henning P. Schmiedehausen
2001-02-08 21:46 ` Gerhard Mack
2001-02-08 22:58 ` H. Peter Anvin
2001-02-08 23:32 ` Michael H. Warfield
2001-02-08 23:47 ` H. Peter Anvin
2001-02-08 23:54 ` Michael H. Warfield
2001-02-09 0:01 ` H. Peter Anvin
2001-02-09 0:08 ` Michael H. Warfield
2001-02-09 0:11 ` H. Peter Anvin
2001-02-09 0:31 ` Michael H. Warfield
2001-02-09 0:43 ` Johannes Erdfelt [this message]
2001-02-12 12:55 ` Henning P. Schmiedehausen
2001-02-12 19:19 ` James Antill
2001-02-13 19:52 ` Henning P. Schmiedehausen
2001-02-20 23:45 ` James Antill
2001-02-09 7:04 ` Jan Gyselinck
2001-02-12 12:57 ` Henning P. Schmiedehausen
2001-02-12 20:20 ` Kai Henningsen
2001-02-13 20:39 ` Henning P. Schmiedehausen
[not found] <linux.kernel.20010208193120.C1640@alcove.wittsend.com>
2001-02-09 1:50 ` Aaron Denney
2001-02-09 3:05 ` Michael H. Warfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010208194332.Y23514@sventech.com \
--to=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhw@wittsend.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox