Openvpn windows clients use providers DNS. DNS leak.

[deleted]

I have this lines in openvpn config:
push "redirect-gateway def1 bypass-dhcp"
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4" Everything works fine, except that clients are using theri own dns-servers. I checked out it on whoer.net and find out that for some reason DNS-server won't pushed to clients. Seems like clients completley ignoring push directives. Why is that happening and how to resolve that? Thank you.

TinCanTech

What OS is your client ?

[deleted]

They are windows. XP and 7.

TinCanTech

Please see:
HOWTO: Request Help !

[deleted]

Here's my config files:

Server config file: #################################################
# Sample OpenVPN 2.0 config file for #
# multi-client server. #
# #
# This file is for the server side #
# of a many-clients <-> one-server #
# OpenVPN configuration. #
# #
# OpenVPN also supports #
# single-machine <-> single-machine #
# configurations (See the Examples page #
# on the web site for more info). #
# #
# This config should work on Windows #
# or Linux/BSD systems. Remember on #
# Windows to quote pathnames and use #
# double backslashes, e.g.: #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
# #
# Comments are preceded with '#' or ';' #
#################################################

# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
proto tcp
;proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one. On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert server.crt
key server.key # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.
dh dh2048.pem

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file. If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface. Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0. Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients. Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses. You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server. Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
tls-auth ta.key 0 # This file is secret

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC # Blowfish (default)
;cipher AES-128-CBC # AES
cipher DES-EDE3-CBC # Triple-DES

# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
;user nobody
;group nogroup

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it. Use one
# or the other (but not both).
log openvpn.log
;log-append openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20 Server log file:

