Yes for the IP.
No for the port.
The port displayed in the journals is the source port initiated from the client.
And should connect to destination port 5335 where unbound should be listening.
unbound will reply to the same source port that was initiated by the client.
But if configured unbound according to the official guide, unbound shouldn't be listening or replying to any IP's besides the ones on the loopback interface named lo:
pi@ph5b:~ $ less /etc/unbound/unbound.conf.d/pi-hole.conf
[..]
interface: 127.0.0.1
port: 5335
pi@ph5b:~ $ sudo ss -nltup sport 5335
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
udp UNCONN 0 0 127.0.0.1:5335 0.0.0.0:* users:(("unbound",pid=19820,fd=3))
tcp LISTEN 0 256 127.0.0.1:5335 0.0.0.0:* users:(("unbound",pid=19820,fd=4))
pi@ph5b:~ $ ip -br link show lo
lo UNKNOWN 00:00:00:00:00:00 <LOOPBACK,UP,LOWER_UP>
pi@ph5b:~ $ ip -br address show lo
lo UNKNOWN 127.0.0.1/8 ::1/128
What does below output?
sudo rgrep -v '^ *#\|^ *$' /etc/unbound/unbound.conf*