[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] Sendmail weirdness excessive recursion
- Subject: Re: [cobalt-developers] Sendmail weirdness excessive recursion
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Fri Mar 29 16:52:08 2002
- Organization: nobaloney.net
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
Taco Scargo wrote:
> I am surprised that YOU don't check faq's and knowledgebases... this issue
> is clearly documented to point you to DNS ...
> Probably you are using CNAMES or don't have MX entries for the domain.
Taco, I honestly thought I'd covered the DNS issue in my post. I agree
I wanted control of the DNS for further testing, and I've made
arrangements for that. The DNS has been moved over to my servers, and
by tomorrow, when all the root-servers point to my nameserver, and I'm
using the same file for his domain that I use for hundreds of other,
working domains, we'll see if that fixes it.
The fact is that he's NOT using CNAMES and there IS an MX record. I'm
not sure I like the MX records; I've NEVER seen "@" symbol used on the
right side of a DNS record. However, there's nothing in RFC 1035 that
will disallow it. I know that doesn't mean that BIND implements it the
way I read RFC 1035, which is why I'm hoping that you're right and my
hosting the DNS resolves the problem.
Here's a copy of his previous DNS (reformatted so it will look okay in
email clients using 80 column screens and non-proportional fonts); it
looks ok to me except for the aforementioned issue of the "@" on the
right side of the MX record.
$TTL 86400
@ IN SOA ns3.safepages.com. postmaster.safepages.com. (
1 ; Serial
10800 ; Refresh after 3 hours
3600 ; Retry after 1 hour
604800 ; Expire after 1 week
86400 ) ; Minimum TTL of 1 day
IN NS ns3.safepages.com.
IN NS ns4.safepages.com.
IN A 207.224.22.148
IN MX 10 @
localhost IN A 27.0.0.1
;
pop IN CNAME @
smtp IN CNAME @
www IN CNAME @
ftp IN CNAME @
While there ARE CNAME records, none of them should affect the mail
delivery; MX points to the domain and the domain is represented by an A
record.
Thanks for your suggestion, but I really don't think it's the issue.
Unless the "@" implementation isn't as written in RFC 1035.
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Linux and Cobalt/Sun/RaQ Consulting
nobaloney.net
P. O. Box 52672, Riverside, CA 92517
voice: (909) 778-9980 * fax: (702) 548-9484