Fri Nov 25 20:02:36 2016 OpenVPN 2.3.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Nov 12 2015
Fri Nov 25 20:02:36 2016 library versions: OpenSSL 1.0.1t  3 May 2016, LZO 2.08
Fri Nov 25 20:02:36 2016 Diffie-Hellman initialized with 2048 bit key
Fri Nov 25 20:02:36 2016 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Fri Nov 25 20:02:36 2016 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Nov 25 20:02:36 2016 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Nov 25 20:02:36 2016 Socket Buffers: R=[87380->131072] S=[16384->131072]
Fri Nov 25 20:02:36 2016 ROUTE_GATEWAY 46.172.91.1/255.255.255.0 IFACE=eth0 HWADDR=52:54:00:4e:84:a6
Fri Nov 25 20:02:36 2016 TUN/TAP device tun0 opened
Fri Nov 25 20:02:36 2016 TUN/TAP TX queue length set to 100
Fri Nov 25 20:02:36 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Fri Nov 25 20:02:36 2016 /sbin/ip link set dev tun0 up mtu 1500
Fri Nov 25 20:02:36 2016 /sbin/ip addr add dev tun0 local 10.8.0.1 peer 10.8.0.2
Fri Nov 25 20:02:36 2016 /sbin/ip route add 10.8.0.0/24 via 10.8.0.2
Fri Nov 25 20:02:36 2016 Listening for incoming TCP connection on [undef]
Fri Nov 25 20:02:36 2016 TCPv4_SERVER link local (bound): [undef]
Fri Nov 25 20:02:36 2016 TCPv4_SERVER link remote: [undef]
Fri Nov 25 20:02:36 2016 MULTI: multi_init called, r=256 v=256
Fri Nov 25 20:02:36 2016 IFCONFIG POOL: base=10.8.0.4 size=62, ipv6=0
Fri Nov 25 20:02:36 2016 ifconfig_pool_read(), in='client,10.8.0.4', TODO: IPv6
Fri Nov 25 20:02:36 2016 succeeded -> ifconfig_pool_set()
Fri Nov 25 20:02:36 2016 IFCONFIG POOL LIST
Fri Nov 25 20:02:36 2016 client,10.8.0.4
Fri Nov 25 20:02:36 2016 MULTI: TCP INIT maxclients=1024 maxevents=1028
Fri Nov 25 20:02:36 2016 Initialization Sequence Completed
Fri Nov 25 20:03:57 2016 TCP connection established with [AF_INET]MYADDR_CLIENT:54185
Fri Nov 25 20:03:58 2016 MYADDR_CLIENT:54185 TLS: Initial packet from [AF_INET]MYADDR_CLIENT:54185, sid=8437d03f 8bdce7b7
Fri Nov 25 20:04:01 2016 MYADDR_CLIENT:54185 VERIFY OK: depth=1, C=RU, L=Moscow, O=Privat team, CN=Privat team CA, name=EasyRSA, emailAddress=irvinglizard@mail.ru
Fri Nov 25 20:04:01 2016 MYADDR_CLIENT:54185 VERIFY OK: depth=0, C=RU, L=Moscow, O=Privat team, CN=client, name=EasyRSA, emailAddress=irvinglizard@mail.ru
Fri Nov 25 20:04:01 2016 MYADDR_CLIENT:54185 Data Channel Encrypt: Cipher 'DES-EDE3-CBC' initialized with 192 bit key
Fri Nov 25 20:04:01 2016 MYADDR_CLIENT:54185 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Nov 25 20:04:01 2016 MYADDR_CLIENT:54185 Data Channel Decrypt: Cipher 'DES-EDE3-CBC' initialized with 192 bit key
Fri Nov 25 20:04:01 2016 MYADDR_CLIENT:54185 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Nov 25 20:04:01 2016 MYADDR_CLIENT:54185 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
Fri Nov 25 20:04:01 2016 MYADDR_CLIENT:54185 [client] Peer Connection Initiated with [AF_INET]MYADDR_CLIENT:54185
Fri Nov 25 20:04:01 2016 client/MYADDR_CLIENT:54185 MULTI_sva: pool returned IPv4=10.8.0.6, IPv6=(Not enabled)
Fri Nov 25 20:04:01 2016 client/MYADDR_CLIENT:54185 MULTI: Learn: 10.8.0.6 -> client/MYADDR_CLIENT:54185
Fri Nov 25 20:04:01 2016 client/MYADDR_CLIENT:54185 MULTI: primary virtual IP for client/MYADDR_CLIENT:54185: 10.8.0.6
Fri Nov 25 20:04:03 2016 client/MYADDR_CLIENT:54185 PUSH: Received control message: 'PUSH_REQUEST'
Fri Nov 25 20:04:03 2016 client/MYADDR_CLIENT:54185 send_push_reply(): safe_cap=940
Fri Nov 25 20:04:03 2016 client/MYADDR_CLIENT:54185 SENT CONTROL [client]: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5' (status=1)
Fri Nov 25 20:05:38 2016 client/MYADDR_CLIENT:54185 Connection reset, restarting [-1]
Fri Nov 25 20:05:38 2016 client/MYADDR_CLIENT:54185 SIGUSR1[soft,connection-reset] received, client-instance restarting
Fri Nov 25 21:19:09 2016 TCP connection established with [AF_INET]MYADDR_CLIENT:1084
Fri Nov 25 21:19:10 2016 MYADDR_CLIENT:1084 TLS: Initial packet from [AF_INET]MYADDR_CLIENT:1084, sid=005f3cd0 b389c3c7
Fri Nov 25 21:19:13 2016 MYADDR_CLIENT:1084 VERIFY OK: depth=1, C=RU, L=Moscow, O=Privat team, CN=Privat team CA, name=EasyRSA, emailAddress=irvinglizard@mail.ru
Fri Nov 25 21:19:13 2016 MYADDR_CLIENT:1084 VERIFY OK: depth=0, C=RU, L=Moscow, O=Privat team, CN=client, name=EasyRSA, emailAddress=irvinglizard@mail.ru
Fri Nov 25 21:19:13 2016 MYADDR_CLIENT:1084 Data Channel Encrypt: Cipher 'DES-EDE3-CBC' initialized with 192 bit key
Fri Nov 25 21:19:13 2016 MYADDR_CLIENT:1084 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Nov 25 21:19:13 2016 MYADDR_CLIENT:1084 Data Channel Decrypt: Cipher 'DES-EDE3-CBC' initialized with 192 bit key
Fri Nov 25 21:19:13 2016 MYADDR_CLIENT:1084 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Nov 25 21:19:14 2016 MYADDR_CLIENT:1084 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
Fri Nov 25 21:19:14 2016 MYADDR_CLIENT:1084 [client] Peer Connection Initiated with [AF_INET]MYADDR_CLIENT:1084
Fri Nov 25 21:19:14 2016 client/MYADDR_CLIENT:1084 MULTI_sva: pool returned IPv4=10.8.0.6, IPv6=(Not enabled)
Fri Nov 25 21:19:14 2016 client/MYADDR_CLIENT:1084 MULTI: Learn: 10.8.0.6 -> client/MYADDR_CLIENT:1084
Fri Nov 25 21:19:14 2016 client/MYADDR_CLIENT:1084 MULTI: primary virtual IP for client/MYADDR_CLIENT:1084: 10.8.0.6
Fri Nov 25 21:19:16 2016 client/MYADDR_CLIENT:1084 PUSH: Received control message: 'PUSH_REQUEST'
Fri Nov 25 21:19:16 2016 client/MYADDR_CLIENT:1084 send_push_reply(): safe_cap=940
Fri Nov 25 21:19:16 2016 client/MYADDR_CLIENT:1084 SENT CONTROL [client]: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5' (status=1)

