[courier-users] DNS lookup failure.. on everything!

[Dustin Puryear]

I have a brand new Courier-MTA install. I can deliver mail fine to local 
accounts, but I cannot send any mail outside the mail server. Also, any 
mail sent from another machine to this server waits in the queue. 
Basically, no matter what happens for these two cases I get an error. Here 
is an example. On mail.example.com I send a message:

# mail [EMAIL PROTECTED]
Subject: testing
hi
.
Cc:
Looking at /var/log/maillog I see:

Apr  2 21:51:09 www courierd: 
started,id=001B3272.3E8BAFAD.00002B3F,from=<[EMAIL PROTECTED]>,module=esmtp,host=puryear-it.com,addr=<[EMAIL PROTECTED]>
Apr  2 21:51:09 www courierd: Waiting.  shutdown time=none, wakeup time=Wed 
Apr  2 21:53:13 2003, queuedelivering=399, inprogress=1
Apr  2 21:51:09 www courieresmtp: 
id=001B3272.3E8BAFAD.00002B3F,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>: 
DNS lookup failed.
Apr  2 21:51:09 www courieresmtp: 
id=001B3272.3E8BAFAD.00002B3F,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,status: 
deferred
Apr  2 21:51:09 www courierd: completed,id=001B3272.3E8BAFAD.00002B3F
Apr  2 21:51:09 www courierd: Waiting.  shutdown time=Wed Apr  2 22:43:12 
2003, wakeup time=Wed Apr  2 21:53:13 2003, queuedelivering=399, inprogress=0

example.com is actually another domain, but I am protecting the innocent. 
So now let's jump to nslookup and see what's up:

# nslookup
Note:  nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead.  Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
> set q=mx
> puryear-it.com
Server:         0.0.0.0
Address:        0.0.0.0#53
Non-authoritative answer:
puryear-it.com  mail exchanger = 0 puryear-it.com.
Authoritative answers can be found from:
puryear-it.com  nameserver = ns2.nocdirect.com.
puryear-it.com  nameserver = ns.nocdirect.com.
puryear-it.com  internet address = 66.227.64.228
ns.nocdirect.com        internet address = 66.227.57.1
ns2.nocdirect.com       internet address = 66.227.56.5
Looks fine to me! What is going on here? I also get DNS lookup error if I 
send from my [EMAIL PROTECTED] account to an account on this system. 
There is a serious amount of mail queueing up. I might blame it on DNS 
problems at puryear-it.com, but this same experiment fails for any user of 
any domain I try to send to.

---
Dustin Puryear <[EMAIL PROTECTED]>
Puryear Information Technology
Windows, UNIX, and IT Consulting
http://www.puryear-it.com


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users