can't-resolve

[Mohammed Ejaz]

Thank you stevean kind co-operation. 


as you said I modified the logging sections.  but still external domains are
unable to resolve.   I wanted tell you one more thing when I reassign my old
IP which is 212.119.64.12 then everything works fine (I mean interal
autherative domain and external yahoo etc.... )without any problem 


options {
        directory "/var/named";
        listen-on port 53 { 212.119.64.228; 212.119.64.226; 212.119.64.12;};
version "Have a nice day!, Good Bye";
recursion yes;
notify no;
};


logging {
    channel bind_syslog {
    file "/var/log/named/bind_sys.log" versions 3 size 5m;
#        syslog daemon;
        severity info;
    };
    category default { bind_syslog; };
};


log file 

bash-2.03# tail -f /var/log/named/bind_sys.log
zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 3
zone makksab.com/IN: loaded serial 2005032202
zone localhost/IN: loaded serial 3
zone cyberiamall.net/IN: loaded serial 2005032202
zone kalam.net.sa/IN: loaded serial 2005032202
running
sloading configuration from '/etc/named.conf'
no IPv6 interfaces found
zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 3
zone makksab.com/IN: loaded serial 2005032202
zone localhost/IN: loaded serial 3
zone cyberiamall.net/IN: loaded serial 2005032202
zone kalam.net.sa/IN: loaded serial 2005032202
running

-----Original Message-----
From: bind-users-bounces at lists.isc.org
[mailto:bind-users-bounces at lists.isc.org] On Behalf Of Steven Carr
Sent: Thursday, December 25, 2014 12:29 PM
To: Bind users
Subject: Re: can't-resolve

On 25 December 2014 at 08:05, Mohammed Ejaz <mejaz at cyberia.net.sa> wrote:
> logging {
>
>         channel querylog{
>
>                     file "/var/log/querylog";
>                     severity debug 10;
>                     print-category yes;
>                     print-time yes;
>                     print-severity yes;
>                     };
>
>        category queries { querylog;}; };

OK so you only have query logging enabled, enable additional logging and it
will more than likely point you to the error, BIND is issueing a SERVFAIL
for the query which means it will dump an error message into syslog (when
configured).

Something like the following will pump all other messages to syslog...

logging {
    channel bind_syslog {
        syslog daemon;
        severity info;
    };
    category default { bind_syslog; };
};

Steve
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to
unsubscribe from this list

bind-users mailing list
bind-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

--