Are you running NTP? (e.g. is your time correct on the device running bind?)
Forwarding to another recursive resolver or using hints?
I'm running Bind 9.18.29 on FreeBSD 14.1-p4 on a RPI4. No jails. (It runs
on RPI5 also)
I also have it setup to run unbound 1.21.0 for comparison. (BTW, that works
Hi Steven.
As you said, `listen-on {...;};` tells BIND which addresses to register for
incoming traffic. This can be a list, not just one address. Any query
received on (say) 10.0.0.1 will be responded to from the same address.
It is possible to choose which address to use for outgoing queries/fet
On 13/09/2024 16:14, Steven Shockley wrote:
Is there a way to tell BIND to listen (and respond) on a specific
interface? I already have listen-on { 10.0.0.1; }; (vlan101 IP) in the
config with nothing else listening.
BIND will send the response with a source address of 10.0.0.1, and it
hand
On 9/12/2024 9:20 PM, Steven Shockley wrote:
I'll try to run some tcpdumps inbound and outbound tomorrow, traffic
should be pretty light.
I did find something interesting that may or may not be related.
The machine is also the Internet gateway. One NIC has a vlan interface
for each network;
On 9/11/2024 2:11 AM, Ondřej Surý wrote:
Does this happen only with this specific domain or it happens with different
names too?
Thanks for the reply. It happens with many domains.
If you can reliably reproduce the problem, you can either bump up the debugging
(-d 9 argument to named) or c
Hi Steven,
sorry to hear that.
Does this happen only with this specific domain or it happens with different
names too?
If you can reliably reproduce the problem, you can either bump up the debugging
(-d 9 argument to named) or capture the traces.
Are there any other log entries preceding the
6 matches
Mail list logo
