Quantcast
Channel: EdgeRouter topics
Viewing all articles
Browse latest Browse all 20028

Vyatta Perl error with internal DNS via VPN?

$
0
0

I have used the DNS forwarding options directive to instruct DNSMasq to use certain nameservers for DNS resolution on remote LANs I'm connected to via OpenVPN. But I think this is causing the "uninitialized value" errors I'm seeing below:

 

david@RoutyMcRouterson# run show dns forwarding nameservers
Use of uninitialized value $nameserver_via in concatenation (.) or string at /opt/vyatta/bin/sudo-users/vyatta-op-dns-forwarding.pl line 176.
Use of uninitialized value $nameserver_via in concatenation (.) or string at /opt/vyatta/bin/sudo-users/vyatta-op-dns-forwarding.pl line 176.
Use of uninitialized value $nameserver_via in concatenation (.) or string at /opt/vyatta/bin/sudo-users/vyatta-op-dns-forwarding.pl line 176.
-----------------------------------------------
   Nameservers configured for DNS forwarding
-----------------------------------------------
8.8.8.8 available via 'statically configured'
8.8.4.4 available via 'statically configured'
2601:4860:4860::8888 available via 'statically configured'
2601:4860:4860::8844 available via 'statically configured'
/radin/192.168.1.1 available via ''
/rena/192.168.10.1 available via ''
/meadows.local/192.168.3.253 available via ''

-----------------------------------------------
 Nameservers NOT configured for DNS forwarding
-----------------------------------------------
127.0.0.1 available via 'system'

Ideally those three should be available via vtun0, vtun0, and vtun1, respectively. They are defined as:

 

david@RoutyMcRouterson# show service dns forwarding
 cache-size 150
 listen-on switch0
 listen-on vtun0
 listen-on vtun1
 name-server 8.8.8.8
 name-server 8.8.4.4
 name-server 2601:4860:4860::8888
 name-server 2601:4860:4860::8844
 options server=/radin/192.168.1.1
 options server=/rena/192.168.10.1
 options server=/meadows.local/192.168.3.253
 options bogus-nxdomain=198.105.244.228

 

And lastly here's dnsmasq.conf:

david@RoutyMcRouterson# more /etc/dnsmasq.conf
#
# autogenerated by vyatta-dns-forwarding.pl on Fri Jun 10 14:38:01 EDT 2016
#
log-facility=/var/log/dnsmasq.log
interface=switch0
interface=vtun0
interface=vtun1
cache-size=150
server=8.8.8.8  # statically configured
server=8.8.4.4  # statically configured
server=2601:4860:4860::8888     # statically configured
server=2601:4860:4860::8844     # statically configured
server=/radin/192.168.1.1
server=/rena/192.168.10.1
server=/meadows.local/192.168.3.253
bogus-nxdomain=198.105.244.228
no-resolv

 

Is this a bug? It would seem so. Is there a workaround? Will this cause any problems otherwise? It seems to all be working fine now...


Viewing all articles
Browse latest Browse all 20028

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>