Net Qmail Big-dns Patch

Hi:I am running QmailToaster and have been for many years. In addition I have changed out DNS programs on the mail server totry to help i.e.caching-nameserverpdns-recursordjbdns (rbldnsd)Currently, I have DNS lookups pointed to a Windows DNS server with thesame issue. Doing a dig or nslookup on the mx records shows a validmx record.Does anyone have an idea as to the problem?Thanks,EdYou remembered to change your /etc/resolv.conf file with theseresolvers, right?(nameserver 127.0.0.1)I recommend using pdns-recursor, installed on the QMT host. PowerDNS isa modern, efficient, well maintained resolver. If that has an issueresolving something, the problem is likely with the target domain's DNSrecords. In addition I have changed out DNS programs on the mail server totry to help i.e.caching-nameserverpdns-recursordjbdns (rbldnsd)Currently, I have DNS lookups pointed to a Windows DNS server with thesame issue. Doing a dig or nslookup on the mx records shows a validmx record.Does anyone have an idea as to the problem?Thanks,EdYou remembered to change your /etc/resolv.conf file with theseresolvers, right?(nameserver 127.0.0.1)I recommend using pdns-recursor, installed on the QMT host.

PowerDNSis a modern, efficient, well maintained resolver. If that has an issueresolving something, the problem is likely with the target domain'sDNS records.Hi Eric:Yes, I did change the resolv.conf to to reflect only the 127.0.0.1.But Dig works for the domains see below:.@qmail # dig mx teichert.com; DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx teichert.com;; global options: printcmd;; Got answer:;; -HEADER DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx blm.gov;; global options: printcmd;; Got answer:;; -HEADER DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx tahoe.ca.gov;; global options: printcmd;; Got answer:;; -HEADER. In addition I have changed out DNS programs on the mail server totry to help i.e.caching-nameserverpdns-recursordjbdns (rbldnsd)Currently, I have DNS lookups pointed to a Windows DNS server with thesame issue. Doing a dig or nslookup on the mx records shows a validmx record.Does anyone have an idea as to the problem?Thanks,EdYou remembered to change your /etc/resolv.conf file with theseresolvers, right?(nameserver 127.0.0.1)I recommend using pdns-recursor, installed on the QMT host.

PowerDNSis a modern, efficient, well maintained resolver. If that has an issueresolving something, the problem is likely with the target domain'sDNS records.Yes, I did change the resolv.conf to to reflect only the 127.0.0.1.; DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx teichert.com;; global options: printcmd;; -HEADER DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx blm.gov;; global options: printcmd;; -HEADER DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx tahoe.ca.gov;; global options: printcmd;; -HEADER. In addition I have changed out DNS programs on the mail server totry to help i.e.caching-nameserverpdns-recursordjbdns (rbldnsd)Currently, I have DNS lookups pointed to a Windows DNS server with thesame issue. Doing a dig or nslookup on the mx records shows a validmx record.Does anyone have an idea as to the problem?Thanks,EdYou remembered to change your /etc/resolv.conf file with theseresolvers, right?(nameserver 127.0.0.1)I recommend using pdns-recursor, installed on the QMT host.

PowerDNSis a modern, efficient, well maintained resolver. If that has an issueresolving something, the problem is likely with the target domain'sDNS records.Yes, I did change the resolv.conf to to reflect only the 127.0.0.1.; DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx teichert.com;; global options: printcmd;; -HEADER DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx blm.gov;; global options: printcmd;; -HEADER DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx tahoe.ca.gov;; global options: printcmd;; -HEADER. I don't know qmail-remote in depth, but is it perhaps checking thesender's domain and choking on that?Maybe but I am not very familiar with it myself.One thing that is weird with dns on this system. It doesn't matter whatdns program I setup on it.

Net Qmail Big-dns Patch Free

It will not use it to resolve dns queries.I have tried powerdns and caching-nameserver and pointed resolv.conf toitself (127.0.0.1) but any dns queries will not resolve. I havedisabled selinux and iptables to remove them from the equation with noresults. I have to point resolv.conf to my windows dns server for qmailand dns to work.Thanks,Ed-To unsubscribe, e-mail: qmailtoaster-list-.@qmailtoaster.comFor additional commands, e-mail: qmailtoaster-list-.@qmailtoaster.com.

In addition I have changed out DNS programs on the mail server totry to help i.e.caching-nameserverpdns-recursordjbdns (rbldnsd)Currently, I have DNS lookups pointed to a Windows DNS server with thesame issue. Doing a dig or nslookup on the mx records shows a validmx record.Does anyone have an idea as to the problem?Thanks,EdYou remembered to change your /etc/resolv.conf file with theseresolvers, right?(nameserver 127.0.0.1)I recommend using pdns-recursor, installed on the QMT host. PowerDNSis a modern, efficient, well maintained resolver. If that has an issueresolving something, the problem is likely with the target domain'sDNS records.Yes, I did change the resolv.conf to to reflect only the 127.0.0.1.; DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx teichert.com;; global options: printcmd;; -HEADER DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx blm.gov;; global options: printcmd;; -HEADER DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el58.6 mx tahoe.ca.gov;; global options: printcmd;; -HEADER. I don't know qmail-remote in depth, but is it perhaps checking thesender's domain and choking on that?Maybe but I am not very familiar with it myself.One thing that is weird with dns on this system. It doesn't matter whatdns program I setup on it. It will not use it to resolve dns queries.

Net Qmail Big-dns Patch 2017

Ihave tried powerdns and caching-nameserver and pointed resolv.conf toitself (127.0.0.1) but any dns queries will not resolve. I havedisabled selinux and iptables to remove them from the equation with noresults. I have to point resolv.conf to my windows dns server for qmailand dns to work.Thanks,Ed-I would try installing pdns-recursor again:# yum install pdns-recursorI think you'll need to start the service:# service pdns-recursorand make sure it's started on reboot:# chkconfig pdns-recursor onThen test:# dig @127.0.0.1 somedomain.comIf that comes back successful, then activate it by puttingnameserver 127.0.0.1as the first nameserver line in your /etc/resolv.conf file.This has worked for me.