Re: CNAME_lookup_failed_temporarily._(#4.4.3)
On Wed, 12 Jul 2000, you wrote: At 03:19 PM 7/12/00 -0700, you wrote: Can you give me a good place to start looking in DNS for a solution. The box running qmail is also the DNS box. I am in charge of both of them, although rather green in both too. Anyway I am looking for a good place to start. I am on the bind list and have mailed out my named.conf / 127.0.0 files and everyone says it's good to go. I have applied the patch, re-did the make setup check, and config-fast. I still have CNAME failures happening. I really want to get this resolved, but I am quickly becoming stumped. Please help. Thanks Could it be the fact that my ip 216.160.204.35 resolves to jdsl35.phnx.uswest.net and when I did the config-fast andigilog.com it is confused. But I want to receive mail for andigilog.com. What am I doing wrong? I haven't yet, but I will have the DNS server for andigilog.com (presently earthlink) change the MX to point to jdsl35.phnx.uswest.net. Where and how can I resolve this? Thanks Steven M. Klass Systems Administrator Andigilog Inc. 7404 W. Detroit Street, Suite 100 Chandler, AZ 85226 Ph: 602-940-6200 ext. 18 Fax: 602-940-4255 [EMAIL PROTECTED] http://www.andigilog.com/ Greetings, DNS seems to stump more people than anything else, yet it's quite simple First, forget cnames. They'll just get you in trouble. Think in terms of machine name and mail exchanger (MX) records. What's the name of the machine your mta is on. No matter what the original name of that machine, you can declare it as mail.domain and assign it any address you want (assuming the address belongs to you). If you are the authoritative DNS host for andigilog.com, you can put records for andigilog.com in the zone file and they'll be valid. (If you don't like mail, use any name you like) Along with declaring the address record for mail, you can use the MX record to point to the location of the mta. Of course, the MX record pointing to a specific domain can be used in any DNS zone file, not so for the A record. IF you try to claim authority for a DNS zone and someone else really is, you have created a "lame delegation" If you are trying to receive mail for andigilog.com and there is no MX record in the AUTHORATATIVE DNS zone file pointing to you, forget it. You will have trouble receiving any mail for andigilog.com, if at all. Sorry if it seems like I'm ranting I do a lot of DNS and I see so much wrong information and nonunderstaning that it drives me up a tree. If you have a DNS question, direct it to me personally. I'll give you the best answer I'm capable of. Regards, Eric -- Eric Fletcher - Data Center Support Dialtone Internet - Extremely Fast Web Systems (954) 581-0097 - Voice (954) 581-7629 - Fax [EMAIL PROTECTED] - Email http://www.dialtoneinternet.net
RE: CNAME_lookup_failed_temporarily._(#4.4.3)
is anydomain.com a single domain or absolutely anydomain? try nslookup anydomain.com 198.6.1.1 (thats using uunet dnsserver) and see if you get the same response. you most likely are getting dns problems. -Original Message- From: Steven M. Klass [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 12, 2000 8:10 PM To: Tim Hunter; Steven M. Klass; [EMAIL PROTECTED]; dave Sill Subject: RE: CNAME_lookup_failed_temporarily._(#4.4.3) OH HOW I BOW DOWN TO THEE!!! After scouring the qmail posts YOURS comes shining through. Now I have a weird problem. Why can I do an nslookup of anydomain.com and get the ip, but when I ping anydomain.com i get zilch. Now if I ping the IP of anydomain.com, I get something. What's goin on around here? Any Ideas? Again, thanks a million Steven At 07:32 PM 7/12/00 -0400, Tim Hunter wrote: the error CNAME_lookup_failed_temporarily._(#4.4.3) means that your machine cannot lookup the remote host. This does not mean that your qmail is misconfigured it does mean that your dns or the remote dns is misconfigured. I would doubt you are able to ping the MX for that host you are having problems with. -Original Message- From: Steven M. Klass [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 12, 2000 7:32 PM To: Steven M. Klass; [EMAIL PROTECTED]; dave Sill Subject: Re: CNAME_lookup_failed_temporarily._(#4.4.3) At 03:19 PM 7/12/00 -0700, you wrote: Can you give me a good place to start looking in DNS for a solution. The box running qmail is also the DNS box. I am in charge of both of them, although rather green in both too. Anyway I am looking for a good place to start. I am on the bind list and have mailed out my named.conf / 127.0.0 files and everyone says it's good to go. I have applied the patch, re-did the make setup check, and config-fast. I still have CNAME failures happening. I really want to get this resolved, but I am quickly becoming stumped. Please help. Thanks Could it be the fact that my ip 216.160.204.35 resolves to jdsl35.phnx.uswest.net and when I did the config-fast andigilog.com it is confused. But I want to receive mail for andigilog.com. What am I doing wrong? I haven't yet, but I will have the DNS server for andigilog.com (presently earthlink) change the MX to point to jdsl35.phnx.uswest.net. Where and how can I resolve this? Thanks Steven M. Klass Systems Administrator Andigilog Inc. 7404 W. Detroit Street, Suite 100 Chandler, AZ 85226 Ph: 602-940-6200 ext. 18 Fax: 602-940-4255 [EMAIL PROTECTED] http://www.andigilog.com/ Steven M. Klass Physical Design Engineering Manager Andigilog Inc. 7404 W. Detroit Street, Suite 100 Chandler, AZ 85226 Ph: 602-940-6200 ext. 18 Fax: 602-940-4255 [EMAIL PROTECTED] http://www.andigilog.com/
RE: CNAME_lookup_failed_temporarily._(#4.4.3)
I finally figured it out. Let this stand as a record for deja / qmail surfers everywhere!! 1. Can your computer do a nslookup of a FQDN and not yours? That needs to be working. 2. Can you ping a FQDN and an IP Thats where I screwed up! I could easily nslookup anyone but my machine had an incorrect entry in /etc/resolve.conf It need to say somewhere in there nameserver 127.0.0.1 That's what the problem was for me!! Thanks to everyone! Steven At 09:16 AM 7/13/00 -0400, Tim Hunter wrote: is anydomain.com a single domain or absolutely anydomain? try nslookup anydomain.com 198.6.1.1 (thats using uunet dnsserver) and see if you get the same response. you most likely are getting dns problems. -Original Message- From: Steven M. Klass [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 12, 2000 8:10 PM To: Tim Hunter; Steven M. Klass; [EMAIL PROTECTED]; dave Sill Subject: RE: CNAME_lookup_failed_temporarily._(#4.4.3) OH HOW I BOW DOWN TO THEE!!! After scouring the qmail posts YOURS comes shining through. Now I have a weird problem. Why can I do an nslookup of anydomain.com and get the ip, but when I ping anydomain.com i get zilch. Now if I ping the IP of anydomain.com, I get something. What's goin on around here? Any Ideas? Again, thanks a million Steven At 07:32 PM 7/12/00 -0400, Tim Hunter wrote: the error CNAME_lookup_failed_temporarily._(#4.4.3) means that your machine cannot lookup the remote host. This does not mean that your qmail is misconfigured it does mean that your dns or the remote dns is misconfigured. I would doubt you are able to ping the MX for that host you are having problems with. -Original Message- From: Steven M. Klass [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 12, 2000 7:32 PM To: Steven M. Klass; [EMAIL PROTECTED]; dave Sill Subject: Re: CNAME_lookup_failed_temporarily._(#4.4.3) At 03:19 PM 7/12/00 -0700, you wrote: Can you give me a good place to start looking in DNS for a solution. The box running qmail is also the DNS box. I am in charge of both of them, although rather green in both too. Anyway I am looking for a good place to start. I am on the bind list and have mailed out my named.conf / 127.0.0 files and everyone says it's good to go. I have applied the patch, re-did the make setup check, and config-fast. I still have CNAME failures happening. I really want to get this resolved, but I am quickly becoming stumped. Please help. Thanks Could it be the fact that my ip 216.160.204.35 resolves to jdsl35.phnx.uswest.net and when I did the config-fast andigilog.com it is confused. But I want to receive mail for andigilog.com. What am I doing wrong? I haven't yet, but I will have the DNS server for andigilog.com (presently earthlink) change the MX to point to jdsl35.phnx.uswest.net. Where and how can I resolve this? Thanks Steven M. Klass Systems Administrator Andigilog Inc. 7404 W. Detroit Street, Suite 100 Chandler, AZ 85226 Ph: 602-940-6200 ext. 18 Fax: 602-940-4255 [EMAIL PROTECTED] http://www.andigilog.com/ Steven M. Klass Physical Design Engineering Manager Andigilog Inc. 7404 W. Detroit Street, Suite 100 Chandler, AZ 85226 Ph: 602-940-6200 ext. 18 Fax: 602-940-4255 [EMAIL PROTECTED] http://www.andigilog.com/
Re: CNAME_lookup_failed_temporarily._(#4.4.3)
Can you give me a good place to start looking in DNS for a solution. The box running qmail is also the DNS box. I am in charge of both of them, although rather green in both too. Anyway I am looking for a good place to start. I am on the bind list and have mailed out my named.conf / 127.0.0 files and everyone says it's good to go. I have applied the patch, re-did the make setup check, and config-fast. I still have CNAME failures happening. I really want to get this resolved, but I am quickly becoming stumped. Please help. Thanks At 03:27 PM 7/6/00 -0400, you wrote: Robert Sander [EMAIL PROTECTED] wrote: On Wed, Jul 05, 2000 at 01:12:42PM -0400, Dave Sill wrote: Claudinei Luis Bianchini [EMAIL PROTECTED] wrote: I had applied the patch for this and work very well with BIND. recently, I changed to DNScache and this message came back. where's the problem ?? Exactly. What makes you think this message indicates a problem on your end? That exactly was my question about one week ago. How do I know where the problem is? It's a DNS problem. qmail couldn't resolve a host name, and the resolver said the problem was temporary. Normally, you don't have to do anything except wait for the name server problem to be fixed. If you know for a fact that the name is resolvable, then you might have a problem that demands your attention. But it's not specifically a qmail problem. -Dave Steven M. Klass Physical Design Engineering Manager Andigilog Inc. 7404 W. Detroit Street, Suite 100 Chandler, AZ 85226 Ph: 602-940-6200 ext. 18 Fax: 602-940-4255 [EMAIL PROTECTED] http://www.andigilog.com/
Re: CNAME_lookup_failed_temporarily._(#4.4.3)
At 03:19 PM 7/12/00 -0700, you wrote: Can you give me a good place to start looking in DNS for a solution. The box running qmail is also the DNS box. I am in charge of both of them, although rather green in both too. Anyway I am looking for a good place to start. I am on the bind list and have mailed out my named.conf / 127.0.0 files and everyone says it's good to go. I have applied the patch, re-did the make setup check, and config-fast. I still have CNAME failures happening. I really want to get this resolved, but I am quickly becoming stumped. Please help. Thanks Could it be the fact that my ip 216.160.204.35 resolves to jdsl35.phnx.uswest.net and when I did the config-fast andigilog.com it is confused. But I want to receive mail for andigilog.com. What am I doing wrong? I haven't yet, but I will have the DNS server for andigilog.com (presently earthlink) change the MX to point to jdsl35.phnx.uswest.net. Where and how can I resolve this? Thanks Steven M. Klass Systems Administrator Andigilog Inc. 7404 W. Detroit Street, Suite 100 Chandler, AZ 85226 Ph: 602-940-6200 ext. 18 Fax: 602-940-4255 [EMAIL PROTECTED] http://www.andigilog.com/
RE: CNAME_lookup_failed_temporarily._(#4.4.3)
the error CNAME_lookup_failed_temporarily._(#4.4.3) means that your machine cannot lookup the remote host. This does not mean that your qmail is misconfigured it does mean that your dns or the remote dns is misconfigured. I would doubt you are able to ping the MX for that host you are having problems with. -Original Message- From: Steven M. Klass [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 12, 2000 7:32 PM To: Steven M. Klass; [EMAIL PROTECTED]; dave Sill Subject: Re: CNAME_lookup_failed_temporarily._(#4.4.3) At 03:19 PM 7/12/00 -0700, you wrote: Can you give me a good place to start looking in DNS for a solution. The box running qmail is also the DNS box. I am in charge of both of them, although rather green in both too. Anyway I am looking for a good place to start. I am on the bind list and have mailed out my named.conf / 127.0.0 files and everyone says it's good to go. I have applied the patch, re-did the make setup check, and config-fast. I still have CNAME failures happening. I really want to get this resolved, but I am quickly becoming stumped. Please help. Thanks Could it be the fact that my ip 216.160.204.35 resolves to jdsl35.phnx.uswest.net and when I did the config-fast andigilog.com it is confused. But I want to receive mail for andigilog.com. What am I doing wrong? I haven't yet, but I will have the DNS server for andigilog.com (presently earthlink) change the MX to point to jdsl35.phnx.uswest.net. Where and how can I resolve this? Thanks Steven M. Klass Systems Administrator Andigilog Inc. 7404 W. Detroit Street, Suite 100 Chandler, AZ 85226 Ph: 602-940-6200 ext. 18 Fax: 602-940-4255 [EMAIL PROTECTED] http://www.andigilog.com/
RE: CNAME_lookup_failed_temporarily._(#4.4.3)
OH HOW I BOW DOWN TO THEE!!! After scouring the qmail posts YOURS comes shining through. Now I have a weird problem. Why can I do an nslookup of anydomain.com and get the ip, but when I ping anydomain.com i get zilch. Now if I ping the IP of anydomain.com, I get something. What's goin on around here? Any Ideas? Again, thanks a million Steven At 07:32 PM 7/12/00 -0400, Tim Hunter wrote: the error CNAME_lookup_failed_temporarily._(#4.4.3) means that your machine cannot lookup the remote host. This does not mean that your qmail is misconfigured it does mean that your dns or the remote dns is misconfigured. I would doubt you are able to ping the MX for that host you are having problems with. -Original Message- From: Steven M. Klass [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 12, 2000 7:32 PM To: Steven M. Klass; [EMAIL PROTECTED]; dave Sill Subject: Re: CNAME_lookup_failed_temporarily._(#4.4.3) At 03:19 PM 7/12/00 -0700, you wrote: Can you give me a good place to start looking in DNS for a solution. The box running qmail is also the DNS box. I am in charge of both of them, although rather green in both too. Anyway I am looking for a good place to start. I am on the bind list and have mailed out my named.conf / 127.0.0 files and everyone says it's good to go. I have applied the patch, re-did the make setup check, and config-fast. I still have CNAME failures happening. I really want to get this resolved, but I am quickly becoming stumped. Please help. Thanks Could it be the fact that my ip 216.160.204.35 resolves to jdsl35.phnx.uswest.net and when I did the config-fast andigilog.com it is confused. But I want to receive mail for andigilog.com. What am I doing wrong? I haven't yet, but I will have the DNS server for andigilog.com (presently earthlink) change the MX to point to jdsl35.phnx.uswest.net. Where and how can I resolve this? Thanks Steven M. Klass Systems Administrator Andigilog Inc. 7404 W. Detroit Street, Suite 100 Chandler, AZ 85226 Ph: 602-940-6200 ext. 18 Fax: 602-940-4255 [EMAIL PROTECTED] http://www.andigilog.com/ Steven M. Klass Physical Design Engineering Manager Andigilog Inc. 7404 W. Detroit Street, Suite 100 Chandler, AZ 85226 Ph: 602-940-6200 ext. 18 Fax: 602-940-4255 [EMAIL PROTECTED] http://www.andigilog.com/
Re: CNAME_lookup_failed_temporarily._(#4.4.3)
On Wed, Jul 05, 2000 at 01:12:42PM -0400, Dave Sill wrote: Claudinei Luis Bianchini [EMAIL PROTECTED] wrote: I had applied the patch for this and work very well with BIND. recently, I changed to DNScache and this message came back. where's the problem ?? Exactly. What makes you think this message indicates a problem on your end? That exactly was my question about one week ago. How do I know where the problem is? Greetings -- Robert Sander Epigenomics AG www.epigenomics.de Kastanienallee 24 +493024345330 10435 Berlin
Re: CNAME_lookup_failed_temporarily._(#4.4.3)
Robert Sander [EMAIL PROTECTED] wrote: On Wed, Jul 05, 2000 at 01:12:42PM -0400, Dave Sill wrote: Claudinei Luis Bianchini [EMAIL PROTECTED] wrote: I had applied the patch for this and work very well with BIND. recently, I changed to DNScache and this message came back. where's the problem ?? Exactly. What makes you think this message indicates a problem on your end? That exactly was my question about one week ago. How do I know where the problem is? It's a DNS problem. qmail couldn't resolve a host name, and the resolver said the problem was temporary. Normally, you don't have to do anything except wait for the name server problem to be fixed. If you know for a fact that the name is resolvable, then you might have a problem that demands your attention. But it's not specifically a qmail problem. -Dave
CNAME_lookup_failed_temporarily._(#4.4.3)
Hi, I had applied the patch for this and work very well with BIND. recently, I changed to DNScache and this message came back. where's the problem ?? -- Claudinei Luis Bianchini [EMAIL PROTECTED]
Re: CNAME_lookup_failed_temporarily._(#4.4.3)
Claudinei Luis Bianchini [EMAIL PROTECTED] wrote: I had applied the patch for this and work very well with BIND. recently, I changed to DNScache and this message came back. where's the problem ?? Exactly. What makes you think this message indicates a problem on your end? -Dave
CNAME_lookup_failed_temporarily._(#4.4.3)/
Hey, I'm pretty new to qmail but love it so far. Unfortunately I have 1 minor issue with it. Everytime a user sends a message to aol.com, I get May 19 13:27:07 mail qmail: 927134827.225231 starting delivery 2: msg 69468 to remote [EMAIL PROTECTED] May 19 13:27:07 mail qmail: 927134827.225670 status: local 0/10 remote 1/20 May 19 13:27:13 mail qmail: 927134833.032636 delivery 2: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/ Is there an easy way to get around this? I have just noticed this, but it has been going on since I setup the mail server. One of my users just got a bounce from a message that was sent over a MONTH ago!
Re: CNAME_lookup_failed_temporarily._(#4.4.3)/
Greg Owen [EMAIL PROTECTED] writes: Everytime a user sends a message to aol.com, I get [...] deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/ Is there an easy way to get around this? Yup, search the archives for "oversized DNS" and check out the patch on www.qmail.org described as: "Chuck Foster has a patch which works on both qmail's dns.c and tcpserver's dns.c which make them work with oversize DNS packets." There's another patch which does something similar, but I believe it's mentioned in the archives and not on the qmail page. There are, AFAIK, three patches that fix this bug. 1. Just bump the packet buffer size up to 65536. Works with recent BIND resolver libraries, which will automatically do a TCP query within the library code if the reply comes back with the truncation bit set. This is the simplest fix, though it's also the most wasteful of memory (and/or swap space allocation, depending on how your system does copy-on-write and its page size and so on). 2. Chuck Foster's patch URL:http://www.qmail.org/big-dns-patch. This patch dynamically reallocates the buffer based on the size returned by the resolver library (repeating as necessary to make it big enough). This also requires resolver libraries that do the TCP retry, and might have problems if the resolver code returns the number of bytes placed in the buffer instead of the number of bytes in the full response (though I've never seen this behavior, I vaguely recall someone saying they'd seen it). 3. My patch URL:http://www.ckdhr.com/ckd/qmail-103.patch. This is an adaptation of Chuck Foster's patch (see #2) which should work with any resolver library, no matter how old, and uses a guard byte to avoid the "number of bytes placed in the buffer" library bug. It reallocates only once, to 65536, rather than just to the size needed, so it can be less memory-efficient than Chuck's patch (though like his patch it only reallocates if the response is larger than PACKETSZ, which defaults to 512 bytes). After reallocating, it forces a TCP query, rather than requiring the resolver library to do so (avoiding an extra round-trip between qmail and the name server, though if they're on the same machine or local network this is not a big worry). Since last time this question came up (also regarding AOL), there was a question as to why some people didn't have trouble reaching it, I would also like to explain that. Basically, depending on the timing and ordering of queries made to your local nameserver, the size of the response to an ANY query for "aol.com" may be larger than the 512 byte limit of a UDP packet, or it may not. "May not" is likely to happen if the A and MX records time out but the NS records don't; since the .COM servers set a 2 day TTL on those but AOL sets a 1 hour TTL on their records, this will often happen on lower traffic nameservers. Higher traffic nameservers are more likely to have those records in cache at any given time, frustrating an unpatched qmail's attempts to check for CNAMEs. A better test is to send mail to [EMAIL PROTECTED]; if it clears your queue and winds up bouncing from here, your MTA can send mail to hosts with MX lists that exceed 512 bytes. (By using a single RRset with a single TTL that exceeds 512 bytes, the problem can be seen without depending on the timing and ordering of other queries.) -- Christopher Davis * [EMAIL PROTECTED] * URL:http://www.ckdhr.com/ckd/ Put location information in your DNS! URL:http://www.ckdhr.com/dns-loc/
Re: CNAME_lookup_failed_temporarily._(#4.4.3)/
"Tim Hunter" [EMAIL PROTECTED] writes:
| Everytime a user sends a message to aol.com, I get ...
| CNAME_lookup_failed_temporarily._(#4.4.3)/
|
| Is there an easy way to get around this? I have just noticed this, but it
| has been going on since I setup the mail server. One of my users just got a
| bounce from a message that was sent over a MONTH ago!
Yes, there's a simple fix. Change line 24 of dns.c from
static union { HEADER hdr; unsigned char buf[PACKETSZ]; } response;
to
static union { HEADER hdr; unsigned char buf[115]; } response;
Notice that this doesn't increase the working set of any part of qmail
by more than one page, since unneeded pages are never touched. More
complex solutions have been proposed which involve dynamic memory
allocation and more queries of DNS, all of which cost something too.
Re: CNAME_lookup_failed_temporarily._(#4.4.3)/
Christopher K Davis [EMAIL PROTECTED] writes: |... This is the simplest fix, though it's also |the most wasteful of memory (and/or swap space allocation, depending |on how your system does copy-on-write and its page size and so on). I don't think copy-on-write is a factor. Demand paging, like every Unix has had for years and years and years should take care of the whole issue. If you don't touch a page, it doesn't consume RAM, just backing store, which is not in short supply.
