Como corrijo as configurações do servidor DNS IPv6 no Linux Mint 18.x?

Navegue suas respostas
1

OS: Linux Mint 18.2 Canela + Windows 10 Pro; inicialização dupla.

Acabei de usar o link deste site para verificar minha preparação para o IPv6.

Resultados no Windows 10 Pro:

ResultadosnoLinuxMint18.2Canela:

Comovocêpodever,tenhoalgumproblemacomasconfiguraçõesdeDNSnomeuLinuxMint.Mastudopareceestarativado,comoemConfiguraçõesderede-seçãoIPv6:

NãoseiaocertoondeprocuraraconfiguraçãodeDNScomfalha.OuoLinuxMint18nãoestáprontoparaoIPv6ainda?

EDIT1:

$cat/etc/resolv.confnameserver209.222.18.222nameserver209.222.18.218

MasnoGerenciadorderede,vejooDNSdoGooglecomoprincipal+odeumIPScomosecundário,queconfigureinaseçãoDHCPemIPv4domeuroteador:

Quaissãoosquemeulaptopestáusando.

$nmclidevshow|grepDNSIP4.DNS[1]:8.8.8.8IP4.DNS[2]:10.255.255.10IP6.DNS[1]:2a02:768:0:1010::3IP6.DNS[2]:2a02:768:0:1010::2

AdmitoquenãoentendooIPv6,masnãoentendoporquenoWindowsoteste,portantooIPv6estátotalmenteoperacionalenoLinuxnão.

$cat/etc/gai.conf#Configurationforgetaddrinfo(3).##Sofaronlyconfigurationforthedestinationaddresssortingisneeded.#RFC3484governsthesorting.ButtheRFCalsosaysthatsystem#administratorsshouldbeabletooverwritethedefaults.Thiscanbe#achievedhere.##Alllineshaveaninitialidentifierspecifyingtheoptionfollowedby#uptotwovalues.Informationspecifiedinthisfilereplacesthe#defaultinformation.Completeabsenceofdataofonekindcausesthe#appropriatedefaultinformationtobeused.Thesupportedcommandsinclude:##reload<yes|no>#Ifsettoyes,eachgetaddrinfo(3)callwillcheckwhetherthisfile#changedandifnecessaryreload.Thisoptionshouldnotreallybe#used.Therearepossibleruntimeproblems.Thedefaultisno.##label<mask><value>#AddanotherruletotheRFC3484labeltable.Seesection2.1in#RFC3484.Thedefaultis:##label::1/1280#label::/01#label2002::/162#label::/963#label::ffff:0:0/964#labelfec0::/105#labelfc00::/76#label2001:0::/327##ThisdefaultdiffersfromthetablesgiveninRFC3484byhandling#(nowobsolete)site-localIPv6addressesandUniqueLocalAddresses.#Thereasonforthisdifferenceisthattheseaddressesarenever#NATedwhileIPv4site-localaddressesmostprobablyare.Given#theprecedenceofIPv6overIPv4(seebelow)onmachineshavingonly#site-localIPv4andIPv6addressesalookupforaglobaladdresswould#seetheIPv6bepreferred.Theresultisalongdelaybecausethe#site-localIPv6addressescannotbeusedwhiletheIPv4addressis#(atleastfortheforeseeablefuture)NATed.WealsotreatTeredo#tunnelsspecial.##precedence<mask><value>#AddanotherruletotheRFC3484precedencetable.Seesection2.1#and10.3inRFC3484.Thedefaultis:##precedence::1/12850#precedence::/040#precedence2002::/1630#precedence::/9620#precedence::ffff:0:0/9610##ForsiteswhichpreferIPv4connectionschangethelastlineto#precedence::ffff:0:0/96100##scopev4<mask><value>#AddanotherruletotheRFC6724scopetableforIPv4addresses.#BydefaultthescopeIDsdescribedinsection3.2inRFC6724are#used.Changingthesedefaultsshouldhardlyeverbenecessary.#Thedefaultsareequivalentto:##scopev4::ffff:169.254.0.0/1122#scopev4::ffff:127.0.0.0/1042#scopev4::ffff:0.0.0.0/9614

Então,quasetudoécomentado.

Alémdisso,vocêperguntouqualclienteDHCPestavausando:

