br matching was added to interface-order in Debian release 1.77, thus in
wily which has resolvconf 1.77ubuntu1.
--
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/1384394
Title:
The service is called "bind9-resolvconf" but you said you ran "sudo
systemctl start bind9-resolv.conf" and "sudo systemctl stop
bind9-resolv.conf". Look carefully at the spelling.
** Changed in: bind9 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
Do you have the "dnsmasq" package installed and is the instance of the
dnsmasq program started by the "dnsmasq" package configured to listen at
127.0.1.1?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
First, it appears that NetworkManager doesn't handle the error well and
retries without sleeping. Needs fixing.
Separate issue: Why is the error occurring on your machine? Why do you
get "dnsmasq[30613]: failed to create listening socket for 127.0.1.1:
Address already in use"?
--
You received
** Package changed: resolvconf (Ubuntu) => dnsmasq (Ubuntu)
--
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/1516329
Title:
DNS BUG delay resolution of LAN DNS
To manage
*** This bug is a duplicate of bug 1042275 ***
https://bugs.launchpad.net/bugs/1042275
** This bug has been marked a duplicate of bug 1042275
Please enhance dnsmasq to talk directly to resolvconf and to register only
its actual listening address(es)
--
You received this bug notification
Best to submit this wish to the Debian bug tracking system so that
Debian will also benefit from this enhancement.
--
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/1485316
Title:
Christian, the workaround is to comment out the line dns=dnsmasq in
/etc/NetworkManager/NetworkManager.conf.
--
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/1003842
Title:
dnsmasq
To add that, or any other, option to resolv.conf permanently, add the
line
options edns0
to the file
/etc/resolvconf/resolv.conf.d/base
and then resolvconf will include it in the resolv.conf that it
generates.
** Changed in: dnsmasq (Ubuntu)
Status: New = Invalid
--
You
Hi. I don't see how resolvconf could be responsible for this problem.
Initial observation: it seems that dig gets the correct answer from
dnsmasq when it supplies the additional option udp:1280, but the glibc
resolver doesn't get the right answer from dnsmasq when it fails to
supply that option.
** Changed in: network-manager (Ubuntu)
Status: In Progress = New
--
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/1003842
Title:
dnsmasq sometimes fails to resolve private
Dnsmasq treats all nameservers as equivalent (except insofar as it is
instructed to use particular nameservers to resolve names in particular
domains).
The C library resolver, on the other hand, tries one nameserver at a
time in the order that their addresses are listed in resolv.conf.
If you
*** This bug is a duplicate of bug 1314697 ***
https://bugs.launchpad.net/bugs/1314697
** This bug has been marked a duplicate of bug 1314697
DNS resolution no longer works; dnsmasq uses 100% CPU
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Confirmed that the bug affects 2.72-2.
$ cat /etc/dnsmasq.conf | tail -n 2
# Include all files in a directory which end in .conf
#conf-dir=/etc/dnsmasq.d/*.conf$ od -t c /etc/dnsmasq.conf | tail -n 2
0062620 / * . c o n f
0062627
$
** Changed in: dnsmasq (Ubuntu)
Status:
Just checked 2.72-1 and it doesn't seem to have this problem.
$ cat /etc/dnsmasq.conf | tail -n 2
#conf-file=/etc/dnsmasq.more.conf
#conf-dir=/etc/dnsmasq.d
$ od -t c /etc/dnsmasq.conf | tail -n 2
0062320 / e t c / d n s m a s q . d \n
0062337
--
You received this
First, as suggested by the author of dnsmasq, the `local-service`
should be in the default configuration. However, Ubuntu 14.10
doesn't have that
What the man page exactly says is that local-service only has effect
i[f] there are no --interface --except-interface, --listen-address or
Ubuntu 13.10 (Saucy) included dnsmasq 2.66 or so. In dnsmasq 2.69 an
important change was made which may be the cause of your problem. This
change affects Ubuntu 14.10 and later, but not Ubuntu 14.04LTS (Trusty)
which shipped with dnsmasq 2.68-1. The change is mentioned in the
changelog (quoted
** Summary changed:
- squid3 gets killed at startup with dnsmasq and no networkmanager
+ squid3 gets killed at startup with dnsmasq
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
Is dnsmasq getting its DNS server information from resolvconf,
which in turn gets it from /etc/network/interfaces? Or, does
dnsmasq take what it likes from /etc/network/interfaces directly,
discarding the rest?
1. If you have only the dnsmasq-base and network-manager packages installed
then
I gather that you want to use the fact that the resolver happens to try
one address after another, in the order that they are listed in
resolv.conf, as a way of giving precedence of one domain name system
(the service provided over the br* interfaces) over another domain name
system (the one
** Description changed:
This is a wishlist item.
- I'd like to use DNSSEC for dnsmasq out of the box. Currently support for
- DNSSEC appears to be disabled at compile time: if I add dnssec options
- to the dnsmasq.conf, it doesn't accept the configuration. I'm using
- Ubuntu Trusty.
+ I'd
Trusty has dnsmasq 2.68-1. Looking at the buildlog I don't see
HAVE_DNSSEC being defined on the compiler command line.
gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -W -DHAVE_DBUS
-DHAVE_CONNTRACK
*** This bug is a duplicate of bug 1314697 ***
https://bugs.launchpad.net/bugs/1314697
** This bug is no longer a duplicate of bug 1313393
dnsmasq lockup at 100% cpu
** This bug has been marked a duplicate of bug 1314697
DNS resolution no longer works; dnsmasq uses 100% CPU
--
You
*** This bug is a duplicate of bug 1314697 ***
https://bugs.launchpad.net/bugs/1314697
** This bug has been marked a duplicate of bug 1314697
DNS resolution no longer works; dnsmasq uses 100% CPU
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Fixed in Debian dnsmasq 2.71-1
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed = Fix Released
--
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/1315741
Title:
The dnsmasq
Fixed in Utopic
--
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/1315741
Title:
The dnsmasq initscript fails to disable itself when the dnsmasq
package is removed
To manage
*** This bug is a duplicate of bug 1314697 ***
https://bugs.launchpad.net/bugs/1314697
** This bug has been marked a duplicate of bug 1314697
DNS resolution no longer works; dnsmasq uses 100% CPU
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Summary changed:
- Upon upgrade, DNS resolution no longer works
+ Upon upgrade, DNS resolution no longer works; dnsmasq uses 100% CPU
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
*** This bug is a duplicate of bug 1314697 ***
https://bugs.launchpad.net/bugs/1314697
** This bug has been marked a duplicate of bug 1314697
Upon upgrade, DNS resolution no longer works; dnsmasq uses 100% CPU
--
You received this bug notification because you are a member of Ubuntu
The Debian dnsmasq maintainer reports that he has uploaded a new version
of the package for Debian. This will need to be pushed over to Ubuntu
when it's available.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
the script fails to look at the return value
I was wrong; the script does look at the return value.
** Package changed: resolvconf (Ubuntu) = dnsmasq (Ubuntu)
** Also affects: dnsmasq
Importance: Undecided
Status: New
** No longer affects: dnsmasq
** Also affects: dnsmasq (Debian)
** Bug watch added: Debian Bug tracker #746941
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746941
** Changed in: dnsmasq (Debian)
Importance: Undecided = Unknown
** Changed in: dnsmasq (Debian)
Status: New = Unknown
** Changed in: dnsmasq (Debian)
Remote watch: None = Debian
Assuming you are using NetworkManager, a better way to work around the
problem than editing resolv.conf by hand is to edit
/etc/NetworkManager/NetworkManager.conf and comment out the line
`dns=dnsmasq`, save, and then `restart network-manager`. This will cause
NetworkManager not to use a slave
Make sure that the resolvconf package is installed and that
/etc/resolv.conf is a symbolic link to ../run/resolvconf/resolv.conf and
that the proprietary software on your Linux Mint system doesn't futz
with /etc/resolv.conf.
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete = Invalid
--
Can you please edit the bug description to give a lot more detail about
your system and about the malfunction?
--
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/1294239
Title:
dnsmasq
Comment out the line `dns=dnsmasq` in
/etc/NetworkManager/NetworkManager.conf and reboot.
** 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.
We certainly don't want to run resolvconf -u too few times. That is
the bug.
It causes no logical malfunction to run resolvconf -u too many times,
but doing so is not efficient. When a resolvconf update occurs then all
the scripts in /etc/resolvconf/update.d/ get run. If a heavy update
script is
Hmm, good questions . /me thinks.
The (small) gain is that we omit an unneeded update run prior to the
update run that occurs shortly afterwards when the dnsmasq initscript
calls resolvconf.
When other things touch resolvconf the update run can't be omitted.
We don't want to skip the update
When the dnsmasq package is installed its postinst starts the dnsmasq
daemon via the initscript. Dnsmasq initially reads what is most probably
an empty file from /var/run/dnsmasq/resolv.conf and so initially can't
resolve names. (The file is probably empty because it is generated by
** Description changed:
- When using DNS resolving daemons like dnsmasq the mountall-net is done
- to early in the boot process when DNS is not available.
+ When using a DNS resolving daemon such as dnsmasq the mountall-net is
+ done too early in the boot process, when DNS is not available.
--
Fixed in 2.67, not in 2.66.
--
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/1203430
Title:
dnsmasq doesn't listen on a given 127.* listen-address if bind-
dynamic, interface and
Dnsmasq gets its nameserver addresses from resolvconf via the file
/var/run/dnsmasq/resolv.conf. That /etc/resolv.conf contains only
127.0.0.1 is correct.
** Changed in: dnsmasq (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server
You don't need to set `listen-address=127.0.0.1` in /etc/dnsmasq.conf;
dnsmasq listens on that address by default.
If dnsmasq is not being used then you have a nonstandard configuration.
If you do not need a nonstandard configuration then I suggest that you
purge the dnsmasq package and reinstall
How do you rule out this being VirtualBox's fault?
--
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/1228955
Title:
dnsmasq changeds virtualbox guests PTR queries into A queries
To
Hi Bar,
I can reproduce the behavior: Debian 7 in VM with NATted network
interface on VirtualBox 4.2.16 on Ubuntu 13.04 with the NetworkManager-
controlled dnsmasq instance running. Using wireshark on the host I see
127.0.1.1 receiving an A query instead of a PTR query.
** Package changed:
Jérôme, it's nice to hear that it is working correctly, but which of the
following is the case?
1. Dnsmasq is working correctly in the standard factory configuration.
2. It is working with no-negcache mode activated.
3. It is working with clear-on-reload mode activated.
4. It is working and
Jérôme, can you please see if clear-on-reload fixes the problem,
without no-negcache?
** 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.
** Changed in: dnsmasq (Ubuntu)
Status: New = In Progress
--
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/1203430
Title:
dnsmasq doesn't listen on a given 127.*
Hi Simon,
I think we've established that the submitter is having a problem with
dnsmasq server, not with NetworkManager-controlled dnsmasq. So it would
be interesting to know if clear-on-reload fixes the submitter's problem.
(He already said that no-negcache fixes it.)
That clear-on-reload is
Public bug reported:
If I start dnsmasq as follows
dnsmasq --conf-file= --resolv-file=/tmp/r.conf --bind-dynamic
--listen-address=127.0.3.1
echo nameserver 192.168.1.254 /tmp/r.conf
then I can resolve a name, e.g., www.microsoft.com, with dig.
dig @127.0.3.1 www.microsoft.com
** 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
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
** Changed in: dnsmasq (Ubuntu)
Status: Triaged = Invalid
** Summary changed:
- Validate DNSSEC by default
+ Please enhance NetworkManager such that DNSSEC validation is done whenever
possible
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Summary changed:
- dnsmasq should not register 127.0.0.1 with resolvconf if it's not listening
on lo
+ Please enhance dnsmasq to talk directly to resolvconf and to register only
its actual listening address(es)
--
You received this bug notification because you are a member of Ubuntu
Server
The dnsmasq package is still not included on the Server ISO in 13.04.
The dnsmasq package is about 15KiB in size.
** Summary changed:
- The dnsmasq package isn't available on the server ISO
+ Please include the dnsmasq package on the Server ISO
--
You received this bug notification because
** Package changed: dnsmasq (Ubuntu) = ubuntu-meta (Ubuntu)
--
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/661599
Title:
Please include the dnsmasq package on the Server ISO
To
** Package changed: network-manager (Ubuntu) = dnsmasq (Ubuntu)
** Summary changed:
- NetworkManager uses dnsmasq with negative DNS cache enabled
+ Dnsmasq caches negative results if it starts before the network is up
--
You received this bug notification because you are a member of Ubuntu
Stéphane wrote:
Can you confirm that you have the dnsmasq package installed and not only
dnsmasq-base?
If so, then that bug is invalid as when you install dnsmasq on your system,
that'll bypass NetworkManager's own instance and so will run with the
default dnsmasq settings (including
What do you think, Simon?
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete = New
--
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/1172467
Title:
Dnsmasq caches negative
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
I think that this is ultimately an enhancement request for libvirt.
** Package changed: dnsmasq (Ubuntu) = libvirt (Ubuntu)
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
** Summary changed:
- Can't resolve both VM names and LAN names
+ Please run dnsmasq in such a way that it
The feature was dropped from the resolvconf package in Ubuntu 13.04. The
bind9 maintainers have been invited to add a similar feature to support
BIND 9. Your contribution may help to convince them to take action.
Until this feature actually appears in bind9 you will have to implement
it locally
** Changed in: dnsmasq (Ubuntu)
Status: Expired = Confirmed
** Description changed:
- dnsmasq does not resolve DNS names correcty.
+ Dnsmasq sometimes does not resolve DNS names correcty.
- Applications like Thunderbird or tools like ssh rely on working name
- resolution. However, if
Arno,
Does disabling NetworkManager-controlled dnsmasq fix the problem? (To
disable NetworkManager-controlled dnsmasq, comment out dns=dnsmasq in
/etc/NetworkManager/NetworkManager.conf and then restart network-
manager.)
Hypothesis: dnsmasq is given two nameserver addresses. The first
** 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
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
*** 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
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
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:
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
*** 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
Earlier there was some dispute about what the RFCs say about multiple
nameservers.
I found the following RFC which does have something to say about these
issues.
http://www.zoneedit.com/doc/rfc/rfc2182.txt
Here are a couple of passages...
Request for Comments: 2182
Category: Best Current
The target milestone should be adjusted, I guess.
--
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/1003842
Title:
dnsmasq sometimes fails to resolve private names in networks with
Hi Simon.
Before I forget to ask: can you please update dnsmasq(8) to include
under --strict-order a description of what happens when nameserver
addresses are passed in via D-Bus instead of via a file?
You wrote,
you can very easily provide the same behaviour - only pass the first
nameserver
[...cont'd after in order to fix...] bug #1072899, dnsmasq will have
to be enhanced such that proposition #1 is true. But we can discuss the
details of that in bug #1072899.
parenthesis
There is a close analogy between the problem here (bug #1003842) and a problem
we have with avahi. Avahi
Simon wrote:
Consider
[...]
server=/google.com/3.3.3.3
server=/google.com/4.4.4.4
[...]
Queries sent to *google.com will be sent 3.3.3.3 or 4.4.4.4 in the
same way as if strict order was set, ie, to 3.3.3.3 first, and only to
4.4.4.4 if 3.3.3.3 returns a SERVFAIL or REFUSED error, or doesn't
Simon in #49:
It doesn't work [...] the order of servers given to the DBus
interface isn't preserved internally
Aha, so the answer to my question
Will switching on strict-order have the same effect
now that nameserver addresses are sent over D-Bus?
(in comment #42) is No. So switching
there's still the unresolved question
of whether re-enabling --strict-order
will suffice as a workaround, since
12.10 relies on DBus to populate the
nameservers. Is there any extra
information on this?
Please try it and report back. :-)
(Put strict-order in a file in
Robie is right. In the failure case the resolver is contacting
127.0.1.1, where the NetworkManager-controlled dnsmasq process listens,
rather than 127.0.0.1, where BIND named is listening.
Robie is right, too, in saying that the instructions you followed have
to be reinterpreted for Ubuntu. In
** Description changed:
- The system dnsmasq is preventing nameservice from working with
- NetworkManager. By setting /etc/deafault/dnsmasq ENABLED=1 to ENABLED=0,
- nameservice started working again.
+ The standalone Dnsmasq (from the dnsmasq package) is preventing the
+
*** This bug is a duplicate of bug 933723 ***
https://bugs.launchpad.net/bugs/933723
** This bug has been marked a duplicate of bug 933723
bind9 registers itself with resolvconf even though it's unable to provide
name service
--
You received this bug notification because you are a
Compare bug #113417.
** Summary changed:
- host crashed with SIGSEGV in start_thread()
+ host crashed with SIGSEGV in start_thread() on login
** Summary changed:
- host crashed with SIGSEGV in start_thread() on login
+ host -t soa local. SIGSEGV in start_thread() on login
--
You received
** Summary changed:
- [apport] host crashed with SIGSEGV
+ [apport] host -t soa local crashed after resume from suspend
** Summary changed:
- [apport] host -t soa local crashed after resume from suspend
+ [apport] host -t soa local SIGSEGV after resume from suspend
--
You received this bug
** Summary changed:
- dnsmasq 2.6.1 package update required for precise
+ Please backport dnsmasq 2.6.1 or later to Precise
--
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/1103357
*** This bug is a duplicate of bug 1006898 ***
https://bugs.launchpad.net/bugs/1006898
** Description changed:
Ubuntu Precise currently ships with dnsmasq 2.59, but due to the issue
- reported in https://lists.launchpad.net/openstack/msg11696.html we
- require that to be updated in Precise
@tombert: Probably not the same issue, since the issue being discussed
here is not fixed by restarting. Please file a new bug report against
dnsmasq with a detailed description of your problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Not a NM problem; probably a dupe of #933723.
** Package changed: network-manager (Ubuntu) = bind9 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1098152
Title:
DNS resolve
David, I suggest you get a Linux expert to help you at your location.
** Changed in: bind9 (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
David T wrote in comment #8:
- Loaded Ubuntu 12.04
- Tried to install [a package]
- couldn't resolve dns
Possibly this is just another instance of bug #1000244.
David T, can you reproduce the failure?
** Description changed:
ARGH! Every release causes new problems :(
If you have:
Stéphane?
--
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/1003842
Title:
dnsmasq sometimes fails to resolve private names in networks with non-
equivalent nameservers
To manage
To anyone else who wants this feature: You are cordially invited to add
your voice here. :-) Please explain how you intend to use the feature.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Bug watch added: Debian Bug tracker #687507
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687507
** Also affects: resolvconf (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687507
Importance: Unknown
Status: Unknown
--
You received this bug notification
** No longer affects: bind
** Also affects: bind9 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483098
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Link to similar upstream bug report with title Please default to
RESOLVCONF=no (Upstream bug report #483098 is now being tracked in
Launchpad by wishlist bug #1091602 with title Please add resolvconf
hook script to generate dynamic forwarders list.)
** Bug watch added: Debian Bug tracker
** Description changed:
- This is a wish. It is requested that the bind9 package include a
- resolvconf hook script /etc/resolvconf/update.d/bind9 which writes a
- forwarders{} statement to /var/run/named/forwarders based on the
- nameserver information in resolvconf's database. Then in order
** Description changed:
It is requested that the bind9 package be enhanced such that named uses
forwarder addresses obtained from resolvconf's database.
Such a feature would normally be implemented by means of a resolvconf
update hook script, in this case
Yes, I'd say that wontfix is appropriate unless someone comes forward
with a reason why ntpd *should* listen at 127.0.1.1.
P.S. I earlier wrote the following.
It appears that bind9 operates in the same way.
I added a virtual interface eth0:0 with a bogus address
and named started listening
Public bug reported:
This is a wish. It is requested that the bind9 package include a
resolvconf hook script /etc/resolvconf/update.d/bind9 which writes a
forwarders{} statement to /var/run/named/forwarders based on the
nameserver information in resolvconf's database. Then in order to use
named
For the reason explained in comment #17, setting to Invalid for bind9.
** Changed in: bind9 (Ubuntu)
Status: Incomplete = Invalid
** Changed in: ntp (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
@Brian Burch: What is your opinion now about this report, insofar as it
affects ntp?
** Summary changed:
- Certain services do not listen on 127.0.1.1
+ ntpd does not listen on 127.0.1.1, the IP address associated with the system
hostname
--
You received this bug notification because you are
1 - 100 of 351 matches
Mail list logo
