public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Henning P. Schmiedehausen" <hps@tanstaafl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: DNS goofups galore...
Date: Tue, 13 Feb 2001 20:39:52 +0000 (UTC)	[thread overview]
Message-ID: <96c62o$o69$1@forge.intermeta.de> (raw)
In-Reply-To: <968mjv$l9t$1@forge.intermeta.de>, <7vh2HM81w-B@khms.westfalen.de>

kaih@khms.westfalen.de (Kai Henningsen) writes:

>hps@tanstaafl.de (Henning P. Schmiedehausen)  wrote on 12.02.01 in <968mjv$l9t$1@forge.intermeta.de>:

>> jan.gyselinck@be.uu.net (Jan Gyselinck) writes:
>>
>> >There's not really something wrong with MX's pointing to CNAME's.  It's
>> >just that some mailservers could (can?) not handle this.  So if you want to
>> >be able to receive mail from all kinds of mailservers, don't use CNAME's
>> >for MX's.
>>
>> No. It breaks a basic assumption set in stone in RFC821. It has
>> nothing to do with mailer software.

>May I point out that RFC 821 does not mention either CNAME or MX anywhere.

RFC 974 is about the "DOMAIN NAME SYSTEM". RFC 821 mentions DOMAINS:

3.7.  DOMAINS

>So don't tell us about stuff set in stone in RFC XYZ, when it's plain  
>you've never looked at that RFC.

Says who? RFC974 is a clarification of how to interpret Domain Name
System contents in a mail context. RFC821 makes a clear statement about
Domains in section 3.7:

[...]
      Whenever domain names are used in SMTP only the official names are
      used, the use of nicknames or aliases is not allowed.
[...]

and in RFC974 it is stated:

[...]
   In addition to mail information, the servers store certain other
   types of RR's which mailers may encounter or choose to use.  These
   are: the canonical name (CNAME) RR, which simply states that the
   domain name queried for is actually an alias for another domain name,
   which is the proper, or canonical, name; [...]
[...]

In my understanding (and I assume that you're familiar with both as
you've chosen to insult me by suggesting that I've not read this
stuff), this means clearly:

"YOU MUST NOT USE AN ALIAS WHENEVER DOMAINS ARE USED IN SMTP". (RFC821)

and

"THIS NAME IS AN ALIAS FOR ANOTHER DOMAIN NAME, WHICH IS THE PROPER,
CANONICAL NAME".

This boils down for me to 

"YOU MUST NOT USE A CNAME ANYWHERE IN SMTP".

and "ANYWHERE" also states for me "in the 220 greeting".

Any further questions?

	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   

  reply	other threads:[~2001-02-13 20: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
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 [this message]
     [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='96c62o$o69$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