From: "Henning P. Schmiedehausen" <hps@tanstaafl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: DNS goofups galore...
Date: Mon, 12 Feb 2001 12:55:41 +0000 (UTC) [thread overview]
Message-ID: <968mgd$l8m$1@forge.intermeta.de> (raw)
In-Reply-To: <95ulrk$aik$1@forge.intermeta.de>, <3A83335A.A5764CD7@transmeta.com>
hpa@transmeta.com (H. Peter Anvin) writes:
>> 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.
>>
>There is no reducibility problem for MX -> CNAME, unlike the CNAME ->
>CNAME case.
>Please explain how there is any different between an CNAME or MX pointing
>to an A record in a different SOA versus an MX pointing to a CNAME
>pointing to an A record where at least one pair is local (same SOA).
CNAME is the "canonical name" of a host. Not an alias. There is good
decriptions for the problem with this in the bat book. Basically it
breaks if your mailer expects one host on the other side (mail.foo.org)
and suddently the host reports as mail.bar.org). The sender is
allowed to assume that the name reported after the "220" greeting
matches the name in the MX. This is impossible with a CNAME:
mail.foo.org. IN A 1.2.3.4
mail.bar.org. IN CNAME mail.foo.org.
bar.org. IN MX 10 mail.bar.org.
% telnet mail.bar.org smtp
220 mail.foo.org ESMTP ready
^^^^^^^^^^^^
This kills loop detection. Yes, it is done this way =%-) and it breaks
if done wrong.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
-
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-12 12:58 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
2001-02-12 12:55 ` Henning P. Schmiedehausen [this message]
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='968mgd$l8m$1@forge.intermeta.de' \
--to=hps@tanstaafl.de \
--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