BIND 9.4.2 Debian setup

Vladimir Shingarev telelvis at gmail.com
Wed Feb 20 14:11:38 UTC 2008 

Hello everyone. I am trying to relocate old BIND server running on
FreeBSD4.10 to new Debian Etch-r3 setup. So I transferred all
named.conf and zones (about 300) to new server and starts bind - it's
starts and works perfectly. But when I assign to this new installation
ip address of old DNS - so users may query it without changing their
conf - it actually doesnt work. System has about dns 200 queries/sec.
Compiling BIND from sources - it doesnt help. Hardware is Xeon2.40GHz
x 2 with 1 Gb ram and 2 Gb swap. Thanks for any advice

System is DebianEtch 4.0r3
man:/home/sva# uname -a
Linux man 2.6.18-5-686 #1 SMP Mon Dec 24 16:41:07 UTC 2007 i686 GNU/Linux
man:/home/sva# named -v
BIND 9.4.2

Syslog:
Feb 20 14:56:04 man named[14223]: starting BIND 9.4.2 -u bind
Feb 20 14:56:04 man named[14223]: loading configuration from
'/etc/bind/named.conf'
Feb 20 14:56:04 man named[14223]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 20 14:56:04 man named[14223]: listening on IPv4 interface eth1:0,
81.25.0.33#53
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
127.IN-ADDR.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
254.169.IN-ADDR.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
2.0.192.IN-ADDR.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
255.255.255.255.IN-ADDR.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
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
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
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
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
D.F.IP6.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
8.E.F.IP6.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
9.E.F.IP6.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
A.E.F.IP6.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view internal:
B.E.F.IP6.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
127.IN-ADDR.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
254.169.IN-ADDR.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
2.0.192.IN-ADDR.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
255.255.255.255.IN-ADDR.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
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
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
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
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
D.F.IP6.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
8.E.F.IP6.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
9.E.F.IP6.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
A.E.F.IP6.ARPA
Feb 20 14:56:04 man named[14223]: automatic empty zone: view external:
B.E.F.IP6.ARPA
Feb 20 14:56:04 man named[14223]: command channel listening on 127.0.0.1#953
Feb 20 14:56:04 man named[14223]: zone ./IN/internal: NS
'ns.tts.nov.ru' has no address records (A or AAAA)
Feb 20 14:56:04 man named[14223]: zone ./IN/internal: loaded serial 2007021201
Feb 20 14:56:04 man named[14223]: zone com/IN/internal: loaded serial 2007021201
Feb 20 14:56:04 man named[14223]: zone net/IN/internal: loaded serial 2007021201
Feb 20 14:56:04 man named[14223]: zone org/IN/internal: loaded serial 2007021201
Feb 20 14:56:04 man named[14223]: zone ru/IN/internal: loaded serial 2007101501
Feb 20 14:56:04 man named[14223]: zone alcatel7300/IN/external: loaded
serial 2006021001

---   HERE COMES ABOUT ~300 ZONES LOADING  ---
..................
---   AND ACTUALLY ERRORS ------

Feb 20 14:56:55 man named[14223]: internal_send: 194.64.40.71#33421:
Invalid argument
Feb 20 14:56:55 man named[14223]: client 194.64.40.71#33421: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send: 66.111.111.55#32768:
Invalid argument
Feb 20 14:56:55 man named[14223]: client 66.111.111.55#32768: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send: 87.245.155.130#32769:
Invalid argument
Feb 20 14:56:55 man named[14223]: client 87.245.155.130#32769: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send: 87.245.155.130#32769:
Invalid argument
Feb 20 14:56:55 man named[14223]: client 87.245.155.130#32769: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send: 138.81.11.14#54989:
Invalid argument
Feb 20 14:56:55 man named[14223]: client 138.81.11.14#54989: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send: 138.81.11.14#54989:
Invalid argument
Feb 20 14:56:55 man named[14223]: client 138.81.11.14#54989: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send: 138.81.11.14#54989:
Invalid argument
Feb 20 14:56:55 man named[14223]: client 138.81.11.14#54989: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send: 195.235.26.4#61891:
Invalid argument
Feb 20 14:56:55 man named[14223]: client 195.235.26.4#61891: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send:
217.116.100.235#34011: Invalid argument
Feb 20 14:56:55 man named[14223]: client 217.116.100.235#34011: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send: 195.49.216.15#3553:
Invalid argument
Feb 20 14:56:55 man named[14223]: client 195.49.216.15#3553: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send: 78.36.131.148#1027:
Invalid argument
Feb 20 14:56:55 man named[14223]: client 78.36.131.148#1027: view
external: error sending response: invalid file
Feb 20 14:56:55 man named[14223]: socket.c:1179: unexpected error:
Feb 20 14:56:55 man named[14223]: internal_send: 213.164.0.7#32771:
Invalid argument

And so errors repeat for every query

Interesting moment:
When I disconnect network cable from server physically, then assign
proper ip address, restart bind, give it some time to load up, AND
actually plug in cable - when bind runs some time, anwer queries, but
freezes with some time passing.

-- 
Vladimir Shingarev

More information about the bind-users mailing list