[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-07-08 Thread Thomas Hood
>> You need to configure things such that each nameserver listed in resolv.conf >> can resolve all names you want resolved. > This requirement feels impossible to meet; the dnsmasq spawned by libvirt > on my laptop knows only the VMs running on my laptop. It is not possible > for this dnsmasq to k

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-07-08 Thread Seth Arnold
Thanks Thomas, > You need to configure things such that each nameserver listed in resolv.conf > can resolve > all names you want resolved. This requirement feels impossible to meet; the dnsmasq spawned by libvirt on my laptop knows only the VMs running on my laptop. It is not possible for this d

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-07-08 Thread Thomas Hood
Hi Seth, Just read your bug report again. It appears that you have two nameservers, neither of which has complete DNS information. You need to configure things such that each nameserver listed in resolv.conf can resolve all names you want resolved. On a LAN, for example, there is sometimes a na

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-07-08 Thread Thomas Hood
** Description changed: First, apologies for the complicated configuration. I use the 'uvt' front-end to libvirt-managed kvm guest machines. I also have a LAN with a router that does local dynamic DNS configuration with the client-provided dhcp hostnames. I would like to resolve ho

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-26 Thread Robie Basak
If you're still having the issue, the other bug is marked as Fix Released and you don't think it's a duplicate, I think it would be fair to unmark this as a duplicate rather than have the bug appear as if it is resolved. ** This bug is no longer a duplicate of bug 1126488 libvirt instance of dn

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-03 Thread Thomas Hood
*** This bug is a duplicate of bug 1126488 *** https://bugs.launchpad.net/bugs/1126488 ** This bug has been marked a duplicate of bug 1126488 libvirt instance of dnsmasq in raring fails to forward DNS requests -- You received this bug notification because you are a member of Ubuntu Server

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-03 Thread Seth Arnold
Thomas, I'm experiencing this problem on Raring. The uvt version (in the source code) is: script_version="2013021401" I upgraded to Raring completely -- this isn't a frankenmonster :) -- after having successfully working 12.04 LTS and 12.10 configurations. (Obviously, with earlier versions of uvt,

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-03 Thread Thomas Hood
For the record, please say which version of the uvt script you are using. In the description you say: > This configuration worked for 12.04 LTS, 12.10, but does not work for Raring. In comment #6 you say: > I don't think this is a duplicate of bug #1126488 since I made the > conscious decision t

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-03 Thread Thomas Hood
** This bug is no longer a duplicate of bug 1126488 libvirt instance of dnsmasq in raring fails to forward DNS requests -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1163147 Title

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-02 Thread Seth Arnold
*** This bug is a duplicate of bug 1126488 *** https://bugs.launchpad.net/bugs/1126488 Robie, this very well might be an abuse of dnsmasq; however, the upstream author discusses a libvirt-managed dnsmasq instance as a perfectly well supported configuration in https://bugzilla.redhat.com/show_b

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-02 Thread Thomas Hood
*** This bug is a duplicate of bug 1126488 *** https://bugs.launchpad.net/bugs/1126488 I guess this is the same as bug #1126488. ** This bug has been marked a duplicate of bug 1126488 libvirt instance of dnsmasq in raring fails to forward DNS requests -- You received this bug notificatio

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-02 Thread Thomas Hood
The instructions say you should comment out "dns=dnsmasq" in order to disable "the system dnsmasq". But commenting out that line (and restarting network-manager) will only disable the NetworkManager- controlled dnsmasq instance (which listens at 127.0.1.1 in Quantal and higher, at 127.0.0.1 in Prec

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-02 Thread Thomas Hood
Where did you get the uvt program? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1163147 Title: can't resolve lan hosts (regression) To manage notifications about this bug go to:

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-02 Thread Thomas Hood
> Put a line into /etc/dhcp/dhclient.conf like so: > > prepend domain-name-servers 192.168.122.1; The following doesn't address the main issue but does seem to me to be worth mentioning. Since the introduction of resolvconf in Ubuntu 12.04 it is more advisable to configure nameserver addresse

[Bug 1163147] Re: can't resolve lan hosts (regression)

2013-04-02 Thread Robie Basak
Thank you for filing this bug and helping to make Ubuntu better. I appreciate that this behaviour has changed for you. I understand what you're trying to do/have been doing. I always saw this use of dnsmasq as a hack. Does anybody know if it is actually documented as supported behaviour upstream?