Bind 9.2.3 very, very slow starup

[Vinny Abello]

Although I've always had the best luck with Intel NICs, I've seen NICs do 
very strange things on/to machines before so you never know.

At 10:54 AM 7/16/2004, Eric Dynowski wrote:
>Vinny,
>
>Yes, I would agree, but I hadn't noticed the slow performance of the Intel
>NIC until late yesterday when trying to copy files from it. Im not sure if
>it's a hardware problem or kernel/driver issue interacting with bind.. I
>would expect that the NIC would wither work or not work, not sort of in
>between.
>
>Eric.
>
> > Sounds like you plain and simple just have a hardware problem which some
> > people suggested. This will affect anything as you've seen with your scp.
> >
> > At 07:29 AM 7/16/2004, Eric Dynowski wrote:
> >>Everyone,
> >>
> >>Just an update..
> >>
> >>I was about to rebuild bind on another machine and replace this one
> >>because I was ran out other ideas. So I tar'ed up the /etc/bind direcory
> >>to copy over, and noticed the copy (scp) was very, very, very slow.. So I
> >>disabled the on board Intel NIC, installed a Netgear, and recompiled the
> >>Kernel (2.4.18) without EtherExpress Pro support and with DEC Tulip
> >>support, then rebooted and bind started perfectly the first time.
> >>
> >>Because this is a production server, Im still affraid to restart bind and
> >>find out if this really solved the problem. I guess we will see what
> >>happens the next time I try and restart. Has anyone ever seen a problem
> >>with bind relating to network kernel drivers? I have tried different
> >>kernel versions up to 2.6..
> >>
> >>Strange..
> >>
> >>Eric.
> >>
> >> > On Tue, 2004-07-13 at 19:20, Eric Dynowski wrote:
> >> >> > At 01:46 PM 7/13/2004, Eric Dynowski wrote:
> >> >> >>Danny,
> >> >> >>
> >> >> >>There are no errors in the logs, so I am assuming there are none in
> >> >> the
> >> >> >>zone files. I have removed all zones but one and still the same
> >> >> problem
> >> >> >>occurs.
> >> >> >>
> >> >> >>Eric.
> >> >> >
> >> >> > run named-checkzone to make sure and named-checkconf.
> >> >> >
> >> >> > Danny
> >> >> >
> >> >> >
> >> >>
> >> >> Danny,
> >> >>
> >> >> named-checkzone, and named-checkconf return all OK. No problems
> >> found.
> >> >>
> >> >> I ran named-checkzone on all of our zone files.
> >> >>
> >> >> Eric.
> >> >
> >> > One thing comes to mind, are you starting named *BEFORE* you have your
> >> > network connections up and active?
> >> >
> >> > --
> >> > G. Roderick Singleton <gerry at pathtech.org>
> >> > PATH tech
> >> >
> >> >
> >
> >
> > Vinny Abello
> > Network Engineer
> > Server Management
> > vinny at tellurian.com
> > (973)300-9211 x 125
> > (973)940-6125 (Direct)
> > PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0  E935 5325 FBCB 0100 977A
> >
> > Tellurian Networks - The Ultimate Internet Connection
> > http://www.tellurian.com (888)TELLURIAN
> >
> > There are 10 kinds of people in the world. Those who understand binary and
> > those that don't.
> >
> >


Vinny Abello
Network Engineer
Server Management
vinny at tellurian.com
(973)300-9211 x 125
(973)940-6125 (Direct)
PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0  E935 5325 FBCB 0100 977A

Tellurian Networks - The Ultimate Internet Connection
http://www.tellurian.com (888)TELLURIAN

There are 10 kinds of people in the world. Those who understand binary and 
those that don't.