Re: Still getting CNAME_lookup_failed_temporarily errors
Hi again I've finally managed to convince qmail to send my mail. The problem was, as Armando suspected, a library incompatibility. What I tried first was to move qmail to another machine with a more elaborate setup. No luck there - the CNAME error persisted. The next thing I did was to install a compiler on that machine and compile qmail locally. That version worked great. This is a bit strange though. On all the machines, I'm using the same version of the libraries qmail uses (libc and libresolv). The only difference I can see is the hex number that is displayed by ldd in parentheses after the version number. I know this is a bit off-topic, but what does that number mean? Anyway, the problem seems to be solved and I would like to thank you guys, especially Armando and Holborn, for all your help. Thanks, Jens
Re: Still getting CNAME_lookup_failed_temporarily errors
>From: "asantos" <[EMAIL PROTECTED]> > >A ldd qmail-remote on my machine gives me: > >libresolv.so.2 => /lib/libresolv.so.2 (0x40019000) >libc.so.6 => /lib/libc.so.6 (0x40027000) >/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) > >I bet you a eider feather against a authentic Sakenussem scroll that your >problem is right there on the first line: different versions of libresolv. > ldd qmail-remote on triton gives libresolv.so.2 => /lib/libresolv.so.2 (0x40015000) libc.so.6 => /lib/libc.so.6 (0x40025000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) ldd qmail-remote on the machine I compiled it gives libresolv.so.2 => /lib/libresolv.so.2 (0x40018000) libc.so.6 => /lib/libc.so.6 (0x40028000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) Running ldd -v shows the same version numbers on both systems. I'll try and move qmail to another machine that is more similar to the one I compiled it on and see how it runs there. Thanks, Jens Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: Still getting CNAME_lookup_failed_temporarily errors
asantos wrote: > I bet you a eider feather against a authentic Sakenussem scroll that your > problem is right there on the first line: different versions of libresolv. Agreed. After confirming his resolv was setup and functioning, I suggested a recompile (if on the same box) without and LD_LIBRARY_PATH and after rerunning ldocnfig as root (he was on Linux so no need for the -R :) Failing that a truss/strace and actually see what it's up to. Regards, D.
Re: Still getting CNAME_lookup_failed_temporarily errors
From: Jens Hafsteinsson <[EMAIL PROTECTED]> >>Did you install qmail from source or using a binary package? >> > >From source, but compiled on a different machine (the user and group match). Right. A ldd qmail-remote on my machine gives me: libresolv.so.2 => /lib/libresolv.so.2 (0x40019000) libc.so.6 => /lib/libc.so.6 (0x40027000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) I bet you a eider feather against a authentic Sakenussem scroll that your problem is right there on the first line: different versions of libresolv. Armando
Re: Still getting CNAME_lookup_failed_temporarily errors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1 Aug 00, at 3:42, Chris, the Young One wrote: > At the moment though, as far as I know, the messages get sent pretty > much straight after preprocessing. Just how do you get the messages > ``reinjected''? For example by a smtproutes entry pointing back at yourself. (Be careful about rcpthosts or RELAYCLIENT in that case; you don't want to bounce the message during reinjection, do you?) -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOYWSMlMwP8g7qbw/EQJDhgCfaHTdaaewRJ5UYpXQjNaaYX2Ti/AAn0Km UXztdJ0vkYlHpAVO1Ug0a0fB =RGZE -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: Still getting CNAME_lookup_failed_temporarily errors
On Mon, Jul 31, 2000 at 05:33:39PM +0200, Petr Novotny wrote: ! No, it's done by qmail-send. (qmail-queue writes the message into ! the queue and pulls the trigger; that's all.) Having just peek at INTERNALS again, I agree. My mistake. ! DJB sais that qmail-2.0 will handle this situation better. (Like, you ! want to ditch all mails going to aol.com; once they're ! preprocessed, you can't just put aol.com in virtualdomains and ! /dev/null the messages locally; you must first re-inject the ! messages, so that local/remote decision is retried.) At the moment though, as far as I know, the messages get sent pretty much straight after preprocessing. Just how do you get the messages ``reinjected''? (Please don't tell me it's in the FAQ. :-)) ---Chris K. -- Chris, the Young One |_ but what's a dropped message between friends? Auckland, New Zealand |_ this is UDP, not TCP after all ;) ---John H. http://cloud9.hedgee.com/ |_ Robinson, IV PGP: 0xCCC6114E/0x706A6AAD |_
Re: Still getting CNAME_lookup_failed_temporarily errors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1 Aug 00, at 3:25, Chris, the Young One wrote: > If I remember right, preprocessing (which is done by qmail-queue) No, it's done by qmail-send. (qmail-queue writes the message into the queue and pulls the trigger; that's all.) > involves determining whether a message is local or remote. Yep. > ! Say that I now change > ! my setup in some way but that change isn't reflected in the old > ! messages in the queue as the have already been preprocessed, so next > ! time qmail tries to deliver them, they fail. > > This happens if you change /var/qmail/control/locals so that the > notion of what's local is changed. Other than that I can't see how > else it can happen. DJB sais that qmail-2.0 will handle this situation better. (Like, you want to ditch all mails going to aol.com; once they're preprocessed, you can't just put aol.com in virtualdomains and /dev/null the messages locally; you must first re-inject the messages, so that local/remote decision is retried.) -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOYWORFMwP8g7qbw/EQL7cgCgrWgAAC4wG/9c0OMGCsBff+RpwzwAoN+M v7oFujaricywPflsvlrgbJrv =bCXp -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: Still getting CNAME_lookup_failed_temporarily errors
On Mon, Jul 31, 2000 at 03:11:14PM +, Jens Hafsteinsson wrote: ! Yes. qmail-qstat says it has 0 preprocessed messages in the queue but 2 ! waiting to be sent. I was just wondering if qmail did some header building ! or something based on information it had at the time. If I remember right, preprocessing (which is done by qmail-queue) involves determining whether a message is local or remote. ! Say that I now change ! my setup in some way but that change isn't reflected in the old messages in ! the queue as the have already been preprocessed, so next time qmail tries to ! deliver them, they fail. This happens if you change /var/qmail/control/locals so that the notion of what's local is changed. Other than that I can't see how else it can happen. See INTERNALS in the qmail distribution. ---Chris K. -- Chris, the Young One |_ If you can't afford a backup system, you can't Auckland, New Zealand |_ afford to have important data on your computer. http://cloud9.hedgee.com/ |_ ---Tracy R. Reed PGP: 0xCCC6114E/0x706A6AAD |_
Re: Still getting CNAME_lookup_failed_temporarily errors
>From: Holborn BongMiester <[EMAIL PROTECTED]> > >Do you have an nsswitch.conf in your /etc/ dir? Make sure it has: > >hosts: files dns > >as the hosts line. This means it will first attempt to resolve the entry >in /etc/hosts if not it tries dns. The hosts line in nsswitch.conf reads: hosts: files nisplus nis dns I don't use NIS. > >Them in ya resolv.conf you'll want: > >nameserver 127.0.0.1 Ok. I had 'search axon.is' and 'nameserver 194.144.127.194'. Tried to also remove search but it didn't change anything. Now I only have 'nameserver 127.0.0.1'. > >That _should_ be your resolv set up correctly, what does nslookup -d -q=mx >abacus.com give? nslookup -d -q=mx abacus.com. ;; res_nmkquery(QUERY, 1.0.0.127.in-addr.arpa, IN, PTR) Got answer: HEADER: opcode = QUERY, id = 15582, rcode = NOERROR header flags: response, auth. answer, want recursion, recursion avail. questions = 1, answers = 1, authority records = 2, additional = 2 QUESTIONS: 1.0.0.127.in-addr.arpa, type = PTR, class = IN ANSWERS: -> 1.0.0.127.in-addr.arpa name = localhost ttl = 86400 (1D) AUTHORITY RECORDS: -> 0.0.127.in-addr.arpa nameserver = triton.axon.is ttl = 86400 (1D) -> 0.0.127.in-addr.arpa nameserver = sprettur.isnet.is ttl = 86400 (1D) ADDITIONAL RECORDS: -> triton.axon.is internet address = 194.144.127.194 ttl = 86400 (1D) -> sprettur.isnet.is internet address = 193.4.58.19 ttl = 15853 (4h24m13s) Server: localhost Address: 127.0.0.1 ;; res_nmkquery(QUERY, abacus.com, IN, MX) Got answer: HEADER: opcode = QUERY, id = 15583, rcode = NOERROR header flags: response, want recursion, recursion avail. questions = 1, answers = 2, authority records = 3, additional = 5 QUESTIONS: abacus.com, type = MX, class = IN ANSWERS: -> abacus.com preference = 10, mail exchanger = merc91.us.sas.com ttl = 28300 (7h51m40s) -> abacus.com preference = 10, mail exchanger = merc92.us.sas.com ttl = 28300 (7h51m40s) AUTHORITY RECORDS: -> abacus.com nameserver = LAMB.sas.com ttl = 172296 (1d23h51m36s) -> abacus.com nameserver = SCHAF.sas.com ttl = 172296 (1d23h51m36s) -> abacus.com nameserver = BLEAT.sas.com ttl = 172296 (1d23h51m36s) ADDITIONAL RECORDS: -> merc91.us.sas.com internet address = 149.173.6.1 ttl = 28398 (7h53m18s) -> merc92.us.sas.com internet address = 149.173.6.2 ttl = 28398 (7h53m18s) -> LAMB.sas.com internet address = 149.173.1.1 ttl = 172296 (1d23h51m36s) -> SCHAF.sas.com internet address = 212.185.185.19 ttl = 172296 (1d23h51m36s) -> BLEAT.sas.com internet address = 149.173.1.4 ttl = 172296 (1d23h51m36s) Non-authoritative answer: abacus.com preference = 10, mail exchanger = merc91.us.sas.com ttl = 28300 (7h51m40s) abacus.com preference = 10, mail exchanger = merc92.us.sas.com ttl = 28300 (7h51m40s) Authoritative answers can be found from: abacus.com nameserver = LAMB.sas.com ttl = 172296 (1d23h51m36s) abacus.com nameserver = SCHAF.sas.com ttl = 172296 (1d23h51m36s) abacus.com nameserver = BLEAT.sas.com ttl = 172296 (1d23h51m36s) merc91.us.sas.com internet address = 149.173.6.1 ttl = 28398 (7h53m18s) merc92.us.sas.com internet address = 149.173.6.2 ttl = 28398 (7h53m18s) LAMB.sas.com internet address = 149.173.1.1 ttl = 172296 (1d23h51m36s) SCHAF.sas.com internet address = 212.185.185.19 ttl = 172296 (1d23h51m36s) BLEAT.sas.com internet address = 149.173.1.4 ttl = 172296 (1d23h51m36s) > > > >So two waiting to go. > > > > I've clean the queue several times just to keep the log managable. These >are > > the most recent messages. > >*nods* I can imagine it's a bit of a nuisence :( > > > What kind of preprocessing does qmail do? > >Preprocessing? You mean before sending mail out 'to the world'? Yes. qmail-qstat says it has 0 preprocessed messages in the queue but 2 waiting to be sent. I was just wondering if qmail did some header building or something based on information it had at the time. Say that I now change my setup in some way but that change isn't reflected in the old messages in the queue as the have already been preprocessed, so next time qmail tries to deliver them, they fail. Jens Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: Still getting CNAME_lookup_failed_temporarily errors
>From: Holborn BongMiester <[EMAIL PROTECTED]> > > >You all may be barking up the wrong tree (there again, so could I > > >:). Whats the address that getting the CNAME lookup failure. > > > > I've tried several addresses, both local to my root domain and external. > > Example domains are dimon.is and abacus.com. All fail with the CNAME >error. > >Okay. What OS? At my end or theirs? My end is Linux (2.2.16, glibc 2.1.2) and dimon is Linux (version ?). I don't know about abacus. > > > >What does qmail-qstat give? > > > > > > > qmail-qstat gives the following: > > > > messages in queue: 2 > > messages in queue but not yet preprocessed: 0 > >So two waiting to go. I've clean the queue several times just to keep the log managable. These are the most recent messages. What kind of preprocessing does qmail do? Jens Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: Still getting CNAME_lookup_failed_temporarily errors
>From: Holborn BongMiester <[EMAIL PROTECTED]> > >You all may be barking up the wrong tree (there again, so could I >:). Whats the address that getting the CNAME lookup failure. I've tried several addresses, both local to my root domain and external. Example domains are dimon.is and abacus.com. All fail with the CNAME error. >What does qmail-qstat give? > qmail-qstat gives the following: messages in queue: 2 messages in queue but not yet preprocessed: 0 Jens Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: Still getting CNAME_lookup_failed_temporarily errors
Jens Hafsteinsson wrote: > >In the right directory? I'm grabing at straws, here, but ... > > Yes, it is in the right directory. You all may be barking up the wrong tree (there again, so could I :). Whats the address that getting the CNAME lookup failure. What does qmail-qstat give? I'm intrested to whats cuasing the CNAME errors. Regards, D.
Re: Still getting CNAME_lookup_failed_temporarily errors
>From: "asantos" <[EMAIL PROTECTED]>
> >named does recursive queries by default according to the docs.
>
>Well.. is your installation the default one? ;)
Yes, I would think so.
> >Everything in named.conf seems fine. The zone "." looks like this:
> >
> >zone "." in
> >{
> > type hint;
> > file "db.cache";
> >};
> >
> >and the db.cache file contains the root servers.
>
>In the right directory? I'm grabing at straws, here, but ...
Yes, it is in the right directory.
>
> >Well, if the problem lies with my resolver, are there any tools that I
>can
> >use to simulate what qmail is trying to do? ping and nslookup seem t be
> >working fine.
> >Maybe some simple source code that I can fiddle with to figure this out?
>
>
>The main difference between qmail and other software re DNS is that qmail
>doesn't give a hoot about the /etc/hosts file. Everything is done through
>DNS. As things stand now, I'd dump bind and try djbdns... unless you can
>get
>someone to debug bind for you.
>
>The tests I've done with triton.axon.is using nslookup did ok. It's even
>recursive. dnsq concurs, everything seems ok. If this was djbdns, with its
>clearer binding to interfaces, I'd say that your DNS server is ok for
>outside queries, but not correctly configured for local queries, and point
>the proverbial finger at the culprit.
>
>Next thing I'd suspect would be libc upgrade problems... what OS are you
>running? I couldn't identify it remotely. It looks like Linux 2.2.14,
>but...
>try to reinstall your libc's.
This thought has bee creeping up on me since yesterday. I'm a bit keen on
sticking with bind, so I will check on my libs first. I'm running Linux
2.2.16 (RH6.1 at heart).
>
>Did you install qmail from source or using a binary package?
>
>From source, but compiled on a different machine (the user and group match).
Thanks,
Jens
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: Still getting CNAME_lookup_failed_temporarily errors
From: Erwin Hoffmann <[EMAIL PROTECTED]> >Can't get your MX-Record ... I can get it. dnsmx axon.is retrieves triton.axon.is. dnsq mx axon.is triton.axon.is also works. As does dnsq mx axon.is sprettur.isnet.is. Even dig @triton.axon.is axos.is mx does. However, all of this only tells us that the server answers ok to queries regarding itself... but the CNAME diagnostic relates to a problem with the recipients domain, not the senders. Armando
Re: Still getting CNAME_lookup_failed_temporarily errors
From: Jens Hafsteinsson <[EMAIL PROTECTED]>
>named does recursive queries by default according to the docs.
Well.. is your installation the default one? ;)
>Sorry, no luck with that one. This strongly suggest some local
configuration
>problem, but I just can't put my finger on it.
Sure, it is a local DNS config problem. See below.
>Oops. Just a typo. It says nameserver in the file.
Damn. Typos are good, you can correct typos :)
>Everything in named.conf seems fine. The zone "." looks like this:
>
>zone "." in
>{
> type hint;
> file "db.cache";
>};
>
>and the db.cache file contains the root servers.
In the right directory? I'm grabing at straws, here, but ...
>Well, if the problem lies with my resolver, are there any tools that I can
>use to simulate what qmail is trying to do? ping and nslookup seem t be
>working fine.
>Maybe some simple source code that I can fiddle with to figure this out?
The main difference between qmail and other software re DNS is that qmail
doesn't give a hoot about the /etc/hosts file. Everything is done through
DNS. As things stand now, I'd dump bind and try djbdns... unless you can get
someone to debug bind for you.
The tests I've done with triton.axon.is using nslookup did ok. It's even
recursive. dnsq concurs, everything seems ok. If this was djbdns, with its
clearer binding to interfaces, I'd say that your DNS server is ok for
outside queries, but not correctly configured for local queries, and point
the proverbial finger at the culprit.
Next thing I'd suspect would be libc upgrade problems... what OS are you
running? I couldn't identify it remotely. It looks like Linux 2.2.14, but...
try to reinstall your libc's.
Did you install qmail from source or using a binary package?
Armando
Re: Still getting CNAME_lookup_failed_temporarily errors
>From: Erwin Hoffmann <[EMAIL PROTECTED]> snip > >Can't get your MX-Record ... > That's strange. Running dnsmxip axon.is. gives me 194.144.127.194 10 wich corresponds to my MX record. snip > >> > >>As a quick fix, try the following on your /etc/resolv.conf (saving the > >>previous contents elsewhere): > >> > >>search axon.is > >>nameserver 193.4.58.19 > >Try to avoid nameserver statement in resolv.conf > >#nameserver 193.4.58.19 >search axon.is > Hmm. How do you resolve names then? Jens Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: Still getting CNAME_lookup_failed_temporarily errors
At 13:50 30.7.2000 GMT, Jens Hafsteinsson wrote: > >> >What I would like to know is what exactly qmail is trying to do. Why is >>it >> >doing a CNAME lookup in the first place? Why doesn't it just use the >> >designated server in the MX records and be done with it? How does a DNS >> >setup look like that works (the relevant parts)? >> >> >>Your MX *is* a CNAME, mail.axon.is. > Can't get your MX-Record ... >It did point directly to my mail servers A record, triton.axon.is, but I >changed it to a CNAME just to see if that would change anything (which it >apparently didn't). > >> >>On the other hand, it seems that your problem is not with your domain. >>AFAIK, no CNAME lookup of the local domain is needed to send mail. You >>should start by checking your /etc/resolv.conf, it seems that qmail can't >>get any DNS answers. Do you have a local DNS cache? Perhaps you should >>switch to djbdns. > >I'm using named 8.2.2 as my primary DNS running on the same machine as the >mail server. > >> >>As a quick fix, try the following on your /etc/resolv.conf (saving the >>previous contents elsewhere): >> >>search axon.is >>nameserver 193.4.58.19 Try to avoid nameserver statement in resolv.conf #nameserver 193.4.58.19 search axon.is cheers. eh. >> >>and restart qmail. If you can then send mail, then you don't have a correct >>local DNS setup. >> > >No, this didn't solve it. Someone said that by putting nameserver 127.0.0.1 >in resolv.conf fixed his CNAME problem but that didn't help either. > >Surely someone must be using named successfully with qmail? >Or is the resolver misconfigured? >My usual resolv.conf file is like this > >search axon.is >namserver 194.144.127.194 > >Thanks, >Jens >___ _ >Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com > > +---+ | fffhh http://www.fehcom.deDr. Erwin Hoffmann | | ff hh| | ffeee ccc ooomm mm mm Wiener Weg 8 | | fff ee ee hh hh cc oo oo mmm mm mm 50858 Koeln| | ff ee eee hh hh cc oo oo mm mm mm| | ff eee hh hh cc oo oo mm mm mm Tel 0221 484 4923 | | ff hh hhccc ooomm mm mm Fax 0221 484 4924 | +---+
Re: Still getting CNAME_lookup_failed_temporarily errors
>From: "asantos" <[EMAIL PROTECTED]>
snip
> >I'm using named 8.2.2 as my primary DNS running on the same machine as
>the mail server.
>
>I don't have the bind documents handy now, but in essence you
>must tell named that it should answer to recursive queries.
>
named does recursive queries by default according to the docs.
> >>As a quick fix, try the following on your /etc/resolv.conf (saving the
> >>previous contents elsewhere):
> >>
> >>search axon.is
> >>nameserver 193.4.58.19
> >>
> >>and restart qmail. If you can then send mail, then you don't have a
>correct
> >>local DNS setup.
> >>
> >
> >No, this didn't solve it. Someone said that by putting nameserver
>127.0.0.1
> >in resolv.conf fixed his CNAME problem but that didn't help either.
>
>
>What you need is a full resolver, and your named is not setup for that. My
>suggestion re 193.4.58.19 was assuming that they were your ISP and that
>they
>provided recursive DNS service... apparentely they don't.
>
>Ok, just for testing, you can replace the address by 194.65.3.20. This is
>an
>ISPs DNS server here in Portugal, and they do accept recursive queries.
Sorry, no luck with that one. This strongly suggest some local configuration
problem, but I just can't put my finger on it.
>
> >Surely someone must be using named successfully with qmail?
> >Or is the resolver misconfigured?
> >My usual resolv.conf file is like this
> >
> >search axon.is
> >namserver 194.144.127.194
>
>
>Sorry, "namserver" or "nameserver" ? That could be it. If not, your
>resolv.conf seems ok.
Oops. Just a typo. It says nameserver in the file.
>
>Also, check that your hint file is ok. Locate the zone entry for type hint
>on /etc/named.conf, check the directory option on the options entry, and
>check that a file named.root (or the name appearing on the zone "."
>section)
>exists and is not empty.
>
Everything in named.conf seems fine. The zone "." looks like this:
zone "." in
{
type hint;
file "db.cache";
};
and the db.cache file contains the root servers.
>I have a couple of qmail's working allright with bind, so that is not the
>problem.
>
Well, if the problem lies with my resolver, are there any tools that I can
use to simulate what qmail is trying to do? ping and nslookup seem t be
working fine.
Maybe some simple source code that I can fiddle with to figure this out?
Jens
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: Still getting CNAME_lookup_failed_temporarily errors
> >What I would like to know is what exactly qmail is trying to do. Why is >it > >doing a CNAME lookup in the first place? Why doesn't it just use the > >designated server in the MX records and be done with it? How does a DNS > >setup look like that works (the relevant parts)? > > >Your MX *is* a CNAME, mail.axon.is. It did point directly to my mail servers A record, triton.axon.is, but I changed it to a CNAME just to see if that would change anything (which it apparently didn't). > >On the other hand, it seems that your problem is not with your domain. >AFAIK, no CNAME lookup of the local domain is needed to send mail. You >should start by checking your /etc/resolv.conf, it seems that qmail can't >get any DNS answers. Do you have a local DNS cache? Perhaps you should >switch to djbdns. I'm using named 8.2.2 as my primary DNS running on the same machine as the mail server. > >As a quick fix, try the following on your /etc/resolv.conf (saving the >previous contents elsewhere): > >search axon.is >nameserver 193.4.58.19 > >and restart qmail. If you can then send mail, then you don't have a correct >local DNS setup. > No, this didn't solve it. Someone said that by putting nameserver 127.0.0.1 in resolv.conf fixed his CNAME problem but that didn't help either. Surely someone must be using named successfully with qmail? Or is the resolver misconfigured? My usual resolv.conf file is like this search axon.is namserver 194.144.127.194 Thanks, Jens Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: Still getting CNAME_lookup_failed_temporarily errors
From: Jens Hafsteinsson <[EMAIL PROTECTED]> >What I would like to know is what exactly qmail is trying to do. Why is it >doing a CNAME lookup in the first place? Why doesn't it just use the >designated server in the MX records and be done with it? How does a DNS >setup look like that works (the relevant parts)? Your MX *is* a CNAME, mail.axon.is. On the other hand, it seems that your problem is not with your domain. AFAIK, no CNAME lookup of the local domain is needed to send mail. You should start by checking your /etc/resolv.conf, it seems that qmail can't get any DNS answers. Do you have a local DNS cache? Perhaps you should switch to djbdns. As a quick fix, try the following on your /etc/resolv.conf (saving the previous contents elsewhere): search axon.is nameserver 193.4.58.19 and restart qmail. If you can then send mail, then you don't have a correct local DNS setup. Good luck Armando
