Actually, the problem is not that they left out the domain, but that
they tacked a period on, which prevents the NS at their end from
automatically adding the current origin domain, and forces it to be
treated as literally 'mail'. Once you local resolver goes to look that
up, all it can qualify it with locally is your domain. Actually, there
is a workaround for this.. Set the following false in your SMTP
transport..
dns_qualify_single Type: boolean Default: true
If the "hosts" or "fallback_hosts" option is being used and names are
being looked up in the DNS, the option to cause the resolver to qualify
single-component names with the local domain is set.
$ dig worldclasssportfishing.net mx
; <<>> DiG 8.2 <<>> worldclasssportfishing.net mx
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUERY SECTION:
;; worldclasssportfishing.net, type = MX, class = IN
;; ANSWER SECTION:
worldclasssportfishing.net. 1D IN MX 30 mail.
;; AUTHORITY SECTION:
worldclasssportfishing.net. 1D IN NS ns1.host207.com.
worldclasssportfishing.net. 1D IN NS ns2.host207.com.
;; ADDITIONAL SECTION:
ns1.host207.com. 1D IN A 207.218.238.22
ns2.host207.com. 1D IN A 207.218.238.126
;; Total query time: 138 msec
;; FROM: newfoundland.pathwaynet.com to SERVER: default -- 216.46.200.1
;; WHEN: Mon Dec 3 16:51:04 2001
;; MSG SIZE sent: 44 rcvd: 143
On Mon, 3 Dec 2001, Marc MERLIN wrote:
> On Mon, Dec 03, 2001 at 02:57:54PM -0500, ScaryG wrote:
> > > panoramix:/etc/mail# host -t MX worldclasssportfishing.net
> > > worldclasssportfishing.net MX 30 mail
> > > !!! worldclasssportfishing.net MX host mail is not canonical
> >
> > Looks like the problem is an incorrect entry in the zone's DNS.
> >
> > Missing something (like the rest of the domain after mail)
> >
> > Change the MX record record to read
> >
> > worldclasssportfishing.net. IN MX 30
> > mail.worldclasssportfishing.net.
> >
> > notice the trailing periods ;-)
>
> I understand the problem very well, but it's not my zone :-)
>
> I'm contacting the people who own it, but I shouldn't have to deal with 200+
> frozen Emails because someone is serving a bad zone (and the part that
> confuses me is that with bind, if you set "mail" in the zone, it will add
> the origin, which typically is the domain in the zone, so I'm surprised to
> see "mail" all by itself (maybe they actually added a trailing dot)).
>
> I'm somehow hoping that there is a way for exim or the resolver to not try
> to deliver a mail if the MX is an unqualified hostname.
>
> Marc
>
--