Client config: ##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client

# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap

# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
proto tcp
;proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote MYADDR 1194
;remote my-server-2 1194

# Choose a random host from the remote
# list for load-balancing. Otherwise
# try hosts in the order specified.
;remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server. Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind

# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nogroup

# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]

# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
ca ca.crt
cert client.crt
key client.key

# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server". This is an
# important precaution to protect against
# a potential attack discussed here:
# http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server". The build-key-server
# script in the easy-rsa folder will do this.
ns-cert-type server

# If a tls-auth key is used on the server
# then every client must also have the key.
tls-auth ta.key 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
cipher DES-EDE3-CBC

# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo

# Set log file verbosity.
verb 3

# Silence repeating messages
;mute 20 Client log file:

Fri Nov 25 21:26:05 2016 OpenVPN 2.3.13 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Nov  3 2016
Fri Nov 25 21:26:05 2016 Windows version 5.1 (Windows XP) 32bit
Fri Nov 25 21:26:05 2016 library versions: OpenSSL 1.0.1u  22 Sep 2016, LZO 2.09
Fri Nov 25 21:26:05 2016 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Fri Nov 25 21:26:05 2016 Need hold release from management interface, waiting...
Fri Nov 25 21:26:06 2016 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Fri Nov 25 21:26:06 2016 MANAGEMENT: CMD 'state on'
Fri Nov 25 21:26:06 2016 MANAGEMENT: CMD 'log all on'
Fri Nov 25 21:26:06 2016 MANAGEMENT: CMD 'hold off'
Fri Nov 25 21:26:06 2016 MANAGEMENT: CMD 'hold release'
Fri Nov 25 21:26:07 2016 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Fri Nov 25 21:26:07 2016 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Nov 25 21:26:07 2016 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Nov 25 21:26:07 2016 Socket Buffers: R=[8192->8192] S=[8192->8192]
Fri Nov 25 21:26:07 2016 Attempting to establish TCP connection with [AF_INET]MYADDR:1194 [nonblock]
Fri Nov 25 21:26:07 2016 MANAGEMENT: >STATE:1480101967,TCP_CONNECT,,,
Fri Nov 25 21:26:08 2016 TCP connection established with [AF_INET]MYADDR:1194
Fri Nov 25 21:26:08 2016 TCPv4_CLIENT link local: [undef]
Fri Nov 25 21:26:08 2016 TCPv4_CLIENT link remote: [AF_INET]MYADDR:1194
Fri Nov 25 21:26:08 2016 MANAGEMENT: >STATE:1480101968,WAIT,,,
Fri Nov 25 21:26:08 2016 MANAGEMENT: >STATE:1480101968,AUTH,,,
Fri Nov 25 21:26:08 2016 TLS: Initial packet from [AF_INET]MYADDR:1194, sid=255b4f05 e0a54761
Fri Nov 25 21:26:10 2016 VERIFY OK: depth=1, C=RU, L=Moscow, O=Privat team, CN=Privat team CA, name=EasyRSA, emailAddress=irvinglizard@mail.ru
Fri Nov 25 21:26:10 2016 VERIFY OK: nsCertType=SERVER
Fri Nov 25 21:26:10 2016 VERIFY OK: depth=0, C=RU, L=Moscow, O=Privat team, CN=server, name=EasyRSA, emailAddress=irvinglizard@mail.ru
Fri Nov 25 21:26:11 2016 Data Channel Encrypt: Cipher 'DES-EDE3-CBC' initialized with 192 bit key
Fri Nov 25 21:26:11 2016 WARNING: INSECURE cipher with block size less than 128 bit (64 bit).  This allows attacks like SWEET32.  Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
Fri Nov 25 21:26:11 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Nov 25 21:26:11 2016 Data Channel Decrypt: Cipher 'DES-EDE3-CBC' initialized with 192 bit key
Fri Nov 25 21:26:11 2016 WARNING: INSECURE cipher with block size less than 128 bit (64 bit).  This allows attacks like SWEET32.  Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
Fri Nov 25 21:26:11 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Nov 25 21:26:11 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
Fri Nov 25 21:26:11 2016 [server] Peer Connection Initiated with [AF_INET]MYADDR:1194
Fri Nov 25 21:26:12 2016 MANAGEMENT: >STATE:1480101972,GET_CONFIG,,,
Fri Nov 25 21:26:13 2016 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Fri Nov 25 21:26:14 2016 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5'
Fri Nov 25 21:26:14 2016 OPTIONS IMPORT: timers and/or timeouts modified
Fri Nov 25 21:26:14 2016 OPTIONS IMPORT: --ifconfig/up options modified
Fri Nov 25 21:26:14 2016 OPTIONS IMPORT: route options modified
Fri Nov 25 21:26:14 2016 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Nov 25 21:26:14 2016 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 I=3 HWADDR=00:0c:29:78:7d:3c
Fri Nov 25 21:26:14 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Fri Nov 25 21:26:14 2016 MANAGEMENT: >STATE:1480101974,ASSIGN_IP,,10.8.0.6,
Fri Nov 25 21:26:14 2016 open_tun, tt->ipv6=0
Fri Nov 25 21:26:14 2016 TAP-WIN32 device [Подключение по локальной сети 3] opened: \\.\Global\{F4E1ED63-26BB-4523-837A-95DFF8521C6F}.tap
Fri Nov 25 21:26:14 2016 TAP-Windows Driver Version 9.9 
Fri Nov 25 21:26:14 2016 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {F4E1ED63-26BB-4523-837A-95DFF8521C6F} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Fri Nov 25 21:26:14 2016 Successful ARP Flush on interface [4] {F4E1ED63-26BB-4523-837A-95DFF8521C6F}
Fri Nov 25 21:26:19 2016 TEST ROUTES: 2/2 succeeded len=1 ret=1 a=0 u/d=up
Fri Nov 25 21:26:19 2016 C:\WINDOWS\system32\route.exe ADD MYADDR MASK 255.255.255.255 192.168.1.1
Fri Nov 25 21:26:19 2016 Route addition via IPAPI succeeded [adaptive]
Fri Nov 25 21:26:19 2016 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.8.0.5
Fri Nov 25 21:26:19 2016 Route addition via IPAPI succeeded [adaptive]
Fri Nov 25 21:26:19 2016 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.8.0.5
Fri Nov 25 21:26:19 2016 Route addition via IPAPI succeeded [adaptive]
Fri Nov 25 21:26:19 2016 MANAGEMENT: >STATE:1480101979,ADD_ROUTES,,,
Fri Nov 25 21:26:19 2016 C:\WINDOWS\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.5
Fri Nov 25 21:26:19 2016 Route addition via IPAPI succeeded [adaptive]
Fri Nov 25 21:26:19 2016 Initialization Sequence Completed
Fri Nov 25 21:26:19 2016 MANAGEMENT: >STATE:1480101979,CONNECTED,SUCCESS,10.8.0.6,MYADDR

