On 08/30/2013 01:19 PM, Jim Shupert wrote:
here are contents of /etc/resolv.conf
search pps-inc.com
nameserver 216.136.95.2
nameserver 192.168.200.226
===================
the above refers to 2 other machines that are running bind dns
Right. The first is twtelecom, presumably your ISP.
The second (which would only be used if the first one had a problem) is
running on your local network.
And that might not be the *smart move*
It's not ideal. It's not quite as efficient as it might be, plus you're
primarily at the mercy of your ISP for correct name resolution.
I take it you think I should be running dns on my mailserver?
A resolver, yes. (NOT an authoritative DNS server though).
and the dns pkg of choice is pdns-recursor
Yes.
install w
# yum install pdns-recursor
# service named stop
# service pdns-recursor start
# chkconfig named off
# chkconfig pdns-recursor on
- all I have to have in the conf is one line -- 'localhost'?
nameserver 127.0.0.1
Correct. The dns resolving service (pdns-recursor) runs on the QMT host
itself.
You might leave the
nameserver 216.136.95.2
line in there listed 2nd as a backup resolver, but I prefer to know if
my localhost resolver is having an issue. Not having a backup lets me
know rather quickly. ;)
If you feel better using a backup resolver, I would consider using
google (8.8.8.8, 4.4.4.4) or opendns (208.67.220.220, 208.67.222.222) as
backup resolvers. They both have good reputations for reliability.
what about allow-from
http://www.thatfleminggent.com/2009/08/09/getting-a-powerdns-recursor-up-and-going-fast
pdns-recursor will allow requests from localhost by default. If you want
to use this server as a resolver for other hosts on your network, you
can tailor this and your firewall appropriately.
That link is a little dated, as pdns-recursor is now in the base el5 repo.
I am not an 'expert' with dns
Thanks for the help!
Sure. We all learn a little along the way.
Now that I'm looking at this again, I realize that you need *absolutely
nothing* in your /etc/resolv.conf file. Linux uses itself by default. :)
I may just begin making a habit of installing pdns-recursor on all my
servers and leaving /etc/resolv.conf empty. One less thing to deal with.
--
-Eric 'shubes'
On 8/30/2013 11:16 AM, Eric Shubert wrote:
QMT has been patched with what is pretty much the cream of the crop of
patches for qmail. See "rpm -qi qmail-toaster". The bigdns patch is
included.
There might be one or two patches from jms which I might consider
including in a future release, but I'm not aware of any patches that
are what I'd consider to be urgent. I'll be revisiting patches when I
put the source code on git, which I plan to do after the QMT 1.5
(COS6) release.
Some resolvers have difficulty resolving DNS records which may be set
up in an peculiar way. (I'm not surprised that a government entity
would be using a peculiar configuration. ;) ) Using a different
resolver may be helpful.
Which dns resolver are you using? Please post contents of
/etc/resolv.conf file. I would expect using pdns-recursor might solve
your problem. You can use pdns-recursor by doing the following:
# yum install pdns-recursor
# service named stop
# service pdns-recursor start
# chkconfig named off
# chkconfig pdns-recursor on
You only need the commands regarding named if you're currently running
a bind resolver (caching-nameserver package is installed).
Then change /etc/resolv.conf to be:
nameserver 127.0.0.1
That should do it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
