"Daniel Buchholz" <buchholz@???> writes:
[...]
> 2000-03-19 07:02:04 rejected MAIL FROM: temporarily unable to verify sender
> address (try again later) <mailings@???> H=(testprod.rzmi.gmx.net)
> [194.221.183.17]
[...]
> Does this say that mailings@??? does not exist?
michael@??? replies:
>
> I think it is probably related to:
>
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx12.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx13.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx0.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx1.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx2.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx3.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx4.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx5.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx6.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx7.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx8.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx9.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx10.gmx.net) All possible A RR's lame
> Mar 20 00:00:53 mx0 named[9373]: sysquery: query(mx11.gmx.net) All possible A RR's lame
Well, maybe its changing minute by minute, but what I see is that gmx.net
is delegated to NS3.FREESERVERS.COM [209.210.67.153] & NS4.FREESERVERS.COM
[209.210.67.154] {aside: I bet there's *no* real redundancy in that
configuration at all}, and they are both in the state of believing
that they are *not* authoritative for gmx.net. So one gets the quite
familiar effect that a non-recursive lookup returns a referral to
themselves:
; <<>> DiG 2.1 <<>> +norecurse mx gmx.net. @209.210.67.153
;; res options: init defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr ra; Ques: 1, Ans: 0, Auth: 2, Addit: 2
;; QUESTIONS:
;; gmx.net, type = MX, class = IN
;; AUTHORITY RECORDS:
gmx.net. 1331 NS NS3.FREESERVERS.COM.
gmx.net. 1331 NS NS4.FREESERVERS.COM.
;; ADDITIONAL RECORDS:
NS3.FREESERVERS.COM. 42562 A 209.210.67.153
NS4.FREESERVERS.COM. 35485 A 209.210.67.154
while a recursive lookup gives a SERVFAIL:
; <<>> DiG 2.1 <<>> +recurse mx gmx.net. @209.210.67.153
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 10
;; flags: qr rd ra; Ques: 1, Ans: 0, Auth: 0, Addit: 0
;; QUESTIONS:
;; gmx.net, type = MX, class = IN
Anyway, before this descends into the pathology of the DNS, the original
poster should be reassured that it's a blunder in the setup for gmx.net,
and nothing to do with his Exim configuration (except in so far as he is
using verify_sender at all).
Chris Thompson University of Cambridge Computing Service,
Email: cet1@??? New Museums Site, Cambridge CB2 3QG,
Phone: +44 1223 334715 United Kingdom.
