It's an issue with the new version of Bind - 8.2.2 seems to ping the
network on startup, whereas the previous version did not. I haven't
found a way around this behaviour but that doesn't mean there isn't
one. I noticed this behaviour when I was an early 8.2 adapter via the
ports.
- Mike H.
Date: Sat, 25 Dec 1999 00:50:01 +0300
From: Lev Serebryakov [EMAIL PROTECTED]
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Sender: [EMAIL PROTECTED]
X-Loop: FreeBSD.ORG
Precedence: bulk
X-RULES: lists
Hi, All!
I've upgraded from 3.3-STABLE to 3.4-STABLE and notice strange
thing:
I have ``named'' run on my machine, which have only dial-up
Internet connection. I have ``ppp -nat -auto provider'' run too.
My named have configured to be primary NS in my network (domain is
not registered and IP addresses are from 192.168.xx.xx range).
Also, named have ``forward-only'' option and two addresses of my
ISP DNS.
Whet it was 3.3-STABLE (really -- 3.3-RELEASE with stable kernel)
everything works perfectly. PPP doesn't call my ISP until I (or
somebody in local network) need connection.
But with new system (3.4-RELEASE) ``named'' initiate dial-up just
after start! Why new named want to connect when there is no any
outgoing packets? How could I disable such behavior?
Lev Serebryakov, 2:5030/661.0
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message