Remotely push DNS server to client via OpenVPN

Question

When I try to push a DNS server via the OpenVPN server-config I don't get that server to be the first DNS server on the connected client system. It ends up being specified as an alternative DNS server.

push "dhcp-option DNS 89.238.75.146" # DNS-Server 1 (local djbdns)

To overcome certain network restrictions, if they're at place, I use 443 TCP. - That means that my DNS queries are sent via TCP (if I manually reconfigure the DNS server), which doesn't scale very well from a performance perspective.

Are there any kewl solutions for that?

Marius

Solution

I've noticed that it differs based on "client". If I use network manager I get the DNS but if I use "regular" openvpn service (in Ubuntu) I don't get the DNS. I haven't look deeper into this since I usually let network manager connect my vpn.

Comments

[emgee]

Bit unclear... are you saying you run DNS on port 443 (https)? Anyway, what OS are your clients running?

[wishi]

- the OpenVPN daemon on the remote server works on 443. The DNSd runs on a Linux box. If I route the traffic through the OpenVPN tunnel the DNS traffic is tunneld through 443, too.

[emgee]

Gotcha, so the main problem you are trying to overcome is pushed DNS settings don't show up as primary, but as secondary?

[wishi]

That, and even if I configure it - TCP and DNS don't scale together.

[wishi]

sorry for accepting this answer rather late... I think something is wrong here with my account connection on StackOF and so on...

[Arno Teigseth]

I wanted to vote up Jimmy's answer, but since I can't, I'd like to give thumbs up in this post: Effectively, the NetworkManager openvpn plugin DOES update the /etc/resolv.conf with the DNS options pushed by openvpn server.

[Charney Kaye]

Agree, NetworkManager manages to get that right sigh here's hoping for clean .ovpn compatibility someday...

[Gajus]

See serverfault.com/a/590722/82338