Reply To: DNS setup

Home Page Forums Network Management Networking DNS setup Reply To: DNS setup

#48646

kphung
Member

Thanks I try to rebuild the file, still not work.

Just use as router and DNS only No firewall rules had been seted
DNS start logging as :

10:00:27 starting BIND 9.5.1-P2
10:00:27 adjusted limit on open files from 1024 to 1048576
10:00:27 found 1 CPU, using 1 worker thread
10:00:27 using up to 4096 sockets
10:00:27 loading configuration from ‘/etc/named.conf’
10:00:27 using default UDP/IPv4 port range: [1024, 65535]
10:00:27 using default UDP/IPv6 port range: [1024, 65535]
10:00:27 no IPv6 interfaces found
10:00:27 listening on IPv4 interface lo, 127.0.0.1#53
10:00:27 listening on IPv4 interface ETH00:00, 203.xxx.xxx.xxx#53
10:00:27 listening on IPv4 interface ETH00:01, 192.168.0.75#53
10:00:27 listening on IPv4 interface dummy0, 192.168.141.142#53
10:00:27 listening on IPv4 interface VPN99:00, 192.168.250.254#53
10:00:27 listening on IPv4 interface dummy1, 192.168.142.142#53
10:00:27 automatic empty zone: 0.IN-ADDR.ARPA
10:00:27 automatic empty zone: 127.IN-ADDR.ARPA
10:00:27 automatic empty zone: 254.169.IN-ADDR.ARPA
10:00:27 automatic empty zone: 2.0.192.IN-ADDR.ARPA
10:00:27 automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
10:00:27 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
10:00:27 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
10:00:27 automatic empty zone: D.F.IP6.ARPA
10:00:27 automatic empty zone: 8.E.F.IP6.ARPA
10:00:27 automatic empty zone: 9.E.F.IP6.ARPA
10:00:27 automatic empty zone: A.E.F.IP6.ARPA
10:00:27 automatic empty zone: B.E.F.IP6.ARPA
10:00:27 command channel listening on 127.0.0.1#953
10:00:27 zone salonmedia.com/IN: sending notifies (serial 2009081601)
10:00:27 zone 127-64.xxx.xxx.203.in-addr-arpa/IN: sending notifies (serial 2009082502)
10:00:34 lame server resolving ‘122.127-64.xxx.xxx.203.in-addr.arpa’ (in ‘127-64.xxx.xxx.203.in-addr.arpa’?): 203.xxx.xxx.71#53
10:00:34 connection refused resolving ‘122.127-64.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.126#53
10:00:40 connection refused resolving ‘122.127-64.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.126#53
10:00:40 lame server ‘126.127-64.xxx.xxx.203.in-addr.arpa’ (in ‘127-64.xxx.xxx.203.in-addr.arpa’?): 203.xxx.xxx.71#53
10:00:40 connection refused resolving ‘126.127-64.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.126#53
10:00:49 connection refused resolving ‘126.127-64.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.126#53
10:01:02 connection refused resolving ‘126.127-64.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.126#53
10:01:15 message repeated 2 times
10:01:28 no IPv6 interfaces found