Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

CNAME_lookup_failed_temporarily._(#4.4.3)

1,157 views
Skip to first unread message

Michael DiMartino

unread,
Mar 4, 2011, 10:42:10 AM3/4/11
to
Qmail Users

All mail delivers accept mail to *@hudsonstreet.us.  How can this be corrected?

2011-03-04 10:36:13.063166500 new msg 1757690
2011-03-04 10:36:13.063169500 info msg 1757690: bytes 459 from <ro...@monitor.hudsonstreet.us> qp 14415 uid 509
2011-03-04 10:36:13.064262500 starting delivery 4: msg 1757690 to remote ad...@hudsonstreet.us
2011-03-04 10:36:13.064264500 status: local 0/10 remote 2/20
2011-03-04 10:36:13.156432500 delivery 4: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/



Philippe Ratté

unread,
Mar 4, 2011, 11:48:24 AM3/4/11
to
Hello Michael,

You will most likely need the "oversize DNS patch"

See http://www.memoryhole.net/qmail/#oversize-dns

Available here: http://www.ckdhr.com/ckd/qmail-103.patch

-----Message d'origine-----
De : Michael DiMartino [mailto:mic...@hudsonstreet.us]
Envoyé : Friday, March 04, 2011 10:42 AM
À : qmail List
Objet : CNAME_lookup_failed_temporarily._(#4.4.3)

Qmail Users

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de

Davis Sylvester

unread,
Mar 4, 2011, 12:40:42 PM3/4/11
to
I fixed this issue by installing and running DNScache.

Point your email server's DNS entry (etc/resolv.conf) to the cache server.

This should fix the problem.  Follow the instruction at http://cr.yp.to/djbdns/dnscache.html to install the DNSCache server.

Hope this helps!

2011/3/4 Philippe Ratté <pra...@cybergeneration.com>

Andy Bradford

unread,
Mar 4, 2011, 10:36:45 PM3/4/11
to
Thus said Michael DiMartino on Fri, 04 Mar 2011 10:42:10 EST:

> All mail delivers accept mail to *@hudsonstreet.us. How can this be
> corrected?

I see you're using Google as your MX. Maybe they have some kind of
problem with their DNS records. The response they send back is only 361
bytes:

$ dnsq any hudsonstreet.us 64.98.148.13
255 hudsonstreet.us:
361 bytes, 1+11+0+2 records, response, authoritative, noerror
query: 255 hudsonstreet.us
answer: hudsonstreet.us 900 MX 30 aspmx2.googlemail.com
answer: hudsonstreet.us 900 MX 20 alt2.aspmx.l.google.com
answer: hudsonstreet.us 900 NS ns1.hover.com
answer: hudsonstreet.us 900 NS ns2.hover.com
answer: hudsonstreet.us 900 MX 10 aspmx.l.google.com
answer: hudsonstreet.us 900 MX 30 aspmx5.googlemail.com
answer: hudsonstreet.us 900 MX 30 aspmx3.googlemail.com
answer: hudsonstreet.us 900 A 66.96.147.113
answer: hudsonstreet.us 900 MX 30 aspmx4.googlemail.com
answer: hudsonstreet.us 900 MX 20 alt1.aspmx.l.google.com
answer: hudsonstreet.us 900 SOA ns1.hover.com dnsmaster.hover.com 1298818084 10800 3600 604800 900
additional: ns2.hover.com 900 A 64.98.148.13
additional: ns1.hover.com 900 A 216.40.47.26

This is not nearly enough data to trigger any DNS problems. By the way,
if you get this email, then clearly it is not a DNS problem with
qmail/djbdns. I run qmail (no DNS patches) and dnscache (unpatched) and
have no problems.

Andy

0 new messages