December 19th, 2003, 10:24 AM
sendmail dns issues.
I run my own dns in which I have made an entry for a friends pc (multisal.nl) which is connected via adsl to the internet.
On the multisal machine, I'm using the preconfigured sendmail 8.12.8 which came with Red Hat 9.
multisal.nl. IN SOA ns1.nednieuws.com. joe.nednieuws.com. (
multisal.nl. 14400 IN NS ns1.nednieuws.com.
multisal.nl. 14400 IN A 220.127.116.11
localhost.multisal.nl. 14400 IN A 127.0.0.1
mail.multisal.nl. 14400 IN A 18.104.22.168
multisal.nl. 14400 IN NS ns2.nednieuws.com.
www.multisal.nl. 14400 IN CNAME multisal.nl.
multisal.nl. 14400 IN MX 5 mail
On my machine (at a hosting provider) I have everything working exactly as I want it. On the multisal machine, I keep getting these messages:
Inbound mail (/var/log/maillog):
Dec 19 12:42:47 web sendmail: NOQUEUE: connect from iits01113.inlink.com [22.214.171.124]
Dec 19 12:42:47 web sendmail: AUTH: available mech=PLAIN LOGIN ANONYMOUS, allowed mech=EXTERNAL GSSAPI KERBEROS_V4 DIGEST-MD5 CRAM-MD5
Dec 19 12:42:47 web sendmail: hBJBglDQ005096: Milter: no active filter
Dec 19 12:42:51 web sendmail: hBJBglDQ005096: iits01113.inlink.com [126.96.36.199] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA
Dec 19 12:53:59 web sendmail: NOQUEUE: connect from iits01113.inlink.com [188.8.131.52]
Dec 19 12:53:59 web sendmail: AUTH: available mech=PLAIN LOGIN ANONYMOUS, allowed mech=EXTERNAL GSSAPI KERBEROS_V4 DIGEST-MD5 CRAM-MD5
Dec 19 12:53:59 web sendmail: hBJBrxDQ005225: Milter: no active filter
Dec 19 12:53:59 web sendmail: hBJBrxDQ005225: from=<email@example.com>, size=1525, class=0, nrcpts=1, msgid=<001301c3c626$c0f849a0$9a00000a@ash>, proto=ESMTP, daemon=MTA, relay=iits01113.inlink.com [184.108.40.206]
Dec 19 12:53:59 web sendmail: hBJBrxDQ005225: to=<firstname.lastname@example.org>, delay=00:00:00, mailer=local, pri=30816, dsn=4.4.3, stat=queued
Upon flushing the queue using webmin, I get:
Forcing the attempted delivery of mail with the command /usr/lib/sendmail -v -q -C/etc/mail/sendmail.cf ..
Running /var/spool/mqueue/hBJBrxDQ005225 (sequence 1 of 1)
nednieuws.com: Name server timeout
<email@example.com>... Transient parse error -- message queued for future delivery
nednieuws.com: Name server timeout
multisal.nl: Name server timeout
<firstname.lastname@example.org>... Transient parse error -- message queued for future delivery
Figuring out what's going on on sendmail.org, I think it is because there is no dns on the multisal machine (do they mean that named should be running?). What are my options to solve this without resorting to 'accept unresolvable domains' trickery.
Last edited by nednieuws; December 19th, 2003 at 10:26 AM.
December 19th, 2003, 11:41 AM
CNAME is for DNS illiterate people to use. You know how to use A record on mail so why didn't you use
www.multisal.nl. 14400 IN A 220.127.116.11
No, that's what external DNS is for, and that machine just needs to have sendmail up and running and port 25 can't be filtered. As far as the DNS config on your side they look fine except the CNAME.
December 19th, 2003, 12:33 PM
I didn't see why that would change anything and it didn't. The thing is, it will only send/accept mail (eg. not queue it) when the domain is web.lan (the host=web, domain=lan as defined in the router). I'm really stuck with this one...
dig shows me nothing's wrong:
[foo@web mail]# dig mx multisal.nl
; <<>> DiG 9.2.1 <<>> mx multisal.nl
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOTIMP, id: 24160
;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;multisal.nl. IN MX
;; Query time: 1 msec
;; SERVER: 10.0.0.138#53(10.0.0.138)
;; WHEN: Fri Dec 19 18:31:09 2003
;; MSG SIZE rcvd: 29
Wait, I'm not much of a network guy, but what about the router? The domain is set to 'lan'. Should that be changed to 'multisal.nl' also?
December 19th, 2003, 12:48 PM
Sorry, I don't use insecure software -> sendmail, so I can't help you on that. The CNAME should be dropped for any situation, although it's unrelated to your existing problem. Just so you know, many DNS problems are caused by CNAME. There's no reason to use it when it's simply a matter of changing a single line in your zone file.
As far as web.lan being used a the domain, it has nothing to do with the router. The duty of your router is to NAT/forward/filter requests, no more, no less.
December 19th, 2003, 12:54 PM
Oh, man. Let's see if someone else can help with this one...
I'm looking into switching to qmail on my production box which is running RH 7.3. It seems like such a big operation and switching mta moves me straight out of my (sendmail) comfort zone for such an important thing as e-mail.
Thanks anyway. I've been reading your posts in the Apache forum and I value your input (and, erm, 'stubbornness' with software you like -- excuse my english, probably need another word :-)