On 29/10/12 21:50, Glenn Coombs wrote:
> The nm-dns-dnsmasq.conf file only shows information relating to the 1st
> server - it seems to have totally ignored the 2nd server:
>
> $ cat /var/run/nm-dns-dnsmasq.conf
> server=/kl.imgtec.org/192.168.15.221
> server=/79.168.192.in-addr.arpa/192.168.15.221
> server=/200.9.192.in-addr.arpa/192.168.15.221
> server=/5.168.192.in-addr.arpa/192.168.15.221
> server=/6.168.192.in-addr.arpa/192.168.15.221
> server=/7.168.192.in-addr.arpa/192.168.15.221
> server=/14.168.192.in-addr.arpa/192.168.15.221
> server=/15.168.192.in-addr.arpa/192.168.15.221
>
This would seem to indicate a network-manager problem, rather than one
with dnsmasq.
On 29/10/12 21:50, Glenn Coombs wrote: nm-dns- dnsmasq. conf /kl.imgtec. org/192. 168.15. 221 /79.168. 192.in- addr.arpa/ 192.168. 15.221 /200.9. 192.in- addr.arpa/ 192.168. 15.221 /5.168. 192.in- addr.arpa/ 192.168. 15.221 /6.168. 192.in- addr.arpa/ 192.168. 15.221 /7.168. 192.in- addr.arpa/ 192.168. 15.221 /14.168. 192.in- addr.arpa/ 192.168. 15.221 /15.168. 192.in- addr.arpa/ 192.168. 15.221
> The nm-dns-dnsmasq.conf file only shows information relating to the 1st
> server - it seems to have totally ignored the 2nd server:
>
> $ cat /var/run/
> server=
> server=
> server=
> server=
> server=
> server=
> server=
> server=
>
This would seem to indicate a network-manager problem, rather than one
with dnsmasq.
Simon.