On Thu, 7 Nov 2024, Hans Mayer via bind-users wrote:
[...]
Maybe the server does not log its own query or my config for
dnstap is not perfect.
Dnstap can log queries between the authority and the recursive, and
between the recursive and the client; and both queries and responses. At
least fo
Hi Nick,
many thanks for your reply and your very detailed and exact explanation.
Based on your suggestion I realised that I don't get an Authoritative
Answer if I query @ the IP of eno1 interface but I get an AA flag for
@::1 and @127.0.0.1
Therefore you are right. It must query something el
On 06/11/2024 03:16, Hans Mayer via bind-users wrote:
I have 3 views:
view badcountry: based on geoip ( the name is self-explanatory )
view internal: all local area networks but not the loopback interfaces
for IPv4 and IPv6
it has only two response policy zones for drop and passthru , nothing
Hi Nick,
many thanks for your reply and pointing me a little bit more to the
solution.
I have 3 views:
view badcountry: based on geoip ( the name is self-explanatory )
view internal: all local area networks but not the loopback interfaces
for IPv4 and IPv6
it has only two response policy
Hi Hans.
Based on what you described, it sounds like DNS queries you issue to
your server (using dig) are processed by one view for loopback addresses
and a different view for eno1 addresses? If that is the case it would be
interesting to see how the (same) zone is defined in those two views?
Dear All,
I am running BIND 9.18.32-dev (Extended Support Version)
running on Linux x86_64 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian
6.1.106-3 (2024-08-26)
This server has several interfaces based on docker but in general a
physical interface "eno1" and a loopback interface "lo".
Both in
6 matches
Mail list logo
