LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   bind9 problem (https://www.linuxquestions.org/questions/linux-software-2/bind9-problem-4175528498/)

!! hack-back !! 12-16-2014 07:03 PM

bind9 problem
 
Code:

Dec 16 20:02:10 fibernet named[3712]: starting BIND 9.8.4-rpz2+rl005.12-P1 -u bind -4
Dec 16 20:02:10 fibernet named[3712]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-l
argefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGC
HASE -O2'
Dec 16 20:02:10 fibernet named[3712]: ----------------------------------------------------
Dec 16 20:02:10 fibernet named[3712]: BIND 9 is maintained by Internet Systems Consortium,
Dec 16 20:02:10 fibernet named[3712]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Dec 16 20:02:10 fibernet named[3712]: corporation.  Support and training for BIND 9 are
Dec 16 20:02:10 fibernet named[3712]: available at https://www.isc.org/support
Dec 16 20:02:10 fibernet named[3712]: ----------------------------------------------------
Dec 16 20:02:10 fibernet named[3712]: adjusted limit on open files from 100000 to 1048576
Dec 16 20:02:10 fibernet named[3712]: found 8 CPUs, using 8 worker threads
Dec 16 20:02:10 fibernet named[3712]: using up to 4096 sockets
Dec 16 20:02:10 fibernet named[3712]: loading configuration from '/etc/bind/named.conf'
Dec 16 20:02:10 fibernet named[3712]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Dec 16 20:02:10 fibernet named[3712]: using default UDP/IPv4 port range: [1024, 65535]
Dec 16 20:02:10 fibernet named[3712]: using default UDP/IPv6 port range: [1024, 65535]
Dec 16 20:02:10 fibernet named[3712]: no IPv6 interfaces found
Dec 16 20:02:10 fibernet named[3712]: listening on IPv4 interface lo, 127.0.0.1#53
Dec 16 20:02:10 fibernet named[3712]: listening on IPv4 interface eth1, 192.168.50.4#53
Dec 16 20:02:10 fibernet named[3712]: listening on IPv4 interface eth0, 89.187.216.30#53
Dec 16 20:02:10 fibernet named[3712]: generating session key for dynamic DNS
Dec 16 20:02:10 fibernet named[3712]: sizing zone task pool based on 7 zones
Dec 16 20:02:10 fibernet named[3712]: set up managed keys zone for view _default, file 'managed-keys.bind'
Dec 16 20:02:10 fibernet named[3712]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: 254.169.IN-ADDR.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: D.F.IP6.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: 8.E.F.IP6.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: 9.E.F.IP6.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: A.E.F.IP6.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: B.E.F.IP6.ARPA
Dec 16 20:02:10 fibernet named[3712]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Dec 16 20:02:10 fibernet named[3712]: command channel listening on 127.0.0.1#953
Dec 16 20:02:10 fibernet named[3712]: zone 0.in-addr.arpa/IN: loaded serial 1
Dec 16 20:02:10 fibernet named[3712]: zone 127.in-addr.arpa/IN: loaded serial 1
Dec 16 20:02:10 fibernet named[3712]: zone 50.168.192.in-addr.arpa/IN: loaded serial 2
Dec 16 20:02:10 fibernet named[3712]: zone 255.in-addr.arpa/IN: loaded serial 1
Dec 16 20:02:10 fibernet named[3712]: zone localhost/IN: loaded serial 2
Dec 16 20:02:10 fibernet named[3712]: zone fibernet.net/IN: loaded serial 1
Dec 16 20:02:10 fibernet named[3712]: managed-keys-zone ./IN: loaded serial 3
Dec 16 20:02:10 fibernet named[3712]: running
Dec 16 20:02:10 fibernet named[3712]: zone 50.168.192.in-addr.arpa/IN: sending notifies (serial 2)



Code:

Dec 16 20:02:43 fibernet named[3712]: lame server resolving '33.44.151.63.in-addr.arpa' (in '44.151.63.in-addr.arpa'?): 208.118.241.250#53
Dec 16 20:02:43 fibernet named[3712]: lame server resolving '33.44.151.63.in-addr.arpa' (in '44.151.63.in-addr.arpa'?): 208.118.255.250#53
Dec 16 20:02:48 fibernet named[3712]: error (unexpected RCODE REFUSED) resolving '179.217.107.209.in-addr.arpa/PTR/IN': 95.177.139.57#53
Dec 16 20:02:48 fibernet named[3712]: error (unexpected RCODE REFUSED) resolving '67.80.51.72.in-addr.arpa/PTR/IN': 205.214.192.201#53
Dec 16 20:02:48 fibernet named[3712]: error (unexpected RCODE REFUSED) resolving '67.80.51.72.in-addr.arpa/PTR/IN': 205.214.192.202#53
Dec 16 20:02:48 fibernet named[3712]: error (unexpected RCODE REFUSED) resolving '179.217.107.209.in-addr.arpa/PTR/IN': 95.177.139.50#53
Dec 16 20:02:49 fibernet named[3712]: lame server resolving '114.163.39.70.in-addr.arpa' (in '163.39.70.in-addr.arpa'?): 64.235.225.10#53
Dec 16 20:02:49 fibernet named[3712]: lame server resolving '130.163.39.70.in-addr.arpa' (in '163.39.70.in-addr.arpa'?): 64.235.225.10#53
Dec 16 20:02:50 fibernet named[3712]: error (connection refused) resolving '114.163.39.70.in-addr.arpa/PTR/IN': 216.193.212.140#53
Dec 16 20:02:50 fibernet named[3712]: lame server resolving '145.163.39.70.in-addr.arpa' (in '163.39.70.in-addr.arpa'?): 64.235.225.10#53
Dec 16 20:02:51 fibernet named[3712]: error (connection refused) resolving '145.163.39.70.in-addr.arpa/PTR/IN': 64.235.225.5#53
Dec 16 20:02:51 fibernet named[3712]: error (connection refused) resolving '64.152.155.204.in-addr.arpa/PTR/IN': 78.140.155.8#53
Dec 16 20:02:51 fibernet named[3712]: error (connection refused) resolving '64.152.155.204.in-addr.arpa/PTR/IN': 78.140.155.9#53
Dec 16 20:02:53 fibernet named[3712]: error (connection refused) resolving '65.152.155.204.in-addr.arpa/PTR/IN': 78.140.155.8#53
Dec 16 20:02:53 fibernet named[3712]: error (connection refused) resolving '65.152.155.204.in-addr.arpa/PTR/IN': 78.140.155.9#53
Dec 16 20:02:54 fibernet named[3712]: error (connection refused) resolving '65.152.155.204.in-addr.arpa/PTR/IN': 78.140.155.8#53
Dec 16 20:02:54 fibernet named[3712]: error (connection refused) resolving '65.152.155.204.in-addr.arpa/PTR/IN': 78.140.155.9#53


Code:

/etc/bind/named.conf.options
 forwarders {
 # Give here your ISP DNS IP’s
#192.168.1.1;    # gateway or router
182.176.39.23;
182.176.18.13;
68.87.76.178;
  };
dnssec-enable yes;
dnssec-validation yes;



/etc/bind/named.conf.local

# Our forward zone
zone "net.net" {
 type master;
 file "/etc/bind/zones/db.net.net";
 };

# Our reverse Zone
# Server IP 192.168.1.5
zone "1.168.192.in-addr.arpa" {
  type master;
  file "/etc/bind/zones/db.192";
 };


smallpond 12-17-2014 11:52 AM

and what is the problem you are having?


All times are GMT -5. The time now is 03:57 PM.