Topic: CNAME_lookup_failed_temporarily._(#4.4.3)

[jhale1966]

All of a sudden I started getting this error when the SME Box tries to Email our Exchange Server.

It's been working for months prior to that. I've tried rebooting the SME box but that didn't do any good. :/

Any points in the right direction would be GREATLY appreciated.

[byte]

Has anything changed that you know of?

Also what is shown in /var/log/qmail/current and /var/log/qpsmtpd/current?

[jhale1966]

That's the problem - NOTHING has changed.

I didn't even update the 'website' that I'm running on that box.

[jhale1966]

Here are the messages from the logs:

QMail/Current:
2006-10-26 12:51:53.977977500 delivery 905: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/
2006-10-26 12:51:53.977985500 status: local 0/10 remote 3/20
2006-10-26 12:51:53.979817500 delivery 906: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/
2006-10-26 12:51:53.979822500 status: local 0/10 remote 2/20
2006-10-26 12:51:53.982818500 delivery 907: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/
2006-10-26 12:51:53.982822500 status: local 0/10 remote 1/20
2006-10-26 12:51:53.984817500 delivery 904: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/
2006-10-26 12:51:53.984820500 status: local 0/10 remote 0/20

QPSMTPD/Current:
Nothing listed for the times as they relate to the above.

[CharlieBrady]

2006-10-26 12:51:53.977977500 delivery 905: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/

A CNAME is a type of alias in DNS. Something is broken in the DNS records for whatever domain or server qmail is trying to send to.

[mike_mattos]

>>CNAME_lookup_failed_temporarily._(#4.4.3)/

>> Something is broken in the DNS records for whatever domain or server qmail is trying to send to.

I'm seeing the same message from a server trying to mail to msg.telus.com

similar SME server across town is resolving msg.telus.com properly, and  both servers use the same ISP but different IP groups at the ISP!

weirdly, at the failing site, a windows pc connected directly to the modem resolves properly, so the issue seems to be how SME gets its dns names is different from the method used by Windows.

[CharlieBrady]

>>CNAME_lookup_failed_temporarily._(#4.4.3)/

>> Something is broken in the DNS records for whatever domain or server qmail is trying to send to.

I'm seeing the same message from a server trying to mail to msg.telus.com

That seems unlikely, since msg.telus.com is not a CNAME.

As it says in many, many places on this site, if anything something doesn't work correctly, report it in detail via the Bug Tracker.

[mike_mattos]

Charlie, two sme servers have different results accessing the same site.  The failing site was OK until the ISP changed the IP to a new range of addresses, so it looks like the ISP has an issue. ( and it's been reported to both the ISP and to telus)

SInce I'm not the first person to experience this error, I'm hoping there is a work around that will benefit all of us, such as loading the IP of msg.telus.com somewhere on SME. ( like into a hosts file )

I don't see it as an SME bug, but I could be wrong!

[birolakbay]

hi,

in my case, it was firewall's IDS rules which resets DNS queries that is greater than 512 bytes. I shutdown ip audit functions and it is working perfectly now.

[raem]

mike_mattos

I think you and many others are missing Charlies and other developers point about posting potential issues to the bug tracker rather than to the forums.

Charlie doesn't want to and won't be (from what he says) tracking issues that are potential bugs (whatever their cause) via the forums.
He has said that he will track issues via the bug tracker.

If the issue you report turns out to be a non issue, then the bug is closed, if it turns out to be a real issue then it can be followed through (in the bug tracker) to whatever stage of finalisation is appropriate.

General questions eg how do I do this or that etc are of course appropriate to be asked in the forums.
Anything that has even a hint of being a bug or possible bug should be reported straight to the bug tracker, whatever its source or cause, as it may well be something that needs fixing or catering for in the sme code.

Any "bug type" reporting done in the forums is wasted effort as it will ultimately still need to be reported and resolved in the bug tracker if it is indeed a "real" bug.

As far as doing the basic reporting of an issue is concerned, I don't think the bug tracker is any harder to use than the forums. If you can logon and use the forums, then for sure you have the ability to create a user account and login to the bug tracker.