DNS_PROBE_FINISHED_NXDOMAIN com VPN

1

Antes de instalar o VirtualBox ou o VMware Workstation, minha conexão VPN (L2TP / IPSEC PSK) funciona sem problemas. Consigo alcançar todos os sites que eu quero.

Mas depois que um deles é instalado, recebo esta mensagem de erro em vários sites com o Chrome (o Edge e o Firefox também não carregam, mas sem me fornecer uma mensagem de erro detalhada), por exemplo toda a rede do StackExchange.

Meu telefone Android não tem esse problema (conectado à mesma VPN, é claro)

Eu tentei todas as coisas legais que encontrei no google.

flushing / renew / release dns (e outros comandos de linha de comando louco) - > sem sucesso
Definir DNS-Server manualmente - > sem sucesso
Mesmo depois de desinstalar - > sem sucesso
2 semanas sem VMware / VirtualBox (após a restauração completa do Windows) - > SUCESSO

Minha pergunta agora: É possível recuperar a funcionalidade sem desistir do VirtualBox ou VMware? Alguma idéia, algumas magias?

Servidor = QNAP-NAS
Cliente = Windows 10

Muito obrigado.

UPDATE # 1
O Twisty Impersonator me pede para executar o nslookup em um site inacessível. Superuser.com é sobre eles:

C:\WINDOWS\system32>nslookup -d2 superuser.com
------------
SendRequest(), len 42
    HEADER:
        opcode = QUERY, id = 1, rcode = NOERROR
        header flags:  query, want recursion
        questions = 1,  answers = 0,  authority records = 0,  additional = 0

    QUESTIONS:
        1.0.168.192.in-addr.arpa, type = PTR, class = IN

------------
------------
Got answer (91 bytes):
    HEADER:
        opcode = QUERY, id = 1, rcode = NXDOMAIN
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        1.0.168.192.in-addr.arpa, type = PTR, class = IN
    AUTHORITY RECORDS:
    ->  168.192.in-addr.arpa
        type = SOA, class = IN, dlen = 37
        ttl = 1278 (21 mins 18 secs)
        primary name server = localhost
        responsible mail addr = root
        serial  = 1
        refresh = 604800 (7 days)
        retry   = 86400 (1 day)
        expire  = 2419200 (28 days)
        default TTL = 604800 (7 days)

------------
Server:  UnKnown
Address:  192.168.0.1

------------
SendRequest(), len 31
    HEADER:
        opcode = QUERY, id = 2, rcode = NOERROR
        header flags:  query, want recursion
        questions = 1,  answers = 0,  authority records = 0,  additional = 0

    QUESTIONS:
        superuser.com, type = A, class = IN

------------
DNS request timed out.
    timeout was 2 seconds.
timeout (2 secs)
Fehler bei SendRequest.
------------
SendRequest(), len 31
    HEADER:
        opcode = QUERY, id = 3, rcode = NOERROR
        header flags:  query, want recursion
        questions = 1,  answers = 0,  authority records = 0,  additional = 0

    QUESTIONS:
        superuser.com, type = AAAA, class = IN

------------
------------
Got answer (121 bytes):
    HEADER:
        opcode = QUERY, id = 3, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        superuser.com, type = AAAA, class = IN
    AUTHORITY RECORDS:
    ->  superuser.com
        type = SOA, class = IN, dlen = 78
        ttl = 265 (4 mins 25 secs)
        primary name server = ns-cloud-d1.googledomains.com
        responsible mail addr = cloud-dns-hostmaster.google.com
        serial  = 1
        refresh = 21600 (6 hours)
        retry   = 3600 (1 hour)
        expire  = 259200 (3 days)
        default TTL = 300 (5 mins)

------------
------------
SendRequest(), len 31
    HEADER:
        opcode = QUERY, id = 4, rcode = NOERROR
        header flags:  query, want recursion
        questions = 1,  answers = 0,  authority records = 0,  additional = 0

    QUESTIONS:
        superuser.com, type = A, class = IN

------------
DNS request timed out.
    timeout was 2 seconds.
timeout (2 secs)
Fehler bei SendRequest.
------------
SendRequest(), len 31
    HEADER:
        opcode = QUERY, id = 5, rcode = NOERROR
        header flags:  query, want recursion
        questions = 1,  answers = 0,  authority records = 0,  additional = 0

    QUESTIONS:
        superuser.com, type = AAAA, class = IN

------------
------------
Got answer (121 bytes):
    HEADER:
        opcode = QUERY, id = 5, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        superuser.com, type = AAAA, class = IN
    AUTHORITY RECORDS:
    ->  superuser.com
        type = SOA, class = IN, dlen = 78
        ttl = 263 (4 mins 23 secs)
        primary name server = ns-cloud-d1.googledomains.com
        responsible mail addr = cloud-dns-hostmaster.google.com
        serial  = 1
        refresh = 21600 (6 hours)
        retry   = 3600 (1 hour)
        expire  = 259200 (3 days)
        default TTL = 300 (5 mins)

