host lookup verification of failed
in [Postfix]
|
Prev: M.A.R.L.B.O.R.O...F.O.R...11.99...P.E.R...C.A.R.T.O.N.....gllI4MDlQsytu
Next: Address extension and 550-Mailbox unknown
From: Kevin Audleman on 29 Aug 2007 18:38 Hi, I was wondering if anybody could help me figure out why email from our domain, yesmagazine.org, is being blocked, but only by two companies, both schools. Here are the messages I receive when I try to send them an email: School 1 Received: 550 5.7.1 Fix reverse DNS for 67.40.31.37 School 2 Received: 550 5.7.1 E410 host lookup verification of 67.40.31.37 failed My domain is yesmagazine.org, we do in fact have a Reverse DNS record set up for 67.40.31.37, and it is accepted by most domains. The only thing I can think of is that these institutions are doing an A record lookup on the response from the ReverseDNS lookup. The A record points to our website, which is a different server, so it would fail. If that's the case, I don't know how to fix it. Any help greatly appreciated. Kevin
From: ivakras1 on 30 Aug 2007 03:38 On 30 , 02:38, Kevin Audleman <kevin.audle...(a)gmail.com> wrote: > Hi, I was wondering if anybody could help me figure out why email from > our domain, yesmagazine.org, is being blocked, but only by two > companies, both schools. Here are the messages I receive when I try to > send them an email: > > School 1 > Received: 550 5.7.1 Fix reverse DNS for 67.40.31.37 > School 2 > Received: 550 5.7.1 E410 host lookup verification of 67.40.31.37 > failed > > My domain is yesmagazine.org, we do in fact have a Reverse DNS record > set up for 67.40.31.37, and it is accepted by most domains. > > The only thing I can think of is that these institutions are doing an > A record lookup on the response from the ReverseDNS lookup. The A > record points to our website, which is a different server, so it would > fail. If that's the case, I don't know how to fix it. > > Any help greatly appreciated. > > Kevin check this for warnings and errors: http://www.dnsstuff.com/tools/dnsreport.ch?domain=yesmagazine.org also `dig` output... ## dig -t any yesmagazine.org ; <<>> DiG 9.3.1 <<>> -t any yesmagazine.org ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59291 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;yesmagazine.org. IN ANY ;; ANSWER SECTION: yesmagazine.org. 86400 IN NS ns1.webcontrolcenter.com. yesmagazine.org. 86400 IN NS ns2.webcontrolcenter.com. ;; AUTHORITY SECTION: yesmagazine.org. 86400 IN NS ns1.webcontrolcenter.com. yesmagazine.org. 86400 IN NS ns2.webcontrolcenter.com. ;; Query time: 424 msec ;; SERVER: 89.179.51.5#53(89.179.51.5) ;; WHEN: Thu Aug 30 11:33:19 2007 ;; MSG SIZE rcvd: 117
From: Kevin Audleman on 30 Aug 2007 12:12 Dmitry, thanks for your response. Does anything stand out to you as incorrect? The DNS report has a few warnings, but none of them seem to be particularly troublesome. The dig shows me what my DNS settings are, but I can't tell from that why a handful of domains are telling me my ReverseDNS is incorrect. Kevin
From: ivakras1 on 4 Sep 2007 00:52
On 30 , 20:12, Kevin Audleman <kevin.audle...(a)gmail.com> wrote: > Dmitry, thanks for your response. Does anything stand out to you as > incorrect? The DNS report has a few warnings, but none of them seem to > be particularly troublesome. The dig shows me what my DNS settings > are, but I can't tell from that why a handful of domains are telling > me my ReverseDNS is incorrect. > > Kevin Yes. It seems yesmagazine.org does not have MX record on DNS. The answer section shows it ;;ANSWER SECTION: yesmagazine.org. 86400 IN NS ns1.webcontrolcenter.com. yesmagazine.org. 86400 IN NS ns2.webcontrolcenter.com. and thats all! dnsstuff.com report: "FAIL Connect to mail servers ERROR: I could not complete a connection to one or more of your mailservers" MX record in DNS (must resolv in both directions) sould solve the problem... Sorry for my english. |