$dhclient--helpInternetSystemsConsortiumDHCPClient4.3.3...

EDIT2:

$cat/etc/dhcp/dhclient.conf#Configurationfilefor/sbin/dhclient.##Thisisasampleconfigurationfilefordhclient.Seedhclient.conf's#manpageformoreinformationaboutthesyntaxofthisfile#andamorecomprehensivelistoftheparametersunderstoodby#dhclient.##Normally,iftheDHCPserverprovidesreasonableinformationanddoes#notleaveanythingout(likethedomainname,forexample),then#fewchangesmustbemadetothisfile,ifany.#optionrfc3442-classless-static-routescode121=arrayofunsignedinteger8;sendhost-name=gethostname();requestsubnet-mask,broadcast-address,time-offset,routers,domain-name,domain-name-servers,domain-search,host-name,dhcp6.name-servers,dhcp6.domain-search,dhcp6.fqdn,dhcp6.sntp-servers,netbios-name-servers,netbios-scope,interface-mtu,rfc3442-classless-static-routes,ntp-servers;#senddhcp-client-identifier1:0:a0:24:ab:fb:9c;#senddhcp-lease-time3600;#supersededomain-name"fugue.com home.vix.com";
#prepend domain-name-servers 127.0.0.1;
#require subnet-mask, domain-name-servers;
timeout 300;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/sbin/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;

#alias {
#  interface "eth0";
#  fixed-address 192.5.5.213;
#  option subnet-mask 255.255.255.255;
#}

#lease {
#  interface "eth0";
#  fixed-address 192.33.137.200;
#  medium "link0 link1";
#  option host-name "andare.swiftmedia.com";
#  option subnet-mask 255.255.255.0;
#  option broadcast-address 192.33.137.255;
#  option routers 192.33.137.250;
#  option domain-name-servers 127.0.0.1;
#  renew 2 2000/1/12 00:00:01;
#  rebind 2 2000/1/12 00:00:01;
#  expire 2 2000/1/12 00:00:01;
#}

EDIT3:

Após copiar a linha de uma linha IPv6 acima: 

cat /etc/dhcp/dhclient.conf 

# Configuration file for /sbin/dhclient.
#
# This is a sample configuration file for dhclient. See dhclient.conf's
#   man page for more information about the syntax of this file
#   and a more comprehensive list of the parameters understood by
#   dhclient.
#
# Normally, if the DHCP server provides reasonable information and does
#   not leave anything out (like the domain name, for example), then
#   few changes must be made to this file, if any.
#

option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;

send host-name = gethostname();
request subnet-mask, broadcast-address, time-offset, routers,
    dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,
    domain-name, domain-name-servers, domain-search, host-name,
    netbios-name-servers, netbios-scope, interface-mtu,
    rfc3442-classless-static-routes, ntp-servers;

#send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
#send dhcp-lease-time 3600;
#supersede domain-name "fugue.com home.vix.com";
#prepend domain-name-servers 127.0.0.1;
#require subnet-mask, domain-name-servers;
timeout 300;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/sbin/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;

#alias {
#  interface "eth0";
#  fixed-address 192.5.5.213;
#  option subnet-mask 255.255.255.255;
#}

#lease {
#  interface "eth0";
#  fixed-address 192.33.137.200;
#  medium "link0 link1";
#  option host-name "andare.swiftmedia.com";
#  option subnet-mask 255.255.255.0;
#  option broadcast-address 192.33.137.255;
#  option routers 192.33.137.250;
#  option domain-name-servers 127.0.0.1;
#  renew 2 2000/1/12 00:00:01;
#  rebind 2 2000/1/12 00:00:01;
#  expire 2 2000/1/12 00:00:01;
#}

EDIT4:

Talvez meu aplicativo de provedor de VPN tenha causado isso, não fiz nenhuma alteração. Atualmente não estou usando a VPN, então queria testar se meu Linux é capaz de usar o IPv6. Os servidores de nomes no resolv.conf pertencem ao provedor de VPN: Private Internet Access.

Tentando descobrir por que resolv.conf não está sendo atualizado: 

$ lsattr /etc/resolv.conf

-------------e-- /etc/resolv.conf

EDIT5: 

