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
2 matches
Mail list logo