# Openvpn does not update device DNS - Leak/Privacy issue
**URL:** https://dietpi.com/forum/t/openvpn-does-not-update-device-dns-leak-privacy-issue/22425
**Category:** General Discussion
**Tags:** vpn
**Created:** [4 January 2025 20:50 UTC](https://dietpi.com/forum/t/openvpn-does-not-update-device-dns-leak-privacy-issue/22425 "2025-01-04T20:50:40Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@t.o](https://dietpi.com/forum/u/t.o)
#### Post date: [4 January 2025 20:50 UTC](https://dietpi.com/forum/t/openvpn-does-not-update-device-dns-leak-privacy-issue/22425/1 "2025-01-04T20:50:40Z")
I am running Dietpi as an openvpn client of a paid/commercial server (no access or control of the server). Openvpn does not update the device DNS settings when connecting, even with DNS being pushed from the server, creating a DNS leak if the user/admin is not aware of this.
There are some automated solutions around - mainly using openresolv. Info [1](https://kifarunix.com/configure-openvpn-clients-to-use-specific-dns-server/) [2](https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients#pushdns-nix) [3](https://ifritltd.com/2019/06/13/how-to-fix-dns-issues-when-using-openvpn/). Has anyone else worked through openvpn/DNS problems? After some discussion here, I’ll probably put in a feature request for an option to handle this.
As a side note, my system runs a network namespace (netns) that separates all my client connections/traffic from my non-vpn traffic (except for the leaky DNS). Using separate netns could also be a big improvement on security/privacy for DIetpi in the future.
---
### Author:  [@system](https://dietpi.com/forum/u/system)
#### Post date: [3 July 2025 20:50 UTC](https://dietpi.com/forum/t/openvpn-does-not-update-device-dns-leak-privacy-issue/22425/2 "2025-07-03T20:50:47Z")
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.