$ sudo tcpdump -i eth0 udp port 53

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
13:28:35.416720 IP 192.168.0.11.46858 > resolver1.privateinternetaccess.com.domain: 22927+ A? imap.gmail.com. (32)
13:28:35.416730 IP 192.168.0.11.46858 > resolver1.privateinternetaccess.com.domain: 8909+ AAAA? imap.gmail.com. (32)
13:28:35.416974 IP 192.168.0.11.39732 > resolver1.privateinternetaccess.com.domain: 35471+ PTR? 222.18.222.209.in-addr.arpa. (45)
13:28:35.436305 IP 192.168.0.11.52326 > resolver1.privateinternetaccess.com.domain: 65414+ A? live.mozillamessaging.com. (43)
13:28:35.436310 IP 192.168.0.11.52326 > resolver1.privateinternetaccess.com.domain: 30886+ AAAA? live.mozillamessaging.com. (43)
13:28:35.478049 IP 192.168.0.11.46175 > resolver1.privateinternetaccess.com.domain: 5292+ A? mx.endora.cz. (30)
13:28:35.478053 IP 192.168.0.11.46175 > resolver1.privateinternetaccess.com.domain: 16624+ AAAA? mx.endora.cz. (30)
13:28:35.815497 IP 192.168.0.11.50734 > resolver1.privateinternetaccess.com.domain: 17117+ A? clients1.google.com. (37)
13:28:35.815508 IP 192.168.0.11.50734 > resolver1.privateinternetaccess.com.domain: 34551+ AAAA? clients1.google.com. (37)
13:28:35.816481 IP resolver1.privateinternetaccess.com.domain > 192.168.0.11.46175: 5292 1/0/0 A 88.86.120.212 (46)
13:28:35.818739 IP resolver1.privateinternetaccess.com.domain > 192.168.0.11.46175: 16624 0/1/0 (86)
13:28:35.959874 IP resolver1.privateinternetaccess.com.domain > 192.168.0.11.50734: 17117 2/0/0 CNAME clients.l.google.com., A 172.217.12.142 (77)
13:28:35.959899 IP resolver1.privateinternetaccess.com.domain > 192.168.0.11.50734: 34551 2/0/0 CNAME clients.l.google.com., AAAA 2607:f8b0:4006:819::200e (89)
13:28:35.972396 IP 192.168.0.11.50409 > resolver1.privateinternetaccess.com.domain: 53313+ A? ocsp2.globalsign.com. (38)
13:28:35.972406 IP 192.168.0.11.50409 > resolver1.privateinternetaccess.com.domain: 62184+ AAAA? ocsp2.globalsign.com. (38)
13:28:36.145921 IP resolver1.privateinternetaccess.com.domain > 192.168.0.11.50409: 62184 3/0/0 CNAME cdn.globalsigncdn.com., AAAA 2400:cb00:2048:1::681f:4a7c, AAAA 2400:cb00:2048:1::681f:4b7c (126)
13:28:36.153394 IP resolver1.privateinternetaccess.com.domain > 192.168.0.11.50409: 53313 3/0/0 CNAME cdn.globalsigncdn.com., A 104.31.75.124, A 104.31.74.124 (102)
13:28:36.345446 IP 192.168.0.11.39036 > resolver1.privateinternetaccess.com.domain: 49155+ A? www.googleapis.com. (36)
13:28:36.345462 IP 192.168.0.11.39036 > resolver1.privateinternetaccess.com.domain: 10791+ AAAA? www.googleapis.com. (36)
13:28:36.483314 IP resolver1.privateinternetaccess.com.domain > 192.168.0.11.39036: 49155 13/0/0 CNAME googleapis.l.google.com., A 172.217.6.234, A 172.217.10.234, A 172.217.12.170, A 172.217.12.202, A 172.217.9.234, A 172.217.10.10, A 172.217.10.42, A 172.217.10.74, A 172.217.10.138, A 172.217.3.106, A 172.217.12.138, A 172.217.6.202 (262)
13:28:36.483344 IP resolver1.privateinternetaccess.com.domain > 192.168.0.11.39036: 10791 2/0/0 CNAME googleapis.l.google.com., AAAA 2607:f8b0:4006:812::200a (98)
^C

EDIT6: 

