On 12/13/2024 7:24 AM, Barry Scott wrote:
This version is reporting errors like these:
client @0x7fb312835168 172.17.1.173#62806 (bolt.dropbox.com): query failed
(failure) for bolt.dropbox.com/IN/A at ../../../lib/ns/query.c:7837
client @0x7fb30fa4d168 172.17.1.200#56216 (mail.gandi.net): query
Thanks to those who replied to my earlier email. I've straightened out
my routing issues but I'm still having name resolution failures.
Since then I've upgraded to OpenBSD 7.6 with BIND 9.20.2 from packages,
with no change.
I'm getting frequent lookup failures on most or all devices, but the
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 ne
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, I'm running BIND 9.18.29 on OpenBSD 7.5, installed from ports. It
does recursion and resolving for a small home network.
Multiple times a day, clients will make a DNS request that fails. The
web browser will say it can't find the address (DNS lookup failure).
Hitting retry a couple of ti
5 matches
Mail list logo
