permission denied - interfaces

[Jim Reid]

>>>>> "David" == David  <david at wmol.com> writes:

    >> On Tue, 10 Aug 1999, david wrote:
    >> 
    >> > i get the following error when named is running: > note: ip
    >> 1.2.3.4 is replacing the real IP
    >> bind(dfd=20, [1.2.3.4].53): Permission denied 
    >> deleting interface [1.2.3.4].53
    >> bind(dfd=20, [127.0.0.1].53): Permission denied
    >> deleting interface [127.0.0.1].53 

    Tim Wilde <twilde at dyndns.org> wrote in message news:Pine.BSF.4.05.9908101325460.8219-100000 at main.amnet.org...
    >> You need to be running as root or under some kind of wrapper
    >> for BIND to be able to bind to ports below 1024.

    David> I am running named as root.  Is there anything else I can
    David> check?

Try reading the man page for the bind() system call. This should tell
you what causes the system call to fail with the EACCES - "permission
denied" error code. You said you were using a FreeBSD system. As far
as I'm aware, the BSD TCP/IP stack only fails bind() system calls with
EACCES if you try to bind to a privileged port (< 1024) and you're not
the super-user. So either the FreeBSD folks have changed the semantics
of bind() or you're mistaken when you think you're running named as
root. My hunch would be that the latter is the more likely explanation.