TinCanTech

What DNS Servers are in use while the VPN is down and then up ? (ipconfig /all)

[deleted]

TinCanTech wroteWhat DNS Servers are in use while the VPN is down and then up ? (ipconfig /all)

That's before:

C:\Documents and Settings\Администратор>ipconfig /all

Настройка протокола IP для Windows

        Имя компьютера  . . . . . . . . . : alex-db3fefd5d7
        Основной DNS-суффикс  . . . . . . :
        Тип узла. . . . . . . . . . . . . : неизвестный
        IP-маршрутизация включена . . . . : нет
        WINS-прокси включен . . . . . . . : нет

Hamachi - Ethernet адаптер:

        DNS-суффикс этого подключения . . :
        Описание  . . . . . . . . . . . . : Hamachi Network Interface
        Физический адрес. . . . . . . . . : 7A-79-19-30-E4-E2
        Dhcp включен. . . . . . . . . . . : да
        Автонастройка включена  . . . . . : нет
        IP-адрес  . . . . . . . . . . . . : 25.48.228.226
        Маска подсети . . . . . . . . . . : 255.0.0.0
        Основной шлюз . . . . . . . . . . :
        DHCP-сервер . . . . . . . . . . . : 25.0.0.1
        Аренда получена . . . . . . . . . : 26 ноября 2016 г. 11:52:38
        Аренда истекает . . . . . . . . . : 26 ноября 2016 г. 11:56:53

