Mailing List Archive: Qmail: users

CNAME_lookup_failed_temporarily._(#4.4.3)

Index | Next | Previous | View Threaded

suporte at netcon

Jul 5, 2000, 10:54 AM

Post #1 of 19 (3789 views)
Permalink

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
bianchini [at] netcon

de5 at sws5

Jul 5, 2000, 10:12 AM

Post #2 of 19 (3759 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

Claudinei Luis Bianchini <suporte [at] netcon> 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

gurubert at epigenomics

Jul 5, 2000, 11:55 PM

Post #3 of 19 (3756 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

On Wed, Jul 05, 2000 at 01:12:42PM -0400, Dave Sill wrote:
> Claudinei Luis Bianchini <suporte [at] netcon> 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

de5 at sws5

Jul 6, 2000, 12:27 PM

Post #4 of 19 (3756 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

Robert Sander <gurubert [at] epigenomics> wrote:

>On Wed, Jul 05, 2000 at 01:12:42PM -0400, Dave Sill wrote:
>> Claudinei Luis Bianchini <suporte [at] netcon> 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

sklass at andigilog

Jul 12, 2000, 3:19 PM

Post #5 of 19 (3761 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

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 <gurubert [at] epigenomics> wrote:
>
> >On Wed, Jul 05, 2000 at 01:12:42PM -0400, Dave Sill wrote:
> >> Claudinei Luis Bianchini <suporte [at] netcon> 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

sklass [at] andigilog
http://www.andigilog.com/

sklass at andigilog

Jul 12, 2000, 4:31 PM

Post #6 of 19 (3758 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

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

sklass [at] andigilog
http://www.andigilog.com/

tim.hunter at cimx

Jul 12, 2000, 4:32 PM

Post #7 of 19 (3755 views)
Permalink

RE: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

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:sklass [at] andigilog]
Sent: Wednesday, July 12, 2000 7:32 PM
To: Steven M. Klass; qmail [at] list; 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

sklass [at] andigilog
http://www.andigilog.com/

sklass at andigilog

Jul 12, 2000, 5:10 PM

Post #8 of 19 (3748 views)
Permalink

RE: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

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:sklass [at] andigilog]
>Sent: Wednesday, July 12, 2000 7:32 PM
>To: Steven M. Klass; qmail [at] list; 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
>
>sklass [at] andigilog
>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

sklass [at] andigilog
http://www.andigilog.com/

ericfl at dialtoneinternet

Jul 13, 2000, 5:58 AM

Post #9 of 19 (3755 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

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
>
> sklass [at] andigilog
> 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
ericfl [at] dialtoneinternet - Email
http://www.dialtoneinternet.net

tim.hunter at cimx

Jul 13, 2000, 6:16 AM

Post #10 of 19 (3764 views)
Permalink

RE: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

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:sklass [at] andigilog]
Sent: Wednesday, July 12, 2000 8:10 PM
To: Tim Hunter; Steven M. Klass; qmail [at] list; 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:sklass [at] andigilog]
>Sent: Wednesday, July 12, 2000 7:32 PM
>To: Steven M. Klass; qmail [at] list; 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
>
>sklass [at] andigilog
>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

sklass [at] andigilog
http://www.andigilog.com/

sklass at andigilog

Jul 13, 2000, 8:31 AM

Post #11 of 19 (3756 views)
Permalink

RE: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

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:sklass [at] andigilog]
>Sent: Wednesday, July 12, 2000 8:10 PM
>To: Tim Hunter; Steven M. Klass; qmail [at] list; 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:sklass [at] andigilog]
> >Sent: Wednesday, July 12, 2000 7:32 PM
> >To: Steven M. Klass; qmail [at] list; 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
> >
> >sklass [at] andigilog
> >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
>
>sklass [at] andigilog
>http://www.andigilog.com/

sgifford at suspectclass

May 26, 2003, 2:34 AM

Post #12 of 19 (3751 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

Michael Green <michael.green [at] gbst> writes:

