Hi,
> On 13. 3. 2023, at 10:37, Michael Richardson wrote:
>
> Signed PGP part
>
> m...@at.encryp.ch wrote:
>> Regarding the usage of [::] - due to usage of firewall I am able to
>> block connections to the 53/udp and 53/tcp which are not coming to
>> specific IP addresses or ranges, I do not ne
Hi Serg.
Can you post the output of "named -V" please?
You're looking for "--disable-linux-caps", which you don't want.
I'm not sure how (if) BIND interacts with AnyIP, but it should pick up new
interfaces as they are added, *if* it is built with the necessary
capabilities enabled. 'named' starts
m...@at.encryp.ch wrote:
> Regarding the usage of [::] - due to usage of firewall I am able to
> block connections to the 53/udp and 53/tcp which are not coming to
> specific IP addresses or ranges, I do not need such filtering
> functionality within bind itself.
Bind doesn't list
The problem is I have lots of IPv6 addresses where I need to listen DNS
requests (IPv6 prefix of /64) and I could not just explicitly add each to the
interface, thus I use AnyIP feature to be able to use entire prefix by locally
by such software like nginx, curl, etc.
Regarding the usage of [::
Serg via bind-users wrote:
> As an alternative approach I have tried to run with a configuration
> "listen-on-v6 { any; }", but it does behave in a way I need - it binds
> separate socket for each discovered IP address rather wildcard address
> of [::].
Bind needs to bind a new s
Mike Lieberman wrote:
> The newer router blocks my local BIND servers (ONLY not clients using
> downstream servers) from receiving anything from the Internet. OUR BIND
> servers still have the local networks, but nothing else.
Your explanation is rather obtuse, but I think you mean t
6 matches
Mail list logo
