>Len, I am curious to see what happens if you dig on the following IP address >against VISI, as all come back with a positive response from VISI in just >the past few minutes: > >66.130.198.216
from the server seeing the failure: # dig 66.130.198.216.relays.visi.com ; <<>> DiG 8.3 <<>> 66.130.198.216.relays.visi.com ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 2 but from another IP: # dig 66.130.198.216.relays.visi.com ; <<>> DiG 9.2.3rc3 <<>> 66.130.198.216.relays.visi.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62561 and another: # dig 66.130.198.216.relays.visi.com ; <<>> DiG 9.2.1 <<>> 66.130.198.216.relays.visi.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60757 But on the MX that is seeing SERVAIL, it uses DNS on the machine 127.0.0.1 which works for all other RBLs and other DNS queries. looks like a connectivity pb. but mx1# dig @relays.visi.com 66.130.198.216.relays.visi.com ; <<>> DiG 8.3 <<>> @relays.visi.com 66.130.198.216.relays.visi.com ; Bad server: relays.visi.com -- using default server and timer opts but on on IP that gave nxdomain: tx1# dig @relays.visi.com 66.130.198.216.relays.visi.com ; <<>> DiG 9.2.3rc3 <<>> @relays.visi.com 66.130.198.216.relays.visi.com ;; global options: printcmd ;; connection timed out; no servers could be reached so something is definitely wrong with connectivity to visi or at relays.visi.com. Len
