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";
    /*
     * If there is a firewall between you and nameservers you want
     * to talk to, you might need to uncomment the query-source
     * directive below.  Previous versions of BIND always asked
     * questions using port 53, but BIND 8.1 uses an unprivileged
     * port by default.
     */
    // query-source address * port 53;
    version "Surely you must be joking";
    notify no;
           allow-recursion { 63.147.8.0/24 ;
              63.147.9.0/24 ;
              63.144.48.0/24 ;
                          65.121.158.0/23;
                          208.44.160.0/24 ;
                        };
         allow-transfer { 10.0.0.7;
                        };

    forwarders {
        10.0.0.7;
        10.0.0.9;
        };
};
//
// a caching only nameserver config
//
controls {
    inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
    type hint;
    file "named.ca";
};

zone "localhost" IN {
    type master;
    file "localhost.zone";
    allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
    type master;
    file "named.local";
    allow-update { none; };
};



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 wletc.com

Do I need to add the line:?
nameserver 127.0.0.1

The reason I ask is when I do I get error messages when I send.

Thanks
Dave

---------------------------------------------------------------------------------

It's generally a good practice to run a DNS resolver (aka caching nameserver) directly on a QMT host, in which case you would have "nameserver 127.0.0.1" as the first line in your resolv.conf file (nameservers are tried in the sequence they're listed in this file). I personally only specify this and at most one other, since if the first one isn't working then your performance will suffer significantly due to timeouts.

The easiest way I presently use is to install and use powerDNS's recursor:
# yum install pdns-recursor
# service pdns-recursor start
# chkconfig pdns-recorsor on

That, along with the proper /etc/resolv.conf file, should get you going.
To test, use the "dig" command:
# dig qmailtoaster.com
will show you which resolver was used to satisfy the request. dig is a very powerful too. "man dig" for details.


<<attachment: dmilholen.vcf>>

---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
    Vickers Consulting Group offers Qmailtoaster support and installations.
      If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
     Please visit qmailtoaster.com for the latest news, updates, and packages.
     
      To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
     For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Reply via email to