[ On Thu, April 9, 1998 at 17:28:20 (+0100), Christopher Purnell wrote: ]
> Subject: [EXIM] DNS
>
> To make it a little clearer what I'm talking about here is the result
> of an MX query for form.com.sg.
>
> ;; ANSWERS:
> form.com.sg. 395291 MX 1 form.com.sg. ;; THIS LINE
> form.com.sg. 395291 MX 0 form-nt.form.com.sg.
>
> ;; AUTHORITY RECORDS:
> form.com.sg. 81628 NS secdns.pacific.net.sg.
> form.com.sg. 81628 NS form-nt.form.com.sg.
>
> ;; ADDITIONAL RECORDS:
> form-nt.form.com.sg. 81628 A 202.42.229.2
> secdns.pacific.net.sg. 81628 A 203.120.90.90
>
> And there is no A record for form.com.sg.
But there *MUST* be (according to the DNS specification)! ;-)
I'm not surprised if Exim goes into a loop trying to find one -- I would
too!
The target of an MX must be a canonical hostname, i.e. a name with at
least one A RR.
Exim should probably bounce the message with a "host not found" error,
perhaps with some detail saying that the MX is broken. I suppose it
could also freeze the message and alert the postmaster so she an go and
bug the owner of the MX for a fix.
--
Greg A. Woods
+1 416 443-1734 VE3TCP <gwoods@???> <robohack!woods>
Planix, Inc. <woods@???>; Secrets of the Weird <woods@???>
--
*** Exim information can be found at
http://www.exim.org/ ***
