From: "Michael H. Warfield" <mhw@wittsend.com>
To: "H. Peter Anvin" <hpa@transmeta.com>
Cc: "Michael H. Warfield" <mhw@wittsend.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: DNS goofups galore...
Date: Thu, 8 Feb 2001 18:54:49 -0500 [thread overview]
Message-ID: <20010208185449.B1642@alcove.wittsend.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>
In-Reply-To: <3A833005.5C8E0D81@transmeta.com>; from hpa@transmeta.com on Thu, Feb 08, 2001 at 03:47:17PM -0800
On Thu, Feb 08, 2001 at 03:47:17PM -0800, H. Peter Anvin wrote:
> "Michael H. Warfield" wrote:
> >
> > On Thu, Feb 08, 2001 at 02:58:30PM -0800, H. Peter Anvin wrote:
> > > Followup to: <Pine.LNX.4.10.10102081346001.16513-100000@innerfire.net>
> > > By author: Gerhard Mack <gmack@innerfire.net>
> > > In newsgroup: linux.dev.kernel
> > > >
> > > > Thanklfully bind 9 barfs if you even try this sort of thing.
> > > >
> >
> > > Personally I find it puzzling what's wrong with MX -> CNAME at all; it
> > > seems like a useful setup without the pitfalls that either NS -> CNAME
> > > or CNAME -> CNAME can cause (NS -> CNAME can trivially result in
> > > irreducible situations; CNAME -> CNAME would require a link maximum
> > > count which could result in obscure breakage.)
> >
> > It generally forces another DNS lookup. If you do a resolve on
> > a name of type=ANY it returns any MX records and A records. If you then
> > do a resolve on the MX records, you then get a CNAME and then have to
> > add an additional lookup for the CNAME. If you have a lot of MX records
> > and not all the servers are "up" that can add up to a significant
> > increase in DNS traffic.
> >
> Wouldn't that be true for any CNAME anyway?
That's the point...
In other words, you do a lookup, you start with a primary lookup
and then possibly a second lookup to resolve an MX or CNAME. It's only
the MX that points to a CNAME that results in yet another lookup. An
MX pointing to a CNAME is almost (almost, but not quite) as bad as a
CNAME pointing to a CNAME.
> -hpa
> --
> <hpa@transmeta.com> at work, <hpa@zytor.com> in private!
> "Unix gives you enough rope to shoot yourself in the foot."
> http://www.zytor.com/~hpa/puzzle.txt
Mike
--
Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com
(The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
-
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-08 23:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 13:06 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 [this message]
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
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=20010208185449.B1642@alcove.wittsend.com \
--to=mhw@wittsend.com \
--cc=hpa@transmeta.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®