sudo dhclient -r
sudo dhclient -v eth0


Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/d8:50:e6:05:e1:db
Sending on   LPF/eth0/d8:50:e6:05:e1:db
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x3ede007c)
DHCPREQUEST of 192.168.0.11 on eth0 to 255.255.255.255 port 67 (xid=0x7c00de3e)
DHCPOFFER of 192.168.0.11 from 192.168.0.1
DHCPACK of 192.168.0.11 from 192.168.0.1
/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf
bound to 192.168.0.11 -- renewal in 2147483648 seconds.

EDIT7: 

$ sudo tcpdump -i eth0 -vvv -n port 68

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
14:30:18.135530 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from d8:50:e6:05:e1:db, length 300, xid 0x7a30842b, Flags [none] (0x0000)
      Client-Ethernet-Address d8:50:e6:05:e1:db
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Request
        Requested-IP Option 50, length 4: 192.168.0.11
        Hostname Option 12, length 10: "vb-nb-mint"
        Parameter-Request Option 55, length 18: 
          Subnet-Mask, BR, Time-Zone, Default-Gateway
          Domain-Name, Domain-Name-Server, Option 119, Hostname
          Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
          NTP, Classless-Static-Route, Classless-Static-Route-Microsoft, Static-Route
          Option 252, NTP
        END Option 255, length 0
        PAD Option 0, length 0, occurs 18
14:30:18.136280 IP (tos 0x0, ttl 64, id 15220, offset 0, flags [none], proto UDP (17), length 576)
    192.168.0.1.67 > 192.168.0.11.68: [udp sum ok] BOOTP/DHCP, Reply, length 548, xid 0x7a30842b, Flags [none] (0x0000)
      Your-IP 192.168.0.11
      Client-Ethernet-Address d8:50:e6:05:e1:db
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: ACK
        Server-ID Option 54, length 4: 192.168.0.1
        Lease-Time Option 51, length 4: 4294967295
        Subnet-Mask Option 1, length 4: 255.255.255.0
        Default-Gateway Option 3, length 4: 192.168.0.1
        Domain-Name-Server Option 6, length 8: 8.8.8.8,10.255.255.10
        END Option 255, length 0
        PAD Option 0, length 0, occurs 270
^C

+ 

$ cat /run/resolvconf/resolv.conf

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 8.8.8.8
nameserver 10.255.255.10
nameserver 127.0.1.1
    
por Vlastimil 21.11.2017 / 07:38

2 respostas

2

Em /etc/gai.conf você precisa comentar novamente a linha dando prioridade ao IPv6 sobre IPv4 como em: 

# precedence ::ffff:0:0/96  100

Você também precisa editar o /etc/dhclient/dhclient6.conf e talvez passar o parâmetro -6 para o dhclient, se não for suficiente.

Também sugeriria corrigir o link resolv.conf.

Eu também poderia jurar que o dhclient usa apenas os dois primeiros servidores DNS transmitidos via DHCP, mas posso estar errado.

EDITAR:

  1. O passo acima está correto, ou seja, sendo o nosso primeiro passo comentando a linha: 

    precedence ::ffff:0:0/96  100

    no seguinte arquivo: 

    /etc/gai.conf

  2. Execute as etapas mencionadas nos documentos da Microsoft aplicáveis para o Linux Mint 18.x, que é baseado no Ubuntu 16.04:

    Criando o seguinte arquivo: 

    /etc/dhcp/dhclient6.conf

    com conteúdo: 

    timeout 10;

    Criando o seguinte arquivo: 

    /etc/network/interfaces.d/50-cloud-init.cfg

    com conteúdo: 

    iface eth0 inet6 auto
    up sleep 5
    up dhclient -1 -6 -cf /etc/dhcp/dhclient6.conf -lf /var/lib/dhcp/dhclient6.eth0.leases -v eth0 || true

  3. E, finalmente, criar o link simbólico enquanto sobrescreve o original resolv.conf : 

    ln -sf /run/resolvconf/resolv.conf /etc/resolv.conf

  4. A reinicialização e voila IPv6 do DHCP estão funcionando.

por 21.11.2017 / 16:17
-1

Você pode dar prioridade ao IPv6 sobre IPv4, adicionando a linha precedence 2001:470::/32 100 e comentando precedence ::ffff:0:0/96 100 no arquivo /etc/gai.conf

    
por 21.11.2017 / 16:30

Tags

Como pausar o processo com vários pid's filhos (java) Como descriptografar o arquivo em tempo real sem substituição de processo?