------------
*** Zeitüberschreitung bei Anforderung an UnKnown.

Atualização 2 Saída de ipconfig / all (Client)

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : PC-Name
   Primäres DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein

Ethernet-Adapter Ethernet:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Intel(R) Ethernet Connection I219-V
   Physische Adresse . . . . . . . . : 1C-39-47-98-0E-7D
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter DockingStation:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Realtek USB GbE Family Controller
   Physische Adresse . . . . . . . . : 00-E0-4C-12-34-72
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter WLAN:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 7265
   Physische Adresse . . . . . . . . : 10-02-B5-A1-01-30
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physische Adresse . . . . . . . . : 10-02-B5-A1-01-31
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter VMware Network Adapter VMnet1:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Physische Adresse . . . . . . . . : 00-50-56-C0-00-01
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::7451:972d:1387:c71b%3(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 192.168.150.1(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . :
   DHCPv6-IAID . . . . . . . . . . . : 100683862
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-21-D1-6A-BB-1C-39-47-98-0E-7D
   DNS-Server  . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS über TCP/IP . . . . . . . : Deaktiviert

Ethernet-Adapter VMware Network Adapter VMnet8:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
   Physische Adresse . . . . . . . . : 00-50-56-C0-00-08
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::e41e:4322:d30b:524c%7(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 192.168.220.1(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Lease erhalten. . . . . . . . . . : Samstag, 6. Januar 2018 08:17:58
   Lease läuft ab. . . . . . . . . . : Samstag, 6. Januar 2018 17:02:57
   Standardgateway . . . . . . . . . :
   DHCP-Server . . . . . . . . . . . : 192.168.220.254
   DHCPv6-IAID . . . . . . . . . . . : 738218070
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-21-D1-6A-BB-1C-39-47-98-0E-7D
   DNS-Server  . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS über TCP/IP . . . . . . . : Deaktiviert

PPP-Adapter MyVPN:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : MyVPN
   Physische Adresse . . . . . . . . :
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   IPv4-Adresse  . . . . . . . . . . : 10.2.0.2(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.255
   Standardgateway . . . . . . . . . : 0.0.0.0
   DNS-Server  . . . . . . . . . . . : 192.168.0.1
   NetBIOS über TCP/IP . . . . . . . : Deaktiviert

Mobiler Breitbandadapter Mobilfunk:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : HUAWEI Mobile Broadband Module
   Physische Adresse . . . . . . . . : 8C-9A-88-55-59-53
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::b91d:5c86:6ce7:c88e%15(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 10.78.75.185(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.0.0.0
   Standardgateway . . . . . . . . . : 10.78.75.186
   DNS-Server  . . . . . . . . . . . : 62.109.121.17
                                       62.109.121.18
   NetBIOS über TCP/IP . . . . . . . : Aktiviert

Tunneladapter LAN-Verbindung* 12:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   IPv6-Adresse. . . . . . . . . . . : 2001:0:9d38:78cf:28bb:225b:f5fd:fffd(Bevorzugt)
   Verbindungslokale IPv6-Adresse  . : fe80::28bb:225b:f5fd:fffd%18(Bevorzugt)
   Standardgateway . . . . . . . . . : ::
   DHCPv6-IAID . . . . . . . . . . . : 301989888
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-21-D1-6A-BB-1C-39-47-98-0E-7D
   NetBIOS über TCP/IP . . . . . . . : Deaktiviert

VMnet1 é a rede interna (para se conectar via SSH sem uma rede física)

VMnet8 é o VMware Bridge

Conectar-se aos dispositivos de rede locais via IP (192.168.0.xx) através da VPN funciona bem.

Como eu mencionei anteriormente, a outra metade da world wide web é alcançável.

    
por reinholda 05.01.2018 / 23:04

1 resposta

0

Sua conexão VPN está configurada com o servidor DNS 192.168.0.1. Conforme demonstrado pela sua tentativa de consulta do nslookup, esse servidor DNS é o primeiro a ser consultado pelo seu computador. Aparentemente, o seu computador não possui uma rota de trabalho para esse servidor DNS quando sua conexão VPN está ativa. Isso precisa ser resolvido.

Com base no seu comentário:

i give up on L2TP/IPSEC. Switched to OpenVPN. No DNS related issues. I'm able to browse the (complete) web AND use my local devices at home.

Parece que algo não estava funcionando com sua conexão VPN e que estava impedindo você de acessar esse servidor DNS.

    
por 10.01.2018 / 16:25