Date: Mon, 24 May 2004 14:09:20 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Nuno =?iso-8859-1?Q?C=E9sar?= Pires <NCPires@isq.pt> Cc: "'freebsd-questions@freebsd.org'" <freebsd-questions@freebsd.org> Subject: Re: Help to start BIND on boot Message-ID: <20040524130920.GB88714@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <6A7539CE32D1CC42AD0B863337EEFCFB020B20F8@isq004> References: <6A7539CE32D1CC42AD0B863337EEFCFB020B20F8@isq004>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Mon, May 24, 2004 at 12:29:55PM +0100, Nuno César Pires wrote:
> My question is: what solve the problem, the new FreeBSD 5.2.1 or the BIND
> 8.3.7?
Good question. It's unlikely to be the simple replacement of one OS
version or one BIND version for another -- we would know about it if
there was a general problem with people running BIND on FreeBSD.
> How can I solve this strange behaviour in the FreeBSD 4.9/BIND 8.3.6 system?
Unfortunately, having made my best guess, I'm afraid I'm all out of
suggestions. Other than this: take a close look at the way both of
those boxes are set up, and try and isolate the differences in
configuration between the two. The answer should lie somewhere in
there -- something you did differently on one of the boxes. Isolate
that, and you're home and dry.
Which is easy to say, but not necessarily easy to do.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAsfQAiD657aJF7eIRAmQUAJ9r/8INB9lqD4EtfIL5QeHb0OeF0ACfYSig
36eiLHuBjVDIPqkU7SYST44=
=O9QJ
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040524130920.GB88714>