Harhkl's latest activity

OK, glad to hear it's solved! :) Please edit your initial post to mark it as solved.

unbound is installed on the test AWS machine. systemd-resolved is installed on my production debian machine. I would suggest keeping...

@Harhkl From your netstat output the reason why "port sharing" works is because openvpn listens on 192.168.0.7 address that is different...

Thank you again for your work you put into this. After sleeping one night, I went back to my idea about port sharing I mentioned earlier...

Same dig output dig google.com ;; communications error to ::1#53: connection refused ;; communications error to ::1#53: connection...

Did not work, I tried this already this morning. dig google.com ;; communications error to ::1#53: connection refused ;; communications...

[Match] PermanentMACAddress=02:3b:35:e9:3d:2b Name=ens5 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true

Thats what I mean. The config is not being used.

If one ignores the missing DNS resolution, then yes: curl -v http://93.184.216.34 * Trying 93.184.216.34:80... * Connected to...

I acutally do systemctl restart each time and after that a full reboot, just to make sure. journalctl -b -u unbound | cat Apr 14...

Nothing changed, same outputs

The do-ip6: no is already there. here the ss output: ss -tunlp sudo: unable to resolve host ip-172-16-24-121: Temporary failure in...

The routes are all from a fresh AWS EC2 instance. No VPN there. unbound output: systemctl status unbound sudo: unable to resolve host...

Did not work unfortunately. The ssh option for you would still be possible FYI

My configuration is stored in /etc/unbound/unbound.conf not in /etc/unbound/unbound.conf.d/unbound.conf cat /etc/unbound/unbound.conf...