Rick van Hattem

1. The k8s dns server needs to be first, otherwise it doesn’t seem to work 2. I mean modifying the unbound configuration to use the k8s dns server for the...

I think it should look something like this: ``` stub-zone: name: "svc.cluster.local" stub-addr: 10.245.0.10 ```

Having the k8s dns first at least makes it work. But I'm not sure if it only resolves k8s addresses that way or if it resolves all hostnames through the...

As for knowing the stub addres... I'm not sure unfortunately. I'm not that well versed with k8s dns yet. I think it's supposed to be passed through the `--cluster-dns=...` parameter...

@qdm12 for the time being, would it be possible to put the custom dns server after the k8s dns server in /etc/resolv.conf? That way it at least works for both...

Oops... tested from the wrong server. Guess it's still building. I'll retry again in a few minutes

For some reason I'm still having issues... it's definitely a routing thing but manually trying to fix it does very little. The default routes when the VPN is connected: ```...

I found the solution! I forgot to add the device when adding the route. If I manually add the route it works now: ``` ip route add 10.192.0.0/10 via 10.244.1.32...

1. Both are needed, otherwise it can't resolve local addresses anymore. 2. Yes, it's the default route but I think it's due to overlapping ip ranges because the vpn takes...

I'm not seeing any difference unfortunately. The routing table looks identical, am I using it incorrectly? ``` ========================================= ================ Gluetun ================ ========================================= ==== A mix of OpenVPN, DNS over TLS,...