Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    openvpn 86125 RESOLVE: Cannot resolve host address:

    Scheduled Pinned Locked Moved OpenVPN
    2 Posts 2 Posters 2.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      Mufflon
      last edited by Mufflon

      Hi,
      up to this morning everything was fine with my current config but suddenly two of my VPN Clients went down. I am using expressvpn and the whole LAN traffic is routed through the tunnel. Looking at the system logs under openvpn I got the following message:

      openvpn 86125  RESOLVE: Cannot resolve host address: XXX:YYY (hostname nor servname provided, or not known)

      Note that XXX is an actual host address and YYY is the related port. Currently using pfsense ver 2.4.4
      As the current config worked fine, I never changed anything... the problem appeared without any changes.

      What I did up to now without any effect:

      • Reboot Firewall

      • Checking whether dns resolver is running (it is!)

      • Using different DNS under (System --> General Setup) like Google's 8.8.8.8 etc

      • Under Dns Resolver: Testing all "outgoing interfaces"... from the default ("all") to all possible gateways

      • Disabling "Enable DNSSEC Support"

      • Contacting ExpressVPN and asked whether they did any changes ("no"!). Other Locations work fine (setting up another client with another location)

      • Using the ExpressVPN Client app to validate the supports statement that their server are running (--> app works fine)

      • Using my ISP's default DNS

      • Using DNS lookup: Very strange behaviour: works but it seems that it uses the DNS which are set up under System --> General (and not the VPN's)

      • Disabling pfblocker_NG

      • Checking under "rounting" the default gateway (WAN)

      Here are some thoughts: I would not suggest that the problem is somewhere in the firewall rules or NAT since it worked fine up to this day. Furthermore, another location works perfect (with the same settings). I have no ipv6 stuff configured. I would also not suggest that it is a problem relating to expressvpn as they did not change any remote host settings... their app works fine

      Some additional Information:
      I have two different VPN Clients running (split tunneling) to route some traffic through tunnel A or B.
      VPN Gateway A (Client is currently running) is used as "outgoing interface" in the DNS resolver settings.... As some of you may suggest not to do so... I already changed it to "any" or any other combination (see above) with no effect. Accordingly, all websites which are setup under the firewall rules to be routed through Client B (with the described issue) are not reachable.
      here is the log from the dns resolver

      Feb 13 13:03:54 	unbound 	4676:0 	info: server stats for thread 0: requestlist max 26 avg 2.11475 exceeded 0 jostled 0
Feb 13 13:03:54 	unbound 	4676:0 	info: average recursion processing time 0.230421 sec
Feb 13 13:03:54 	unbound 	4676:0 	info: histogram of recursion processing times
Feb 13 13:03:54 	unbound 	4676:0 	info: [25%]=0.0371791 median[50%]=0.0824485 [75%]=0.185685
Feb 13 13:03:54 	unbound 	4676:0 	info: lower(secs) upper(secs) recursions
Feb 13 13:03:54 	unbound 	4676:0 	info: 0.000000 0.000001 3
Feb 13 13:03:54 	unbound 	4676:0 	info: 0.008192 0.016384 4
Feb 13 13:03:54 	unbound 	4676:0 	info: 0.016384 0.032768 20
Feb 13 13:03:54 	unbound 	4676:0 	info: 0.032768 0.065536 26
Feb 13 13:03:54 	unbound 	4676:0 	info: 0.065536 0.131072 31
Feb 13 13:03:54 	unbound 	4676:0 	info: 0.131072 0.262144 18
Feb 13 13:03:54 	unbound 	4676:0 	info: 0.262144 0.524288 9
Feb 13 13:03:54 	unbound 	4676:0 	info: 0.524288 1.000000 4
Feb 13 13:03:54 	unbound 	4676:0 	info: 1.000000 2.000000 5
Feb 13 13:03:54 	unbound 	4676:0 	info: 2.000000 4.000000 1
Feb 13 13:03:54 	unbound 	4676:0 	info: 4.000000 8.000000 1
Feb 13 13:03:54 	unbound 	4676:0 	info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Feb 13 13:03:54 	unbound 	4676:0 	info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0
Feb 13 13:03:54 	unbound 	4676:0 	info: server stats for thread 2: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Feb 13 13:03:54 	unbound 	4676:0 	info: server stats for thread 2: requestlist max 0 avg 0 exceeded 0 jostled 0
Feb 13 13:03:54 	unbound 	4676:0 	info: server stats for thread 3: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Feb 13 13:03:54 	unbound 	4676:0 	info: server stats for thread 3: requestlist max 0 avg 0 exceeded 0 jostled 0
Feb 13 13:03:57 	unbound 	7707:0 	notice: init module 0: validator
Feb 13 13:03:57 	unbound 	7707:0 	notice: init module 1: iterator
Feb 13 13:03:57 	unbound 	7707:0 	info: start of service (unbound 1.8.1).
Feb 13 13:04:00 	unbound 	7707:0 	info: generate keytag query _ta-4f66. NULL IN
Feb 13 13:09:09 	unbound 	7707:0 	info: service stopped (unbound 1.8.1).
Feb 13 13:09:09 	unbound 	7707:0 	info: server stats for thread 0: 62 queries, 3 answers from cache, 59 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Feb 13 13:09:09 	unbound 	7707:0 	info: server stats for thread 0: requestlist max 23 avg 0.610169 exceeded 0 jostled 0
Feb 13 13:09:09 	unbound 	7707:0 	info: average recursion processing time 0.131187 sec
Feb 13 13:09:09 	unbound 	7707:0 	info: histogram of recursion processing times
Feb 13 13:09:09 	unbound 	7707:0 	info: [25%]=0.0731286 median[50%]=0.0967056 [75%]=0.120283
Feb 13 13:09:09 	unbound 	7707:0 	info: lower(secs) upper(secs) recursions
Feb 13 13:09:09 	unbound 	7707:0 	info: 0.008192 0.016384 2
Feb 13 13:09:09 	unbound 	7707:0 	info: 0.016384 0.032768 6
Feb 13 13:09:09 	unbound 	7707:0 	info: 0.032768 0.065536 2
Feb 13 13:09:09 	unbound 	7707:0 	info: 0.065536 0.131072 41
Feb 13 13:09:09 	unbound 	7707:0 	info: 0.131072 0.262144 2
Feb 13 13:09:09 	unbound 	7707:0 	info: 0.262144 0.524288 5
Feb 13 13:09:09 	unbound 	7707:0 	info: 0.524288 1.000000 1
Feb 13 13:09:09 	unbound 	7707:0 	info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Feb 13 13:09:09 	unbound 	7707:0 	info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0
Feb 13 13:09:09 	unbound 	7707:0 	info: server stats for thread 2: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Feb 13 13:09:09 	unbound 	7707:0 	info: server stats for thread 2: requestlist max 0 avg 0 exceeded 0 jostled 0
Feb 13 13:09:09 	unbound 	7707:0 	info: server stats for thread 3: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Feb 13 13:09:09 	unbound 	7707:0 	info: server stats for thread 3: requestlist max 0 avg 0 exceeded 0 jostled 0
Feb 13 13:09:12 	unbound 	94756:0 	notice: init module 0: validator
Feb 13 13:09:12 	unbound 	94756:0 	notice: init module 1: iterator
Feb 13 13:09:12 	unbound 	94756:0 	info: start of service (unbound 1.8.1).
Feb 13 13:09:28 	unbound 	94756:0 	info: generate keytag query _ta-4f66. NULL IN

      If you need any further details, please let me know!
      thank you

      1 Reply Last reply Reply Quote 0
      • RicoR
        Rico LAYER 8 Rebel Alliance
        last edited by

        In Diagnostics -> DNS Lookup you can resolve this express vpn host or not?

        -Rico

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.