I am having a mail server problem where the mail to one domain is being sent to the wrong server. When I use "dig masonc.com mx", I get ;; ANSWER SECTION: masonc.com. 86400 IN MX 5 mail.masonc.com. ;; AUTHORITY SECTION: masonc.com. 86400 IN NS ns1.picadoo.com. masonc.com. 86400 IN NS ns2.picadoo.com. ;; ADDITIONAL SECTION: mail.masonc.com. 86400 IN A 207.44.194.3 However, when I send a mail to anyone at masonc.com, the mail service (postfix) on this server tries to deliver to server7.picadoo.com, another of my servers but not the mail server for the domain. Feb 11 10:50:17 server postfix/smtp[16053]: EB01D6280C6: to=<anyone at masonc.com>, relay=server7.picadoo.com[64.246.62.9], delay=8, status=sent (250 2.0.0 k1BEoDM9015689 Message accepted for delivery) I would like to examine the responses from named in the logs, not just the queries, but I cannot find a way to log them. Any suggestions on a: how to log the answers to queries b: what is wrong here -- Chris Mason NetConcepts (264) 497-5670 Fax: (264) 497-8463 Int: (305) 704-7249 Fax: (815)301-9759 UK 44.207.183.0271 Cell: 264-235-5670 Yahoo IM: netconcepts_anguilla at yahoo.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> I would like to examine the responses from named in the logs, not just > the queries, but I cannot find a way to log them. Any suggestions on > a: how to log the answers to queries > b: what is wrong hereI prefer to use syslog to log things from named. Here's what I use in my named.conf: Note that I don't run at severity debug, but I figure you'll want to. The category query line seems to be what you're after, but the whole thing won't hurt. logging { channel "default_syslog" { syslog local6; severity debug; }; category default { default_syslog; }; category general { default_syslog; }; category config { default_syslog; }; category security { default_syslog; }; category resolver { default_syslog; }; category xfer-in { default_syslog; }; category xfer-out { default_syslog; }; category notify { default_syslog; }; category client { default_syslog; }; category network { default_syslog; }; category update { default_syslog; }; category queries { default_syslog; }; category lame-servers { default_syslog; }; }; Then in /etc/syslog.conf local6.* /var/log/named.log If you want to keep the crap out of /var/log/messages, just append 'local6.none' to the definition for /var/log/messages. If you're going to be running this for any length of time, you may want to consider logrotate. Drop this in /etc/logrotate.d/named /var/log/named.log { missingok create 0644 named named postrotate /sbin/service named reload 2> /dev/null > /dev/null || true endscript } Then restart bind and the logging you've messed with and you should be all set. -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety'' Benjamin Franklin 1775
On 11/02/06, Chris Mason (Lists) <lists at masonc.com> wrote:> I am having a mail server problem where the mail to one domain is being > sent to the wrong server. > When I use "dig masonc.com mx", I get > > ;; ANSWER SECTION: > masonc.com. 86400 IN MX 5 mail.masonc.com. > > ;; AUTHORITY SECTION: > masonc.com. 86400 IN NS ns1.picadoo.com. > masonc.com. 86400 IN NS ns2.picadoo.com.I don't know if it helps but I can't see any A records for either ns1.picadoo.com or ns2.picadoo.com [wmcdonald at stella ~]$ dig +noall +answer ns1.picadoo.com [wmcdonald at stella ~]$ dig +noall +answer picadoo.com ns picadoo.com. 507112 IN NS ns4.picadoo.com. picadoo.com. 507112 IN NS ns5.picadoo.com. picadoo.com. 507112 IN NS ns7.picadoo.com. What does /etc/resolv.conf on the non-working system say compared to a functioning one that routes mail correctly? Will.