I can't argue with the point about replacing your resolver if it handles
an anomaly better -- but IME, BIND handles "oddities" far better than PDNS.
I still say:
- If you're a newbie, or just want it to work "hands off, out of the
box" then pdns-resolver will not steer you wrong -- it's a good product!
- If you're experienced with BIND, or want to learn DNS (or have some
odd DNS requirements), then BIND is the "definitive" DNS server (and one
of the most efficient caching-resolvers out there)
But I will add (as a final comment) that CNAME lookup failures are
USUALLY that the CNAME points to something that doesn't resolve.
mail.qmailtoaster.com CNAME mailsterver.qmailtoaster.com
mailserver.qmailtoaster.com IN A 1.1.1.1
See the break? (mailsterver is not mailserver)...
This will get you a CNAME lookup failure message...
Hope this helps!
Dan
IT4SOHO
On 9/6/2013 12:58 PM, Eric Shubert wrote:
A CNAME lookup failure isn't necessarily due to an MX pointing to a
CNAME record. Or is it? This would be easy for us to check if Chandran
had posted the domain name. Chandran, you really need to do a better
job of providing details such as this in order for us to help you
effectively.
Dan's suggestions are certainly appropriate. When I've identified a
domain with misconfigured DNS (typically a problem with rDNS), I
attempt to notify the domain's administrator (technical contact info
can be obtained from whois). They are usually grateful.
On the other hand, if changing the resolver your QMT uses improves
reliability by dealing effectively with some anomaly, why wouldn't you
want to make the change, especially if the anomaly is something
outside of your control?
--
PLEASE TAKE NOTE OF OUR NEW ADDRESS
===================================
IT4SOHO, LLC
33 - 4th Street N, Suite 211
St. Petersburg, FL 33701-3806
CALL TOLL FREE:
877-IT4SOHO
877-484-7646 Phone
727-647-7646 Local
727-490-4394 Fax
We have support plans for QMail!
