Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Nov 1999 12:32:54 -0500 (EST)
From:      Mikhail Teterin <mi@aldan.algebra.com>
To:        Christopher Michaels <ChrisMic@clientlogic.com>
Cc:        stable@freebsd.org
Subject:   Re: Bind in a sandbox (was: Anticipated release date for 3.4)
Message-ID:  <199911191732.MAA08589@misha.cisco.com>
In-Reply-To: <6C37EE640B78D2118D2F00A0C90FCB4401105D9E@site2s1> from Christopher Michaels at "Nov 19, 1999 12:19:58 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
Christopher Michaels once wrote:

> After reading that I was hoping someone could give me some assistance.
> I would like to run bind in a sandbox.
>
> My  problem is  that I  am on  a dynamic  IP and  when I  run it  in a
> sandbox, it complains about not being able  to bind to port 53 for the
> new address on the interface.
>
> Does anyone know  of a way around  this? (does bind need  to listen to
> port 53 on the outside interface)?

No it  does not.  In fact,  it should not,  because this  way it  can be
abused by  people outside  your lan. May  be, we can  patch our  bind to
automaticly detect dynamic interfaces and not listen on them by default?

You want to add something like:

	listen-on {
		127.0.0.1;
		10.10.0.1; // list your other interfaces here
	};

to the  options-section of your  named.conf. This, actually,  belongs to
the questions@freebsd.org mailing list.

	-mi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911191732.MAA08589>