[qmailtoaster] Re: resolv.conf

2012-01-25 Thread Eric Shubert
That's what I'd do. # yum remove bind # yum install pdns-recursor # service pdns-recursor start # dig @127.0.0.1 yahoo.com (to be sure it's working) # chkconfig pdns-recorsor on That should do it. Also be sure that nameserver 127.0.0.1 is the first (and perhaps only) line in your resolv.conf fil

Re: [qmailtoaster] Re: resolv.conf

2012-01-25 Thread David
hmm, Ok, well I guess its about time I did something with this server since it has been set this way since the beginning 7yrs ago :) I have always noticed some performance issues related to our dns and mail. So, I guess my first step would be to remove Bind and install powerdns or visa versa

[qmailtoaster] Re: resolv.conf

2012-01-25 Thread Eric Shubert
Rather than messing with resolv.conf file to see what happens from each resolver, use the @ option with dig. Then you'll know specifically what each server gives you. If it were me, I'd 86 the authoritative DNS on QMT (do you *really* need that there?), and install powerdns-recursor there and

Re: [qmailtoaster] Re: resolv.conf

2012-01-25 Thread David
If I go into the resolv and set nameserver to one of my current nameservers IP and do a dig on any of the ones that did not resolv I will get an answer and when I put 127.0.0.1 as the nameserver I will finally get an answer, but if I try another domain that has not been queried then it will def

Re: [qmailtoaster] Re: resolv.conf

2012-01-25 Thread David
It still comes back with no answer section just list root servers On 01/25/2012 03:32 PM, Eric Shubert wrote: Can you # dig @127.0.0.1 somedomain.com ? (on QMT host) On 01/25/2012 02:21 PM, David wrote: Strike that... Still having issues almost like its not looking any deeper than 127.0.0.1 fo

[qmailtoaster] Re: resolv.conf

2012-01-25 Thread Eric Shubert
Can you # dig @127.0.0.1 somedomain.com ? (on QMT host) On 01/25/2012 02:21 PM, David wrote: Strike that... Still having issues almost like its not looking any deeper than 127.0.0.1 for a resolv. On 01/25/2012 03:09 PM, David wrote: Eric, I think I may have it.. I had to review my hosts and re

Re: [qmailtoaster] Re: resolv.conf

2012-01-25 Thread David
Strike that... Still having issues almost like its not looking any deeper than 127.0.0.1 for a resolv. On 01/25/2012 03:09 PM, David wrote: Eric, I think I may have it.. I had to review my hosts and resolv.conf files they looked a little screwy so I set them with typical settings with my do

Re: [qmailtoaster] Re: resolv.conf

2012-01-25 Thread David
Eric, I think I may have it.. I had to review my hosts and resolv.conf files they looked a little screwy so I set them with typical settings with my domain info I also took a closer look at my dns. I believe the real problem was in the host and resolv.conf files because it is moving so muc

Re: [qmailtoaster] Re: resolv.conf

2012-01-25 Thread David
All 3 are authoritative with one being the master. I may have it working but seems it still doesnt resolv mxtoolbox.com On 01/25/2012 02:37 PM, Eric Shubert wrote: Are the 3 servers authoritative? It's generally a good practice to keep authoritative DNS servers separate from recursors. Of co

Re: [qmailtoaster] Re: resolv.conf

2012-01-25 Thread David
Sry for all the inline post but Im bouncing between 2 issues at the moment here is a partial copy of my config on the nameserver in question : options { directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; /*

[qmailtoaster] Re: resolv.conf

2012-01-25 Thread Eric Shubert
Are the 3 servers authoritative? It's generally a good practice to keep authoritative DNS servers separate from recursors. Of course it can be done, but it typically leads to problems. On 01/25/2012 01:31 PM, David wrote: Currently I have 3 DNS servers running here at the NOC and the mail se

Re: [qmailtoaster] Re: resolv.conf

2012-01-25 Thread Phil Leinhauser
Where do your DNS servers go for lookups?  Are you going to root servers or are you using your providers servers?  It seems something upstream of your server is goofy. > Currently I have 3 DNS servers running here at the NOC and the mail > server is on one of the slaves. > I did a few dig comm

Re: [qmailtoaster] Re: resolv.conf

2012-01-25 Thread David
Do I need to allow recursive on 127.0.0.1? On 01/25/2012 02:12 PM, Eric Shubert wrote: On 01/25/2012 12:44 PM, David wrote: calling on the collective :) My resolv.conf looks like this: nameserver 63.147.8.8 <--- MX server nameserver 63.147.8.7 nameserver 63.147.8.9 domain wletc.com search wle

Re: [qmailtoaster] Re: resolv.conf

2012-01-25 Thread David
Currently I have 3 DNS servers running here at the NOC and the mail server is on one of the slaves. I did a few dig commands and it seems to resolv the popular domain request like yahoo,google,msn,hotmail and others but I could not resolv mxtoolbox.com or freeside.biz Is there something wrong

[qmailtoaster] Re: resolv.conf

2012-01-25 Thread Eric Shubert
On 01/25/2012 12:44 PM, David wrote: calling on the collective :) My resolv.conf looks like this: nameserver 63.147.8.8 <--- MX server nameserver 63.147.8.7 nameserver 63.147.8.9 domain wletc.com search wletc.com Do I need to add the line:? nameserver 127.0.0.1 The reason I ask is when I do I