On further inspection, it did not solve the problem. restarting the
networking along with the fix of the gateway solved the problem. To get
it working reliably, I had to add:
ifdown eth1 ifup eth1 into /etc/init.d/dnsmasq in the start section.
--
You received this bug notification because
On further inspection, it did not solve the problem. restarting the
networking along with the fix of the gateway solved the problem. To get
it working reliably, I had to add:
ifdown eth1 ifup eth1 into /etc/init.d/dnsmasq in the start section.
--
You received this bug notification because
It seems that my problem can be traced to putting a gateway line in my
/etc/network/interfaces file for the static internal interface. That
was causing routing problems as well. After removing the gateway line
and restarting networking and dnsmasq I now have name servers in
It seems that my problem can be traced to putting a gateway line in my
/etc/network/interfaces file for the static internal interface. That
was causing routing problems as well. After removing the gateway line
and restarting networking and dnsmasq I now have name servers in
I can verify this on my 11.10 server using two ethernet networks.
Network manager is not installed. Please see the attached configuration
files.
** Attachment added: dnsmasq.conf.old
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/875950/+attachment/2945657/+files/dnsmasq.conf.old
--
A short term hack seems to be to change the location of the resolv.conf
pointed to in the daemon script, /etc/init.d/dnsmasq.
I changed it to point to /etc/resolvconf/resolv.conf.d/original instead
of /var/run/dnsmasq/resolv.conf and that seems to have worked around the
problem.
From what I can
I can verify this on my 11.10 server using two ethernet networks.
Network manager is not installed. Please see the attached configuration
files.
** Attachment added: dnsmasq.conf.old
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/875950/+attachment/2945657/+files/dnsmasq.conf.old
--
A short term hack seems to be to change the location of the resolv.conf
pointed to in the daemon script, /etc/init.d/dnsmasq.
I changed it to point to /etc/resolvconf/resolv.conf.d/original instead
of /var/run/dnsmasq/resolv.conf and that seems to have worked around the
problem.
From what I can