Recent content by Harhkl

unbound is installed on the test AWS machine. systemd-resolved is installed on my production debian machine. I would suggest keeping this thread closed as of now, to not populate it more. My case is solved for now.

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 in this thread. So I went ahead an tried to make openvpn listen to my WAN IP and some DNS service on localhost. This is my netstat output now: netstat -tulpn...

Same dig output dig google.com ;; communications error to ::1#53: connection refused ;; communications error to ::1#53: connection refused ;; communications error to ::1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ; <<>> DiG 9.18.24-1-Debian <<>>...

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

[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 93.184.216.34 (93.184.216.34) port 80 (#0) > GET / HTTP/1.1 > Host: 93.184.216.34 > User-Agent: curl/7.88.1 > Accept: */* > < HTTP/1.1 404 Not Found < Content-Type...

I acutally do systemctl restart each time and after that a full reboot, just to make sure. journalctl -b -u unbound | cat Apr 14 12:14:19 ip-172-16-24-121 systemd[1]: Starting unbound.service - Unbound DNS server... Apr 14 12:14:20 ip-172-16-24-121 unbound[426]: [426:0] notice: init module 0...

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 name resolution Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port...

The routes are all from a fresh AWS EC2 instance. No VPN there. unbound output: systemctl status unbound sudo: unable to resolve host ip-172-16-24-121: Temporary failure in name resolution ● unbound.service - Unbound DNS server Loaded: loaded (/lib/systemd/system/unbound.service; enabled...

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 # Unbound configuration file for Debian. # # See the unbound.conf(5) man page. # # See /usr/share/doc/unbound/examples/unbound.conf for a commented # reference...

I thought about this: Could I make the OpenVPN server listen on my WAN IP and then the DNS resolver could listen on localhost? This way both OpenVPN and DNS resolver may "share" UDP port 53? Not sure if possible though.

Did not work. Here the requested outputs: sudo systemctl status systemd-networkd | cat sudo: unable to resolve host ip-172-16-24-121: Temporary failure in name resolution ● systemd-networkd.service - Network Configuration Loaded: loaded (/lib/systemd/system/systemd-networkd.service...