named logs RCODE REFUSE?

Discussion in 'Installation/Configuration' started by lyndros, May 25, 2007.

  1. lyndros

    lyndros New Member

    anyone knows something about this entries in named logs. what's that?

    May 23 04:00:03 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.236.201#53
    May 23 04:00:03 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.237.222#53
    May 23 04:00:03 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.236.201#53
    May 23 04:00:03 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.237.222#53
    May 23 04:00:04 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.236.201#53
    May 23 04:00:04 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.237.222#53
    May 23 04:00:04 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.236.201#53
    May 23 04:00:04 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.237.222#53
    May 23 04:01:08 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving 'dns2.xm.fj.cn/A/IN': 202.101.103.55#53

    lots of this entries ...
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

  3. lyndros

    lyndros New Member

  4. falko

    falko Super Moderator ISPConfig Developer

    What's in your named.conf?
     
  5. lyndros

    lyndros New Member

    here we go:

    options {
    pid-file "/var/run/bind/run/named.pid";
    directory "/etc/bind";
    auth-nxdomain no;
    /*
    * 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;
    allow-recursion {
    127.0.0.1;
    LOCAL_IP_NAMESERVER1;
    IP_NAMESERVER2;
    };
    };

    //
    // a caching only nameserver config
    //
    zone "." {
    type hint;
    file "db.root";
    };

    zone "0.0.127.in-addr.arpa" {
    type master;
    file "db.local";
    };

    zone "XXX.XXX.XXX.in-addr.arpa" {
    type master;
    file "pri.XXX.XXX.XXX.in-addr.arpa";
    };

    zone...

    thks

    PD: Now i've tried including on named.conf this lines:

    // Do not log zones that aren't registered in this server (lame servers)

    logging {
    category lame-servers {null; };
    };

    it's strange but error happens when logcheck cronjob finish... but the ip error isn't the local ip... any idea?
    last modification less messages appears...but still there...
     
    Last edited: May 28, 2007
  6. lyndros

    lyndros New Member

    any idea on that?
     

Share This Page