[Bug 1163147] Re: can't resolve lan hosts (regression)
>> 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 know the hosts on my LAN That instance of dnsmasq, call it DV, provides services to VMs. If the VMs are going to access the LAN or the Internet then DV needs to forward DNS queries for which it isn't authoritative to a nameserver on the LAN or on the Internet. > I have a standard consumer router on my network to provide DHCP > and dynamic DNS services. I do not want to require my laptop to be > on and connected to my LAN for other hosts to continue using the LAN. Agreed. Your laptop should ultimately send DNS queries to the nameserver on the router, just as any other machine on the LAN does. You want to be able to resolve VM names on your laptop as well as LAN and Internet names. In that case you will have to use DV as your laptop's nameserver and configure DV to forward DNS queries to the router and not use the nameserver that the laptop is using (which is DV itself — that would be a loop). This should be implemented cleanly using resolvconf. Here is an outline of how that should be done, blindly assuming a few things such as that the "dnsmasq" package is not installed on your machine. I blindly assume, that is, that libvirt runs an instance of dnsmasq using the binary in the dnsmasq-base package. Basically, DV should behave similarly to how the server instance of dnsmasq (from the "dnsmasq" package) behaves with respect to resolvconf. 1. DV should register with resolvconf a loopback address at which it listens. Configure it to listen at 127.0.0.1 on the laptop and modify its control script to run echo "nameserver 127.0.0.1" | resolvconf -a lo.dnsmasq on start and resolvconf -d lo.dnsmasq on stop. 2. DV should have a hook script in /etc/resolvconf/update.d/ which generates a list of forwarders for DV to use. The resolvconf hook script from the dnsmasq package can be used verbatim for this purpose; simply put the file in update.d/ and configure DV to use /var/run/dnsmasq/resolv.conf as its only forwarders-list file. If you want details I can help you, or you can follow the good example of the dnsmasq package. ** Summary changed: - can't resolve lan hosts (regression) + Can't resolve both VM names and LAN names -- 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: Please run dnsmasq in such a way that it can also be used on the host — to look up the VMs' names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
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 dnsmasq to know the hosts on my LAN -- I have a
standard consumer router on my network to provide DHCP and dynamic DNS
services. I do not want to require my laptop to be on and connected to
my LAN for other hosts to continue using the LAN.
The DNS server on my router does not know about the VMs I host on my
laptop. They are "behind" the libvirt-default NAT configuration, so they
aren't even routable addresses on the LAN. Sometimes my laptop leans the
LAN, and I still want to resolve my VM names.
I do not know how to configure my router to serve hostnames with a fake
TLD. (I haven't used a fake TLD since about 2002, I didn't know anyone
still did that..) If you really think this is a solution, I can look
into it, but this all worked flawlessly with 12.04 LTS. :(
** 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 hostnames on my machine for both VM guests and
LAN hosts. This configuration worked for 12.04 LTS, 12.10, but does not
work for Raring. I have followed the directions at
https://wiki.ubuntu.com/SecurityTeam/TestingEnvironment#Networking_with_libvirt
:
> Put a line into /etc/dhcp/dhclient.conf like so:
>
> prepend domain-name-servers 192.168.122.1;
>
> Disable the system dnsmasq to prevent it from looping with libvirt's
dnsmasq by modifying
> /etc/NetworkManager/NetworkManager.conf to comment out the following line:
>
> #dns=dnsmasq
My /etc/resolv.conf when the wireless is up:
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.122.1
nameserver 192.168.1.1
- Here's trying to look up a host on my network:
+ My router / DHCP / Dynamic DNS server is on 192.168.1.1.
+ My laptop ("hunt") is currently allocated 192.168.1.14.
+ The VMs on my laptop run in 192.168.122.0/24.
+ An instance of dnsmasq started by libvirt runs on 192.168.122.1 on my laptop.
+ My panda ("dean") is currently allocated 192.168.1.236.
+
+ Here's trying to look up dean from my laptop:
$ host dean
Host dean not found: 3(NXDOMAIN)
$ host dean 192.168.122.1
Using domain server:
Name: 192.168.122.1
Address: 192.168.122.1#53
Aliases:
Host dean not found: 3(NXDOMAIN)
$ host dean 192.168.1.1
Using domain server:
Name: 192.168.1.1
Address: 192.168.1.1#53
Aliases:
- dean has address 192.168.1.236
- $
$ host 192.168.1.236
236.1.168.192.in-addr.arpa domain name pointer dean.
$ host 192.168.1.236 192.168.122.1
Using domain server:
Name: 192.168.122.1
Address: 192.168.122.1#53
Aliases:
236.1.168.192.in-addr.arpa domain name pointer dean.
$ host 192.168.1.236 192.168.1.1
Using domain server:
Name: 192.168.1.1
Address: 192.168.1.1#53
Aliases:
236.1.168.192.in-addr.arpa domain name pointer dean.
$
I'm surprised that 192.168.122.1 knows the reverse information for dean.
I want the query for plain "dean" to succeed. (As that's how 'ssh'
works..)
If I swap the order of the lines in /etc/resolv.conf to put 192.168.1.1 first,
I get the opposite situation:
$ host dean
dean has address 192.168.1.236
$ uvt start sec-precise-amd64
Sleeping 5 seconds to give 'sec-precise-amd64' a chance to start
$ ssh sec-precise-amd64 "echo hello"
ssh: Could not resolve hostname sec-precise-amd64: No such file or directory
$ ssh sec-precise-amd64. "echo hello"
ssh: Could not resolve hostname sec-precise-amd64.: No such file or directory
$ ssh sec-precise-amd64.local "echo hello"
hello
I do not want to use the .local form for all my VMs. That is annoying and the
scripts we have written around uvt assume that the .local is not necessary.
12.04 LTS and 12.10 had this working well. I would like Raring to work that
well again.
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: dnsmasq (not installed)
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Tue Apr 2 00:04:49 2013
InstallationDate: Installed on 2012-10-18 (166 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120823.1)
MarkForUpload: True
ProcEnviron:
TERM=rxvt-unicode
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: Up
[Bug 1163147] Re: can't resolve lan hosts (regression)
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 nameserver that resolves names in a TLD such as ".private". Such a nameserver has to be so configured that it *also* resolves Internet DNS names. Likewise in your setup. P.S. Can you please edit your description to say which machine has which IP address? And provide more details about how you have configured your nameservers? -- 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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
** 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 hostnames on my machine for both VM guests and LAN hosts. This configuration worked for 12.04 LTS, 12.10, but does not work for Raring. I have followed the directions at https://wiki.ubuntu.com/SecurityTeam/TestingEnvironment#Networking_with_libvirt : > Put a line into /etc/dhcp/dhclient.conf like so: - > + > > prepend domain-name-servers 192.168.122.1; - > + > > Disable the system dnsmasq to prevent it from looping with libvirt's dnsmasq by modifying > /etc/NetworkManager/NetworkManager.conf to comment out the following line: - > + > > #dns=dnsmasq My /etc/resolv.conf when the wireless is up: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.122.1 nameserver 192.168.1.1 Here's trying to look up a host on my network: + $ host dean Host dean not found: 3(NXDOMAIN) $ host dean 192.168.122.1 Using domain server: Name: 192.168.122.1 Address: 192.168.122.1#53 - Aliases: + Aliases: Host dean not found: 3(NXDOMAIN) $ host dean 192.168.1.1 Using domain server: Name: 192.168.1.1 Address: 192.168.1.1#53 - Aliases: + Aliases: dean has address 192.168.1.236 - $ + $ $ host 192.168.1.236 236.1.168.192.in-addr.arpa domain name pointer dean. $ host 192.168.1.236 192.168.122.1 Using domain server: Name: 192.168.122.1 Address: 192.168.122.1#53 - Aliases: + Aliases: 236.1.168.192.in-addr.arpa domain name pointer dean. $ host 192.168.1.236 192.168.1.1 Using domain server: Name: 192.168.1.1 Address: 192.168.1.1#53 - Aliases: + Aliases: 236.1.168.192.in-addr.arpa domain name pointer dean. - $ - - I want $ host dean - Host dean not found: 3(NXDOMAIN) - $ host dean 192.168.122.1 - Using domain server: - Name: 192.168.122.1 - Address: 192.168.122.1#53 - Aliases: - - Host dean not found: 3(NXDOMAIN) - $ host dean 192.168.1.1 - Using domain server: - Name: 192.168.1.1 - Address: 192.168.1.1#53 - Aliases: - - dean has address 192.168.1.236 - $ - $ host 192.168.1.236 - 236.1.168.192.in-addr.arpa domain name pointer dean. - $ host 192.168.1.236 192.168.122.1 - Using domain server: - Name: 192.168.122.1 - Address: 192.168.122.1#53 - Aliases: - - 236.1.168.192.in-addr.arpa domain name pointer dean. - $ host 192.168.1.236 192.168.1.1 - Using domain server: - Name: 192.168.1.1 - Address: 192.168.1.1#53 - Aliases: - - 236.1.168.192.in-addr.arpa domain name pointer dean. - $ - + $ I'm surprised that 192.168.122.1 knows the reverse information for dean. I want the query for plain "dean" to succeed. (As that's how 'ssh' works..) If I swap the order of the lines in /etc/resolv.conf to put 192.168.1.1 first, I get the opposite situation: $ host dean dean has address 192.168.1.236 $ uvt start sec-precise-amd64 Sleeping 5 seconds to give 'sec-precise-amd64' a chance to start $ ssh sec-precise-amd64 "echo hello" ssh: Could not resolve hostname sec-precise-amd64: No such file or directory $ ssh sec-precise-amd64. "echo hello" ssh: Could not resolve hostname sec-precise-amd64.: No such file or directory $ ssh sec-precise-amd64.local "echo hello" hello - I do not want to use the .local form for all my VMs. That is annoying and the scripts we have written around uvt assume that the .local is not necessary. 12.04 LTS and 12.10 had this working well. I would like Raring to work that well again. Thanks ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Tue Apr 2 00:04:49 2013 InstallationDate: Installed on 2012-10-18 (166 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: - TERM=rxvt-unicode - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=rxvt-unicode + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to raring on 2013-03-18 (15 days ago) -- 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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.
[Bug 1163147] Re: can't resolve lan hosts (regression)
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 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: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
*** 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 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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
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, as well; the changes to uvt have been mainly to support secure boot and turn off some whizbang graphic effects in the preseed to make vnc more tolerable for the times we need to perform GUI application tests.) Thanks again, and sorry for the confusion of my last comment. -- 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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
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 to _not_ upgrade to Raring Can you be more clear about whether you are running 12.04 or Raring or some combination of the two? In the latter case, which packages have you upgraded to Raring? ** Changed in: dnsmasq (Ubuntu) Status: New => Incomplete -- 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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
** 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: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
*** 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_bug.cgi?id=833033#c11 . Thomas, I don't think this is a duplicate of bug #1126488 since I made the conscious decision to _not_ upgrade to Raring until after that bug had been fixed in the main archive. :) I didn't want to deal with dnsmasq problems... I had used the resolvconf mechanism in the past, but switched to using prepend nameservers in dhclient.conf to match the instructions on the uvt wikipage while trying to debug this. (I had used both mechanisms without problems on 12.04 LTS and 12.10.) I do not have the dnsmasq package installed. uvt is available in the ubuntu-qa-tools bazaar tree: http://bazaar.launchpad.net/~ubuntu-bugcontrol/ubuntu-qa- tools/master/view/head:/vm-tools/uvt It may not have the polish of the usual GUI tools but it does make deploying and maintaining a dozen qemu/kvm snapshot-capable Ubuntu installs extremely easy and convenient. ** Bug watch added: Red Hat Bugzilla #833033 https://bugzilla.redhat.com/show_bug.cgi?id=833033 -- 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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
*** 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 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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
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 Precise). If you have the "dnsmasq" package installed then you have another system dnsmasq instance running which listens by default on all network interfaces. Make sure that the "dnsmasq" package is not installed if you don't want this dnsmasq instance to be running. -- 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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
> 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 addresses via the network configuration tool, i.e., either ifup or NetworkManager. If you are using ifup then you add extra nameserver addresses to logical interface definitions in /etc/network/interfaces as arguments to the "dns-nameservers" option. If you are using NetworkManager (as you seem to be doing, given that you are editing NetworkManager.conf) then add nameserver addresses in Edit Connections | | Edit... | IPv4 Settings | Additional DNS servers; if necessary, remove DHCP-acquired nameserver addresses by setting Method to "Automatic (DHCP) addresses only". -- 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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1163147] Re: can't resolve lan hosts (regression)
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? -- 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: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
