You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FR] distinguish Do53, DoT and DoH in the logs #969
Yorgos suggested to open a FR ticket here. I like his idea to simply log the destination port and
suggest to append that information to the current log. for example here:
while "my" use-case would be solved by logging a destination port, other users may see benefits if the destination address is logged. It may make sense to log both if an new option log-destaddr: yes is set (or split in log-destaddr and log-destport)
I have found by mistake unbound supports also DTLS on port 853, not necessary reserved for DoQ. Socket stream/datagram indication should be present, but I think indication of protocol used to receive query would be the best. You can still configure to accept DoT on port 443, at least dnssec-trigger uses that.
The option log-destaddr: yes can be used print the destination address, port and type, for the log-replies output. It is implemented in the commit to the repository.
The fix adds this type of output to the log replies: 127.0.0.1 localhost. A IN NOERROR 0.000000 1 54 on tcp 127.0.0.1 53.
Activity
andreasschulze commentedon Nov 25, 2023
while "my" use-case would be solved by logging a destination port, other users may see benefits if the destination address is logged. It may make sense to log both if an new option
log-destaddr: yesis set (or split inlog-destaddrandlog-destport)renaudallard commentedon Nov 25, 2023
It would also be useful to log the protocol (TCP/UDP).
In the end, we have 53 udp or tcp. 853 tcp for DoT and 853 udp for DoQ. 443 tcp for DoH.
pemensik commentedon Nov 29, 2023
I have found by mistake unbound supports also DTLS on port 853, not necessary reserved for DoQ. Socket stream/datagram indication should be present, but I think indication of protocol used to receive query would be the best. You can still configure to accept DoT on port 443, at least dnssec-trigger uses that.
wcawijngaards commentedon Dec 5, 2023
The option
log-destaddr: yescan be used print the destination address, port and type, for the log-replies output. It is implemented in the commit to the repository.The fix adds this type of output to the log replies:
127.0.0.1 localhost. A IN NOERROR 0.000000 1 54 on tcp 127.0.0.1 53.- Fix NLnetLabs#969: [FR] distinguish Do53, DoT and DoH in the logs.
andreasschulze commentedon Feb 21, 2024
Hello Wouter, looks like the commit didn't found a way into release 1.19.1. Was this intentional?
wcawijngaards commentedon Feb 22, 2024
The 1.19.1 release is a security release, and contains the security fixes only. The code is there waiting for a next release, in the code repository.
sunbearc22 commentedon Oct 31, 2024
Is the
log-destaddr:attribute supposed to be available in 1.19.2? I can't use it from the Unbound package provided in Ubuntu Server 24.04.1gthess commentedon Oct 31, 2024
1.19.2 was also a security release. The option made its way in the 1.19.3 release.