> Am 01.09.2020 um 22:28 schrieb Axel Rau <[email protected]>: > > tcp queries are being answered, but udp queries receive no response. > This is independent of client location (local, remote). > > A ktrace shows 8 bytes are written on fd 89, the 8 bytes read on fd 88. > The next read gets an errno 35 (see below).
Commenting these out, seems to resolve the issue:
query-source address 91.216.35.21;
notify-source 91.216.35.21 port 53;
transfer-source 91.216.35.21 port 53;
query-source-v6 address 2a05:bec0:26:5::71;
notify-source-v6 2a05:bec0:26:5::71 port 53;
transfer-source-v6 2a05:bec0:26:5::71 port 53;
Queries to localhost shows that the response does not come from localhost:
root@ns5:/var/log # dig localhost @localhost
;; reply from unexpected source: 91.216.35.21#53, expected 127.0.0.1#53
;; reply from unexpected source: 91.216.35.21#53, expected 127.0.0.1#53
;; reply from unexpected source: 91.216.35.21#53, expected 127.0.0.1#53
; <<>> DiG 9.16.6 <<>> localhost @localhost
;; global options: +cmd
;; connection timed out; no servers could be reached
No issue with remote queries.
Questions:
What has query-source address to do with a query response?
Why does the issue not happen on another server (same config, same OS&bind
version) ?
Axel
---
PGP-Key: CDE74120 ☀ computing @ chaos claudius
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/bind-users