Подключение по локальной сети - Ethernet адаптер:

        DNS-суффикс этого подключения . . :
        Описание  . . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

        Физический адрес. . . . . . . . . : 00-0C-29-78-7D-3C
        Dhcp включен. . . . . . . . . . . : да
        Автонастройка включена  . . . . . : да
        IP-адрес  . . . . . . . . . . . . : 192.168.1.108
        Маска подсети . . . . . . . . . . : 255.255.255.0
        Основной шлюз . . . . . . . . . . : 192.168.1.1
        DHCP-сервер . . . . . . . . . . . : 192.168.1.1
        DNS-серверы . . . . . . . . . . . : 192.168.1.1
        Аренда получена . . . . . . . . . : 26 ноября 2016 г. 11:52:39
        Аренда истекает . . . . . . . . . : 26 ноября 2016 г. 13:52:39

Подключение по локальной сети 3 - Ethernet адаптер:

        Состояние сети  . . . . . . . . . : сеть отключена
        Описание  . . . . . . . . . . . . : TAP-Windows Adapter V9
        Физический адрес. . . . . . . . . : 00-FF-F4-E1-ED-63

And this is after:

Настройка протокола IP для Windows

        Имя компьютера  . . . . . . . . . : alex-db3fefd5d7
        Основной DNS-суффикс  . . . . . . :
        Тип узла. . . . . . . . . . . . . : неизвестный
        IP-маршрутизация включена . . . . : нет
        WINS-прокси включен . . . . . . . : нет

Hamachi - Ethernet адаптер:

        DNS-суффикс этого подключения . . :
        Описание  . . . . . . . . . . . . : Hamachi Network Interface
        Физический адрес. . . . . . . . . : 7A-79-19-30-E4-E2
        Dhcp включен. . . . . . . . . . . : да
        Автонастройка включена  . . . . . : нет
        IP-адрес  . . . . . . . . . . . . : 25.48.228.226
        Маска подсети . . . . . . . . . . : 255.0.0.0
        Основной шлюз . . . . . . . . . . :
        DHCP-сервер . . . . . . . . . . . : 25.0.0.1
        Аренда получена . . . . . . . . . : 26 ноября 2016 г. 11:54:45
        Аренда истекает . . . . . . . . . : 26 ноября 2017 г. 11:54:45

Подключение по локальной сети - Ethernet адаптер:

        DNS-суффикс этого подключения . . :
        Описание  . . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

        Физический адрес. . . . . . . . . : 00-0C-29-78-7D-3C
        Dhcp включен. . . . . . . . . . . : да
        Автонастройка включена  . . . . . : да
        IP-адрес  . . . . . . . . . . . . : 192.168.1.108
        Маска подсети . . . . . . . . . . : 255.255.255.0
        Основной шлюз . . . . . . . . . . : 192.168.1.1
        DHCP-сервер . . . . . . . . . . . : 192.168.1.1
        DNS-серверы . . . . . . . . . . . : 192.168.1.1
        Аренда получена . . . . . . . . . : 26 ноября 2016 г. 11:52:39
        Аренда истекает . . . . . . . . . : 26 ноября 2016 г. 13:52:39

Подключение по локальной сети 3 - Ethernet адаптер:

        DNS-суффикс этого подключения . . :
        Описание  . . . . . . . . . . . . : TAP-Windows Adapter V9
        Физический адрес. . . . . . . . . : 00-FF-F4-E1-ED-63
        Dhcp включен. . . . . . . . . . . : да
        Автонастройка включена  . . . . . : да
        IP-адрес  . . . . . . . . . . . . : 10.8.0.6
        Маска подсети . . . . . . . . . . : 255.255.255.252
        Основной шлюз . . . . . . . . . . : 10.8.0.5
        DHCP-сервер . . . . . . . . . . . : 10.8.0.5
        DNS-серверы . . . . . . . . . . . : 8.8.8.8
                                            8.8.4.4
        Аренда получена . . . . . . . . . : 26 ноября 2016 г. 11:55:09
        Аренда истекает . . . . . . . . . : 26 ноября 2017 г. 11:55:09

[deleted]

I have unbound installed on my server machine. Maybe I can push it as primary DNS server? How can I do that?

TinCanTech

With Windows XP you have to use non-local DNS servers prior to starting openvpn or manually remove local DNS after connecting.

With Windows 7 you can use --block-outside-dns

[deleted]

TinCanTech wroteWith Windows XP you have to use non-local DNS servers prior to starting openvpn or manually remove local DNS after connecting.

With Windows 7 you can use --block-outside-dns

I dont quite understand. There are google dns in showing in ipconfig but somehow they doesnt work. Now I tried add "block-outside-dns" to my client config and whoer shows no dns at all. Thats strange.

UPD:
Windows 7 with "block-outside-dns" show some Netherlands dns or no showing dns at all
Windows XP with "block-outside-dns" show my provider DNS from time to time. Is this a bug?