Wil,
I think this is a config problem in your init script of bind...
I have seen this before in on our DNS servers and we saw
that ndc was causing the problem...
Maybe your init script has been configured the wrong way
and therefor bind doesn't reload correctly which results
that Bind want to start the deamon again but can't because
port 53 is still in use by the first daemon...
Or the daemon isn't killed properly ?
Anyway... I don't think it's a named.conf / firewall problem
but more a init / kill / startup / ndc problem.
Regards,
Brenno
> -----Original Message-----
> From: Wil Cooley [SMTP:[EMAIL PROTECTED]]
> Sent: woensdag 4 juli 2001 21:34
> To: [EMAIL PROTECTED]
> Subject: BIND & firewall rules
>
> My BIND 8 is running unpriviledged and can't rebind to udp/53 after
> reloading as it's set to. I'd like to take that out; the previous
> firewall (which I didn't set up and never saw the rules for)
> in place would complain, but not in my new one (ipchains-based).
> Is there something I should be filtering on that I'm not, or should
> I remove the query-source option in my named.conf?
>
> Wil
> --
> W. Reilly Cooley [EMAIL PROTECTED]
> Naked Ape Consulting http://nakedape.cc
> LNXS: Get 0.2.0-devel at http://sourceforge.net/projects/lnxs/
> irc.openprojects.net #lnxs
>
> When I hear a man applauded by the mob I always feel a pang of pity
> for him. All he has to do to be hissed is to live long enough.
> -- H.L. Mencken, "Minority Report"
_______________________________________________
Firewalls mailing list
[EMAIL PROTECTED]
http://lists.gnac.net/mailman/listinfo/firewalls
