On Thu, 29 Dec 2005 18:52:40 -0500, Pete Weiss <[log in to unmask]> wrote: >Though I am by no means a DNS guru, I see that three DNSes have been defined for CCSI.COM via WHOIS: > >Domain servers in listed order: > > INFINITY.CCSI.COM 216.236.168.2 > QUEST.CCSI.COM 216.236.168.11 > DNS1.NEKSUS.COM 203.76.96.4 > >The last one (dns1.neksus.com) does NOT respond. A colleague wrote me the following: -------------- A quick lookup of the MX for CCSI.COM shows this: ;; ANSWER SECTION: ccsi.com. 300 IN MX 1 superkill.ccsi.com. ;; AUTHORITY SECTION: ccsi.com. 23996 IN NS quest.ccsi.com. ccsi.com. 23996 IN NS infinity.ccsi.com. ccsi.com. 23996 IN NS dns1.neksus.com. ;; ADDITIONAL SECTION: superkill.ccsi.com. 300 IN A 216.236.168.136 superkill.ccsi.com. 300 IN A 216.236.160.11 Note that superkill.ccsi.com has two IP addresses assigned to it. When I performed a reverse-lookup of those IPs, this is what I got: ;; ANSWER SECTION: 136.168.236.216.in-addr.arpa. 86400 IN PTR spamkiller.ccsi.com. - and - ;; ANSWER SECTION: 11.160.236.216.in-addr.arpa. 86400 IN PTR backup.ccsi.com. -------------- A primary mail server responds at the first IP 220 spamkiller.ccsi.com ESMTP Sendmail 8.13.1/8.13.5; Mon, 2 Jan 2006 15:33:57 -0600 Interestingly, a mail server also responds at 216.236.168.11 (the same IP as the nameserver quest.ccsi.com) 220 ccsi.com ESMTP Sendmail 8.12.10/8.12.6; Mon, 2 Jan 2006 15:38:21 -0600 (CST) This lead to a possible conlusion that the A record for backup.ccsi.com had been "fat-fingered" and was just plain wrong. No mail server has answered at that FQDN/IP for several days. But a mail server is answering there now: 220 backup.ccsi.com ESMTP Sendmail 8.12.11/8.12.11; Mon, 2 Jan 2006 15:35:22 -0600 (CST) Hopefully your mail problems with CCSI are now over.