BIND keeps my connection alive

David Botham dns at botham.net
Wed Sep 25 17:52:54 UTC 2002



Check the BIND ARM for "dialup"... These options may be of use.


Dave...
> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of Lejf Diecks
> Sent: Wednesday, September 25, 2002 4:23 AM
> To: comp-protocols-dns-bind at isc.org
> Subject: BIND keeps my connection alive
> 
> 
> Hi,
> 
> I'm connected to the Internet via ADSL (Dial-On-Demand). The System
runs
> RedHat 7.3 (Kernel 2.4.18-3) and acts as a router/DNS-Server (BIND
9.2.1).
> 
> Once a connection is established, the router stays online. Using
"tcpdump"
> shows the reason: my DNS-server generates permanently traffic and
keeps
> the
> connection alive. The dump shows my providers DNS-Server and a lot of
> other
> addresses, too.
> 
> This looks to me like an update between my DNS-Server and other
machines
> (???). How do I stop this behavior? (The config files I've changed are
> below).
> 
> Regards,
> Lejf
> 
> ----- config files for BIND 9.2.1 on RedHat Linux 7.3 ------
> 
> //////////////////// named.conf ///////////////////////////
> // generated by named-bootconf.pl
> 
> options {
> 
> // hier liegen die config-files!
> 
> directory "/var/named";
> 
> /*
> 
> * 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;
> 
> //
> 
> // a caching only nameserver config
> 
> //
> 
> forwarders {
> 
> 194.25.2.129;
> 
> 194.25.2.130;
> 
> 194.25.2.131;
> 
> 194.25.2.132;
> 
> 194.25.2.133;
> 
> 194.25.2.134;
> 
> };
> 
> };
> 
> controls {
> 
> inet 127.0.0.1 allow { localhost; } keys { rndckey; };
> 
> };
> 
> zone "." IN {
> 
> type hint;
> 
> file "named.ca";
> 
> };
> 
> zone "localhost" IN {
> 
> type master;
> 
> file "localhost.zone";
> 
> allow-update { none; };
> 
> };
> 
> zone "0.0.127.in-addr.arpa" IN {
> 
> type master;
> 
> file "named.local";
> 
> allow-update { none; };
> 
> };
> 
> // DNS fuer unsere interne Domaene "hardebek.dom"
> 
> zone "hardebek.dom" IN {
> 
> type master;
> 
> file "hardebek.dom";
> 
> allow-update { none; };
> 
> };
> 
> // reverse DNS fuer unsere interne Domaene "hardebek.dom"
> 
> zone "1.100.10.in-addr.arpa" IN {
> 
> type master;
> 
> file "10.100.1.1";
> 
> allow-update { none; };
> 
> };
> 
> include "/etc/rndc.key";
> 
> 
> //////////////////// resolv.conf ///////////////////////////
> search hardebek.dom
> 
> #nameserver 194.25.2.129
> 
> nameserver 127.0.0.1
> 
> 
> //////////////////// hardebek.dom ///////////////////////////
> $TTL 2D
> 
> hardebek.dom. IN SOA @ root.localhost. (
> 
> 2001013334 ; serial
> 
> 1D ; refresh
> 
> 2H ; retry
> 
> 1W ; expiry
> 
> 2D ) ; minimum
> 
> IN NS @
> 
> IN A 10.100.1.1
> 
> 
> server.hardebek.dom. IN A 10.100.1.1
> 
> pc2s1.hardebek.dom. IN A 10.100.1.2
> 
> pc3s1.hardebek.dom. IN A 10.100.1.3
> 
> pc4s1.hardebek.dom. IN A 10.100.1.4
> 
> .
> 
> .
> 
> pc254s1.hardebek.dom. IN A 10.100.1.254
> 
> //////////////////// 10.100.1.1 ///////////////////////////
> $TTL 2D
> 
> @ IN SOA server.hardebek.dom. root.localhost. (
> 
> 2001013335 ; serial
> 
> 1D ; refresh
> 
> 2H ; retry
> 
> 1W ; expiry
> 
> 2D ) ; minimum
> 
> NS server.hardebek.dom.
> 
> 
> 1 PTR server.hardebek.dom.
> 
> 2 PTR pc2s1.hardebek.dom.
> 
> 3 PTR pc3s1.hardebek.dom.
> 
> .
> 
> .
> 
> 254 PTR pc254s1.hardebek.dom.
> 
> 
> 
> 




More information about the bind-users mailing list