Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: named unable to bind to address?

Am Dienstag, 18. August 2015, 08:56:43 schrieben Sie:
> > is sufficient to let 'named' successfully bind to the IP address of the
> > "bge1" interface.
> Sounds like a named bug to me then.
i use the "internal" version of bind as the pkgsrc variants without any hassle 
- over their correlative rc scripts. 

If your bge1 is really "to slow" - let the depending scripts wait a bit by the 
"!sleep" command someones mention here - in that case the rc script for 
networking might be "optimizable" herein.

My minimum flags in rc.conf:

named9="yes" #(pkgsrc bind)
named="yes" #("internal" bind)


(you may prefer another chroot setup then)

In named.conf:

If you don't have a full IPv6 stack setup, disable it:

        # disable IPv6
        listen-on-v6 { none; };

And i prefer to bind named explicitely to IP(v4) addresses:

        listen-on {

To check if the bge1 is "In the way", you might try to bind just on the local 
iface for test/compare.

hth a bit,

 Niels Dettenbach
 Syndicat IT & Internet

Attachment: signature.asc
Description: This is a digitally signed message part.

Home | Main Index | Thread Index | Old Index