> I have two external qmail servers which I want to use to relay mail
> to/from my internal mail server. Both of these servers
> (mail-1.gbst.net & mail-2.gbst.net) are configured the same way and
> they both accept mail from the Internet and pass it on to our
> internal mail server. However mail-1 will not send outgoing mail and
> mail-2 will. Mail-1 accepts the mail from the internal machine but
> does not attempt delivery.
>
> Both servers use dnscache.
>
> An example of the error in mail-1's log is:
> @400000003ed1390332d5adf4 starting delivery 216: msg 1684269 to remote
> michael.green [at] uqconnect
> @400000003ed1390332d5c564 status: local 0/10 remote 1/20
> @400000003ed1390332ed6ffc delivery 216: deferral:
> CNAME_lookup_failed_temporarily._(#4.4.3)/
> @400000003ed1390332ed8384 status: local 0/10 remote 0/20

What's in /etc/resolv.conf on the two servers?

What do:

dnsqr any uqconnect.net

and

dnsqr cname uqconnect.net

say on each of the two servers?

> As I understand it (please correct me if I'm wrong) mail-1 is attempting to
> do a reverse lookup on the address of the internal mail server before it
> will attempt to deliver it's mail to the final destination.

No. It's trying to do a normal DNS lookup on the recipient domain,
which appears to be "uqconnect.net" in this case.

-----ScottG.

michael.green at gbst

May 26, 2003, 8:45 PM

Post #13 of 19 (3757 views)
Permalink

RE: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

Scott

Both servers also run dnscache and use each other to resolve.
mail-1 internal address is 172.17.5.59
mail-2 internal address is 172.17.5.60

ie /etc/resolv.conf on mail-1 is:
search gbst.com star.com.au
nameserver 172.17.5.60
nameserver 172.17.5.59

and /etc/resolv.conf on mail-2 is the opposite:
search gbst.com star.com.au
nameserver 172.17.5.59
nameserver 172.17.5.60

[root [at] mail- root]# dnsqr any uqconnect.net
255 uqconnect.net:
94 bytes, 1+3+0+0 records, response, noerror
query: 255 uqconnect.net
answer: uqconnect.net 83304 NS ns3.uq.edu.au
answer: uqconnect.net 83304 NS ns1.uq.edu.au
answer: uqconnect.net 83304 NS ns2.uq.edu.au

[root [at] mail- root]# dnsqr cname uqconnect.net
5 uqconnect.net:
31 bytes, 1+0+0+0 records, response, noerror
query: 5 uqconnect.net

[root [at] mail- root]# dnsqr any uqconnect.net
255 uqconnect.net:
94 bytes, 1+3+0+0 records, response, noerror
query: 255 uqconnect.net
answer: uqconnect.net 83283 NS ns2.uq.edu.au
answer: uqconnect.net 83283 NS ns3.uq.edu.au
answer: uqconnect.net 83283 NS ns1.uq.edu.au

[root [at] mail- root]# dnsqr cname uqconnect.net
5 uqconnect.net:
31 bytes, 1+0+0+0 records, response, noerror
query: 5 uqconnect.net

The thing is I can telnet to port 25 on any external mailserver and deliver
mail from BOTH mail-1 and mail-2. But if I Send from my internal mail server
using mail-2 as the relay, mail-2 accepts the message and then makes the
connection to the remote server which also accepts the message. If however
the Internal mail server uses mail-1 as it's relay, mail-1 accepts the
message and then and just queues the message with a #4.4.3 error in the
logs.

-----Original Message-----
From: Scott Gifford [mailto:sgifford [at] suspectclass]
Sent: Monday, 26 May 2003 19:35
To: Michael Green
Cc: 'qmail [at] list'
Subject: Re: CNAME_lookup_failed_temporarily._(#4.4.3)

Michael Green <michael.green [at] gbst> writes:

> I have two external qmail servers which I want to use to relay mail
> to/from my internal mail server. Both of these servers
> (mail-1.gbst.net & mail-2.gbst.net) are configured the same way and
> they both accept mail from the Internet and pass it on to our
> internal mail server. However mail-1 will not send outgoing mail and
> mail-2 will. Mail-1 accepts the mail from the internal machine but
> does not attempt delivery.
>
> Both servers use dnscache.
>
> An example of the error in mail-1's log is:
> @400000003ed1390332d5adf4 starting delivery 216: msg 1684269 to remote
> michael.green [at] uqconnect
> @400000003ed1390332d5c564 status: local 0/10 remote 1/20
> @400000003ed1390332ed6ffc delivery 216: deferral:
> CNAME_lookup_failed_temporarily._(#4.4.3)/
> @400000003ed1390332ed8384 status: local 0/10 remote 0/20

What's in /etc/resolv.conf on the two servers?

What do:

dnsqr any uqconnect.net

and

dnsqr cname uqconnect.net

say on each of the two servers?

> As I understand it (please correct me if I'm wrong) mail-1 is attempting
to
> do a reverse lookup on the address of the internal mail server before it
> will attempt to deliver it's mail to the final destination.

No. It's trying to do a normal DNS lookup on the recipient domain,
which appears to be "uqconnect.net" in this case.

-----ScottG.

sgifford at suspectclass

May 26, 2003, 9:33 PM

Post #14 of 19 (3765 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

Michael Green <michael.green [at] gbst> writes:

> Scott
>
> Both servers also run dnscache and use each other to resolve.
> mail-1 internal address is 172.17.5.59
> mail-2 internal address is 172.17.5.60
>
> ie /etc/resolv.conf on mail-1 is:
> search gbst.com star.com.au
> nameserver 172.17.5.60
> nameserver 172.17.5.59
>
> and /etc/resolv.conf on mail-2 is the opposite:
> search gbst.com star.com.au
> nameserver 172.17.5.59
> nameserver 172.17.5.60

That's unusual...So mail-2 uses mail-1 to resolve, and mail-2 uses
mail-1? That should work fine, but what's the goal of that?

> [root [at] mail- root]# dnsqr any uqconnect.net
> 255 uqconnect.net:
> 94 bytes, 1+3+0+0 records, response, noerror
> query: 255 uqconnect.net
> answer: uqconnect.net 83304 NS ns3.uq.edu.au
> answer: uqconnect.net 83304 NS ns1.uq.edu.au
> answer: uqconnect.net 83304 NS ns2.uq.edu.au
>
> [root [at] mail- root]# dnsqr cname uqconnect.net
> 5 uqconnect.net:
> 31 bytes, 1+0+0+0 records, response, noerror
> query: 5 uqconnect.net
>
> [root [at] mail- root]# dnsqr any uqconnect.net
> 255 uqconnect.net:
> 94 bytes, 1+3+0+0 records, response, noerror
> query: 255 uqconnect.net
> answer: uqconnect.net 83283 NS ns2.uq.edu.au
> answer: uqconnect.net 83283 NS ns3.uq.edu.au
> answer: uqconnect.net 83283 NS ns1.uq.edu.au
>
> [root [at] mail- root]# dnsqr cname uqconnect.net
> 5 uqconnect.net:
> 31 bytes, 1+0+0+0 records, response, noerror
> query: 5 uqconnect.net

And that's right around the time when you're seeing this message in
your log file, like within 5 minutes? You can trigger this message at
will by sending a message, right?

What does:

/var/qmail/bin/qmail-remote uqconnect.net michael.green [at] gbst michael.green [at] uqconnect

do, if you run it within a few minutes of seeing the error, then type
an email message, then hit CTRL-D?

-----ScottG.

jparsons-lists at saffron

May 27, 2003, 5:08 PM

Post #15 of 19 (3748 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

On Tuesday, May 27, 2003, at 05:45 PM, Michael Green wrote:

> Just a thought: We had the same problem with a Sun Solaris machine:
> Turned out to be a simple permissions problem: Changing resolve.conf to
> be world readable fixed things. {Well, actually we made it R/W/X, but
> anyways ...

This means that anyone with an account on your machine can change how
you look things up in DNS. This is dangerous and probably not what you
want.

resolv.conf should be group and world *readable*, not writable, and
certainly not executable.

- Jason Parsons

rsh at pobox

Oct 26, 2003, 10:52 AM

Post #16 of 19 (3753 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

> > http://www.ckdhr.com/ckd/qmail-103.patch
> That patch shouldn't be necessary. What DNS resolver/cache are you using?
> BIND or djbdns's dnscache? Does /etc/resolv.conf point to a remote DNS
> resolver/cache, or to one running on localhost?

I have tryed them both,

/etc/resolv.conf contains.
nameserver 127.0.0.1

> I think, perhaps, you're going to need to strace qmail-rspawn (and all
it's
> children) to find out why you're getting this error. If you don't know
how to
> use strace to do this, contact your OS vendor for assistance.

I am not sure that i did this correct but i started qmail-start using
strace, and i got some output, but i dont understand it.
Do you?

I have attatched it to this mail.

Attachments:

strace.log (26.3 KB)

pratte at cybergeneration

Mar 4, 2011, 8:48 AM

Post #17 of 19 (3768 views)
Permalink

RE: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply 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:michael [at] hudsonstreet]
Envoy�: Friday, March 04, 2011 10:42 AM
��: qmail List
Objet�: CNAME_lookup_failed_temporarily._(#4.4.3)

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 <root [at] monitor> qp 14415 uid 509
2011-03-04 10:36:13.064262500 starting delivery 4: msg 1757690 to remote admin [at] hudsonstreet
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)/

dsylvesteriv at gmail

Mar 4, 2011, 9:40 AM

Post #18 of 19 (3790 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply to]

I fixed this issue by installing and running
DNScache<http://cr.yp.to/djbdns/dnscache.html>
.

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� <pratte [at] cybergeneration>

> 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:michael [at] hudsonstreet]
> Envoy� : Friday, March 04, 2011 10:42 AM
> � : qmail List
> Objet : CNAME_lookup_failed_temporarily._(#4.4.3)
>
> 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 <
> root [at] monitor> qp 14415 uid 509
> 2011-03-04 10:36:13.064262500 starting delivery 4: msg 1757690 to remote
> admin [at] hudsonstreet
> 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)/
>
>
>
>
>

amb-sendok-1301888205.ombjmjhiohhimpafaajf at bradfo

Mar 4, 2011, 7:36 PM

Post #19 of 19 (3783 views)
Permalink

Re: CNAME_lookup_failed_temporarily._(#4.4.3) [In reply 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

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads