On Thu, 9 Apr 1998, Christopher Purnell wrote:
> 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.
Exim should bounce the record. I have just re-tested that this works (I
have testing MX records set up for this purpose). I got the error
all relevant MX records point to non-existent hosts
> The result of this is to bring our mail machines to a halt such that
> they need to be rebooted by external means.
There is a difference for form.com.sg because exim -bt says
x@???
deliver to x@???
router = lookuphost, transport = smtp
host form-nt.form.com.sg [202.42.229.2] MX=0
host form.com.sg MX=1
It should have got rid of the non-existent one. I will investigate and
see what's going on.
On Thu, 9 Apr 1998, Greg A. Woods wrote:
> I'm not surprised if Exim goes into a loop trying to find one -- I would
> too!
It shouldn't loop!
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
--
*** Exim information can be found at
http://www.exim.org/ ***
