The problem was solved when I installed the FreeBSD 4.10 release and setup
BIND 8.3.7; everything is working just fine.

Thanks a lot Matthew,

-----Original Message-----
From: Nuno César Pires 
Sent: terça-feira, 25 de Maio de 2004 10:20
To: 'Matthew Seaman'; Nuno César Pires
Subject: RE: Help to start BIND on boot

The problem is that this behaviour occurs also in a fresh installation
(4.9/8.3.6) in a different box (following the same installation checklist).

At this moment I'm considering to install and setup BIND 8.3.7 in the same
box that is running BIND 8.3.6 manually, i.e. not on boot. :-((

Thanks Matthew,
I will give you the feedback of this.

-----Original Message-----
From: Matthew Seaman [mailto:[EMAIL PROTECTED] 
Sent: segunda-feira, 24 de Maio de 2004 14:09
To: Nuno César Pires
Subject: Re: Help to start BIND on boot

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

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.



Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP:         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

CONFIDENCIALIDADE: Esta mensagem e quaisquer documentos em anexo são
confidenciais. Se não for o destinatário desta mensagem, agradecemos que
avise imediatamente o remetente e que a elimine sem a reproduzir, armazenar
ou divulgar a qualquer entidade.

CONFIDENTIALITY: This  e-mail  and  any attachments are confidential and may
be privileged. If  you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for
any purpose or store or copy the information in any medium.
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to