When setting up the DNS Forwarding service, I was not allowed to put an IPv6 address for the name-server.
I had to work around the problem by dropping back to an IPv4 address for the name-server:
dns {
forwarding {
cache-size 1000
domain localdomain {
server 127.0.0.1
}
listen-on lo
listen-on eth1.5
listen-on eth1.2
listen-on eth0
name-server 8.8.8.8
name-server 8.8.4.4
}}
DNS forwarding is done via dnsmasq.
The following configuration snipped
dns {
forwarding {
listen-on eth0
name-server 9.9.9.9
name-server 8.8.8.8
}
}will produce:
cpo@CR1# cat /etc/dnsmasq.conf # # autogenerated by vyatta-dns-forwarding.pl on Thu Dec 28 00:05:31 CET 2017 # log-facility=/var/log/dnsmasq.log no-poll edns-packet-max=4096 interface=eth0 cache-size=150 server=9.9.9.9 # statically configured server=8.8.8.8 # statically configured resolv-file=/etc/resolv.conf
Implemented in https://github.com/vyos/vyatta-cfg-system/commit/c5e11462769bea9769335944f0f8a8f5411d027e
set service dns forwarding cache-size '150' set service dns forwarding listen-on 'eth0' set service dns forwarding name-server '8.8.8.8' set service dns forwarding name-server '9.9.9.9' set service dns forwarding name-server '2001:4860:4860::8888' set service dns forwarding name-server '2001:4860:4860::8844'
Now generates:
# # autogenerated by vyatta-dns-forwarding.pl on Thu Dec 28 00:38:56 CET 2017 # log-facility=/var/log/dnsmasq.log no-poll edns-packet-max=4096 interface=eth0 cache-size=150 server=8.8.8.8 # statically configured server=9.9.9.9 # statically configured server=2001:4860:4860::8888 # statically configured server=2001:4860:4860::8844 # statically configured resolv-file=/etc/resolv.conf
@dsummers can you please recheck latest ISO? I don't have IPv6 connectivity yet.
Sorry, I just now came across this fixed issue by random chance.
I'll check it out here in the next day or so and report back.
Thanks!
I tested with vyos.999.201802100337 and the original problem is solved.....However....
I could put IPv6 IP addresses in to the
service dns forwarding nameserver
option.
However, I also found another similar problem:
I tried putting
service {
dns {
forwarding {
cache-size 1000
domain localdomain {
server ::1 <-- instead of 127.0.0.1
}
listen-on lo
nameserver 1234:1::1
nameserver 5678:2::2
}
}}
It took the nameserver entries but didn't take the ::1 on the "server" entry line.
Might this be considered part of the same bug or should I create another bug for this?
Thanks!
See T546 ("service dns forwarding doman localdomain server" entry doesn't allow IPv6 address). This one is resolved.