[fastdreg] broken in 0.5.3 due to gluon-wan-dnsmasq
gluon-wan-dnsmasq (introduced in gluon 2014.3) runs a secondary dns on on 127.0.0.1:54 and forwards the requests to the DHCP-assigned DNS:
gluon-mesh-vpn-fastd now uses the new package gluon-wan-dnsmasq, which provides a secondary DNS server on port 54 that is only reachable from localhost and uses the DNS servers on the WAN interface for everything. This allowed us to remove some ugly hacks which were making the DNS servers used depend on the domain being resolved.
gluon-mesh-vpn-fastd uses
*nat
-I OUTPUT -m owner --gid-owner gluon-fastd -o lo -d 127.0.0.1 -p udp --dport 53 -j DNAT --to-destination :54
COMMIT
so fastd can connect to the vpnservers. Usual dns-resolution does not work any more, also for the vpnservers.