Ubuntu 16.04 Tempo limite de pesquisa de DNS com IPv6

Question

Eu tenho um servidor Ubuntu 16.04 com o dnsmasq 2.75 que estou tentando configurar para consultar o DNS usando servidores IPv6, mas estou recebendo tempos limite. Eu tenho uma caixa do Windows na mesma rede que é capaz de consultar o DNS usando o mesmo servidor IPv6 sem nenhum problema. Eu verifiquei firewall e eu posso ver o pedido de sair, mas o servidor apenas retorna um tempo limite.

/etc/dnsmasq.conf

server=2001:4860:4860::8888
server=2001:4860:4860::8844

nslookup

administrator@server:~$ nslookup google.com
;; connection timed out; no servers could be reached

administrator@server:~$ nslookup google.com 2001:4860:4860::8888
;; connection timed out; no servers could be reached

dig

administrator@server-01:~$ dig google.com

; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached

administrator@server-01:~$ dig @2001:4860:4860::8888 google.com

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @2001:4860:4860::8888 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

OBSERVAÇÃO : O servidor ubuntu tem conectividade IPv6, consigo acessar um IP IPv6 na internet.

Para mostrar que posso sair para o servidor IPv6, veja o exemplo:

Ping

administrator@server-01:~$ ping6 2001:4860:4860::8888
PING 2001:4860:4860::8888(2001:4860:4860::8888) 56 data bytes
64 bytes from 2001:4860:4860::8888: icmp_seq=1 ttl=57 time=31.4 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=2 ttl=57 time=33.5 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=3 ttl=57 time=34.7 ms
64 bytes from 2001:4860:4860::8888: icmp_seq=4 ttl=57 time=32.9 ms
^C
--- 2001:4860:4860::8888 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 31.411/33.142/34.708/1.210 ms

Solicitação HTTP

Destino: ipv6.google.com (2607: f8b0: 4000: 804 :: 200e)

administrator@server-01:~$ wget http://[2607:f8b0:4000:804::200e]/
--2017-10-24 08:26:03--  http://[2607:f8b0:4000:804::200e]/
Connecting to [2607:f8b0:4000:804::200e]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-10-24 08:26:03 ERROR 404: Not Found.