*** This bug is a duplicate of bug 989585 ***
https://bugs.launchpad.net/bugs/989585
VarLogDistupgradeTermlog: "resolvconf.postinst: Error: Cannot replace
the current /etc/resolv.conf with a symbolic link because it is
immutable."
To fix this, either install resolvconf version 1.63ubuntu12 fr
*** This bug is a duplicate of bug 994539 ***
https://bugs.launchpad.net/bugs/994539
** This bug has been marked a duplicate of bug 994539
resolvconf 1.63ubuntu12 failed to install/upgrade -- "lsattr: Inappropriate
ioctl for device While reading flags on /etc/resolv.conf"
--
You received
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 th
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
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 are
To prioritize pdns-recursor's listen address in resolv.conf, edit
/etc/resolvconf/interface-order and replace the line
lo.!(pdns|pdns-recursor)
with the following line.
lo.*
See https://bugs.debian.org/308677 for background.
** Package changed: resolvconf (Ubuntu) => pdns-recursor (Ub
Try purging and reinstalling the resolvconf package.
Is there anything unusual about your machine?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525613
Title:
package resolvconf 1.78ubuntu1 failed
The content of the base file is processed, but due to resolvconf's rules
they may fail to show up in resolv.conf. Comments in the base file get
discarded. Lines like "nameserver w.x.y.z" are omitted if another line
is, e.g., "nameserver 127.0.1.1.". If you set
TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBAC
*** 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
Bugs, which is subsc
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 bel
> 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
--aut
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 bu
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: Ne
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978356
Title:
squid
By default the dnsmasq instance started by NetworkManager doesn't do any
caching.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994266
Title:
DNS fails due to wrong local domain
To manage notificat
> I see that your change has made it to vivid
\o/
> undesirable behavior: all DNS queries go to the VPN nameservers
That is in most cases the *desired* behavior, since only the VPN
nameservers have name information about both the VPN and the Internet.
Also, under what circumstances do you not t
*** This bug is a duplicate of bug 1385010 ***
https://bugs.launchpad.net/bugs/1385010
> did not know I am stepping on your toe here
No toes being stepped on here.
> had to take care of this, so I generate the resolv.conf from a package
- no link anymore
OK. Leave the resolvconf package ins
>>> undesirable behavior: all DNS queries go to the VPN nameservers
>> That is in most cases the *desired* behavior
> On today's systems, I don't think so. [...] Ubuntu run a dnsmasq instance...
> Rather than overwrite this...
You are right in saying that when there is a local forwarding nameserve
Returning to the main issue...
> Could this fix be considered for trusty-updates?
The patch is very simple and applying it involves little risk, so I'd
say yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
*** 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
Bugs,
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314697
Title:
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 inst
** Summary changed:
- indicator-printers not working on ubuntu 14.04 beta
+ indicator-printers not working on Ubuntu 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304434
Title:
indicator-pri
Can you find the "nameserver 127.0.0.1" line in one of the files in
/etc/resolvconf/resolv.conf.d/ or /run/resolvconf/interface ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315741
Title:
After u
/run/resolvconf/interface/lo.dnsmasq arises from /etc/init.d/dnsmasq
registering the standalone dnsmasq's listen address 127.0.0.1 with
resolvconf. Normally the standalone dnsmasq listens at all addresses
including 127.0.0.1. Did you have the standalone dnsmasq running?
It is normal that "nameserv
If the "dnsmasq" package is not installed then purging the dnsmasq
package will remove /etc/init.d/dnsmasq and solve your problem.
Do not purge or remove the "dnsmasq-base" package. The dnsmasq-base
package includes the dnsmasq binary which is used by NetworkManager.
Of course, the question remai
> 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 => Debia
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
*** This bug is a duplicate of bug 1000244 ***
https://bugs.launchpad.net/bugs/1000244
** This bug has been marked a duplicate of bug 1000244
Symlink /etc/resolv.conf does not exist after installation or upgrade of
resolvconf -- various causes
--
You received this bug notification becaus
I'll apply this patch upstream for the upcoming 1.76 release. However I
am not sure that Ubuntu is still syncing this package from Debian, so
someone may need to apply this in Ubuntu too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: network-manager-vpnc (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013646
Title:
VPN connected but private-network names cannot be resolved; by
Dnscache should listen on 127.0.0.1
and the dnscache initscript should register this address with resolvconf
and dnscache's resolvconf update script should ignore this address when
compiling the list of addresses to which dnscache should forward.
So far as I know this is already the case. Please
Probably not a bug, but if there turns out to be a bug then it is in the
djbdns package.
** Package changed: resolvconf (Ubuntu) => djbdns (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/130515
** Description changed:
- I have a forwardonly dnscache (from dbdns) set up on my system, with a
+ I have a forwardonly dnscache (from dbndns) set up on my system, with a
forwarding address set up to our campus resolver.
My system has a static IP configuration and in my
/etc/network/inter
OK, in first instance I thought you were talking about djbdns whereas I
should have noticed that you gave package details for dbndns. Sorry
about the mistake.
AIUI dbndns is a fork of djbdns, so I will assume that it is similar to
djbdns in the respects relevant here. Under that assumption I revis
> So if I understand correctly, the right thing to do would be
> to add the dnscache address to /etc/resolvconf/resolv.conf.d/base
> and *not* include the dnscache address under dns-nameservers in
> /etc/network/interfaces.
That will work, but only because there's a bug in
/etc/resolvconf/update.d
** Summary changed:
- Wireless login ignores its stored password
+ Wireless login is not pre-filled with its stored password
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/929403
Title:
Wireless log
*** This bug is a duplicate of bug 1084364 ***
https://bugs.launchpad.net/bugs/1084364
** This bug has been marked a duplicate of bug 1084364
Network-Manager Repeatedly Asks for Authorization (WPA2 Password)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Thanks for the report.
Either a third-party package or the administrator futzed with
/etc/resolv.conf independently of the resolvconf package.
** Changed in: resolvconf (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294239
Title:
dnsmasq preventing DNS loo
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Bug still present.
$ dpkg -l libc6
[...]
ii libc6:amd64 2.17-93ubuntu4
amd64
$ grep hosts /etc/nsswitch.conf
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
$ sudo su
# ./a.out
Making resolv.conf empty
Results of looking up www.googl
Public bug reported:
When the "hosts:" line in nsswitch.conf includes `mdns4` or
`mdns4_minimal` last and the network interface is taken down,
getaddrinfo() returns -5 (EAI_NODATA — "No address associated with
hostname") instead of something more appropriate such as -4 (EAI_FAIL —
"Non-recoverabl
By the way, I was wrong earlier: return value -5 is not EAI_FAMILY but
EAI_NODATA.
$ grep -r EAI_ /usr/include
/usr/include/netdb.h:# define EAI_BADFLAGS-1/* Invalid value for
`ai_flags' field. */
/usr/include/netdb.h:# define EAI_NONAME -2/* NAME or SERVICE is
unknown.
I created a new report, bug #1295229.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154599
Title:
getaddrinfo() returns -11 (EAI_SYSTEM) instead of -2
To manage notifications about this bug go to:
** Summary changed:
- getaddrinfo() returns -5 (EAI_FAMILY) when network interface is down
+ getaddrinfo() returns -5 (EAI_NODATA) when network interface is down
** Summary changed:
- getaddrinfo() returns -5 (EAI_NODATA) when network interface is down
+ With `hosts: mdns4` getaddrinfo() returns
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
--
** Changed in: avahi (Debian)
Importance: Unknown => Undecided
** Changed in: avahi (Debian)
Status: Fix Released => New
** Changed in: avahi (Debian)
Remote watch: Debian Bug tracker #393711 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** 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.
--
Y
The proper way for the admin to stop /etc/resolv.conf from being updated
by resolvconf is for him or her to remove the symbolic link
/etc/resolv.conf -> ../run/resolvconf/resolv.conf. The resolvconf
program only ever writes to the target of that symlink. Thus, in the
absence of that link, resolvcon
I wrote:
> The proper way for the admin to stop /etc/resolv.conf from
> being updated by resolvconf is for him or her to remove the
> symbolic link /etc/resolv.conf -> ../run/resolvconf/resolv.conf.
HeinMueck wrote:
> what you describe as the proper way will not work at all
>- take a look at /etc/
> 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
t
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 servin
** Description changed:
The resolvconf package comes with /etc/dhcp/dhclient-enter-
- hooks.d/resolvconf which convieniently undefines make_resolve_conf
- (previously defined by dhclient-script) and calls resolvconf.
+ hooks.d/resolvconf which, if /sbin/resolvconf is present, undefines
+ make_re
You are right. In the Debian version, the script is activated by "test
-x /sbin/resolvconf" where the presence of /sbin/resolvconf indicates
that the resolvconf package is installed. The convention in Debian is:
"If the resolvconf package is installed then disable your default resolv
.conf-updating
** Description changed:
The resolvconf package comes with /etc/dhcp/dhclient-enter-
- hooks.d/resolvconf which, if /sbin/resolvconf is present, undefines
- make_resolv_conf() (previously defined by dhclient-script) and calls
- resolvconf.
+ hooks.d/resolvconf which, if /sbin/resolvconf is presen
** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096600
Title:
Clicking "Edit Connections..." or "Connection Information
> In the case of static IPv4 but automatic IPv6, this will still result in the
> IPv4 taking precedence.
[...]
> I propose that the order list all of the IPv6 items before the IPv4.
Hmm, are there reasons for preferring either one over the other?
This may be one of those changes where the proble
That it is not new installs but old ones that fail to upgrade properly
is intriguing. Let's get to the bottom of this!
> Is there any way I can force apt or dpkg to install it
If you mean "... to install it (resolvconf) properly" then the answer is
that you do "dpkg-reconfigure resolvconf" after
@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
Bugs, which is subscribed to U
/etc/resolv.conf containing 127.0.0.1 was correct, provided you have a
local nameserver running that listens at IP address 127.0.0.1.
In Ubuntu 12.10, the dnsmasq process controlled by NetworkManager
listens at 127.0.1.1, not at 127.0.0.1, so it wasn't NetworkManager that
registered 127.0.0.1 with
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098152
Title:
DNS resolve failed after up
It's true. Looking at current NM src/nm-device.c line 1978:
static guint32
reserve_shared_ip (void)
{
guint32 start = (guint32) ntohl (0x0a2a0001); /* 10.42.0.1 */
guint32 count = 0;
This is upstream source code. Please file a bug report upstream.
https://bugzilla.gnome
To reduce administration, closed the report in Launchpad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098362
Title:
DHCP settings for network manager shared connection are hard-coded
source, sh
Possibly a driver issue
** Summary changed:
- network-manager fails to detect link status change
+ NetworkManager fails to detect link status change -- Intel 82577LM e1000e
** Description changed:
Steps to reproduce:
1.) Start Ubuntu, with LAN plugged in, login
- 2.) Verify Network Manag
Possibly a driver issue
** Summary changed:
- WIFI disconnects then can not connect to any network
+ Wi-Fi disconnects then cannot connect to any network -- Broadcom BCM43224 bcma
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you a
Please run "apport-collect 1093622" to provide more information.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: ac100
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Possibly a driver issue
** Summary changed:
- NetworkManager disconnects wifi and can't reconnect
+ NetworkManager disconnects Wi-Fi and can't reconnect -- Broadcom BCM4312 wl
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1003842 ***
https://bugs.launchpad.net/bugs/1003842
** This bug has been marked a duplicate of bug 1003842
dnsmasq sometimes fails to resolve private names in networks with
non-equivalent nameservers
--
You received this bug notification because you are
Fixed upstream in 0.2.0-7. Precise now has 0.2.0-7ubuntu1.
** Changed in: rpcbind (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/835833
Title:
spuriou
Thanks for testing. My hypothesis from comment #31 is false.
Is there anything unusual about your resolver configuration? Do you have
a "sortlist", "options", etc., line in resolv.conf? What is the "hosts"
line in your /etc/nsswitch.conf?
--
You received this bug notification because you are a
BTW I just discovered that "restart network-manager" no longer suffices
to reload the configuration of nm-dnsmasq because nm-dnsmasq doesn't get
killed on stopping network-manager. So if you edit files in
/etc/NetworkManager/dnsmasq.d/ you have to "stop network-manager ;
killall dnsmasq; start netw
> Have you filed a bug upstream with Gnome yet?
Nope.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085706
Title:
gnome-screensaver-dialog: pam_ecryptfs: seteuid error
To manage notifications abo
Except for the order in which "nameserver" option instances occur, the
order in options appearing in resolv.conf does not matter.
** Changed in: resolvconf (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> seems that strict-order is the way to go [...] Can that be automated
[...]?
There has been a discussion about the problem and possible solutions in
bug #1003842. I most recently expressed my opinion in comment #41 of
that ticket.
> It takes a long time to resolve the name
Why do you think that
The "-o" option is the same as the strict-order option.
The dnsmasq man page says that in strict-order mode dnsmasq uses the
order from "/etc/resolv.conf" but we shouldn't take that too literally
since dnsmasq obtains nameserver addresses from sources other than
/etc/resolv.conf. The dnsmasq proce
I just stumbled across Debian bug report #367715 which has the following
title.
ppp: overwrites /etc/resolv.conf despite "usepeerdns" being unset
The report says about Debian ppp 2.4.4b1-1 that
pppd sets the environment variable USEPEERDNS regardless
of the option 'usepeerdns' being
When dnsmasq is malfunctioning, does sending the dnsmasq process a
SIGHUP fix it?
sudo kill -HUP $(pidof dnsmasq)
This signal causes dnsmasq to clear its cache, but I imagine it might
also kick dnsmasq out of whatever faulty state it has got into.
--
You received this bug notification becau
*** This bug is a duplicate of bug 998712 ***
https://bugs.launchpad.net/bugs/998712
The symptoms are actually quite similar to the ones described by Wolf
Rogner in bug #998712, so I am going to mark this report as a duplicate
of that one.
** This bug has been marked a duplicate of bug 998712
By the way, is it still the case that only domain name completion is
malfunctioning, not DNS lookups in general and lookups of fully
qualified domain names in particular?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** This bug is no longer a duplicate of bug 998712
domain name completion broken when dnsmasq is used
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781557
Title:
multiple search domains not honou
*** This bug is a duplicate of bug 80900 ***
https://bugs.launchpad.net/bugs/80900
Noticing that the domain names in question end in .local, this could be
bug #80900.
Try the workaround. In /etc/nsswitch.conf, change
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
to
hosts:
Wolf, you wrote:
> nm-tool | grep DNS gives
>
>DNS: 10.1.0.4
>DNS: 10.1.0.254
>DNS: 195.202.128.3
You later wrote:
> I can confirm that my DNS server serves any request from inside the
network.
Which server serves the requests, 10.1.0.4 or 10.1.0.254? Are these
nameservers complete
The unusual time-dependent character of the malfunction makes me
speculate about more exotic possibilities such as misconfigured
firewalls or flaky hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I wrote that. The last sentence is a bit ugly but I was trying to keep
it short. More explicit would have been the following.
After a typical installation of Ubuntu 12.04, /etc/resolv.conf is a
symbolic link to ../run/resolvconf/resolv.conf. If, at the time the
machine is upgraded to Ubuntu 12.10,
Well, we are lucky that you do have a good workaround for the problem,
even if we don't yet fully understand it.
Do I understand correctly that your two internal nameservers can resolve
exactly the same domain names, neither one more names than the other?
If that is not the case then bug #1003842
All very well to classify this as a "wishlist opinion", but please
accompany that with some sort of reasoning.
Bind9's ifdown hook script does "rndc reconfig" which causes named to
notice changes that have been made. If the script is run *before* taking
down the interface then it is run when no ch
Thanks for the report.
When initially installed dnsmasq is configured to integrate with
resolvconf if resolvconf is also installed. This means that dnsmasq
sends its listen address (127.0.0.1) to resolvconf and uses resolvconf's
list of available nameservers to compile its own list of upstream
nam
This report has been downgraded to "wishlist opinion". Very well,
Yolanda, but please accompany that change with some sort of explanation.
Bind9's ifdown hook script does "rndc reconfig" which causes named to
notice changes that have been made. If the script is run *before* taking
down the interfa
Is Won't Fix the right status here? That implies that there *was* a
problem. Shouldn't it be Expired?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/457045
Title:
Command host chooses another DNS ser
@William McCall: Can you please test with the current version of the ppp
package? If you put the following
[ "$USEPEERDNS" ] || exit 0
near the top of /etc/ppp/ip-up.d/000resolvconf does that suffice to
prevent the malfunction that you reported? Or does it have to be the
following?
[ "$U
William wrote:
> I have implemented this with " [ "$USEPEERDNS" ] || exit 0"
> and found that the behavior is now appropriate.
Thanks, I'll go ahead and release Debian resolvconf 1.69 with that
change then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I just encountered this bug. The VPN Connections submenu is empty. I
can still up and down VPN connections using nmcli.
network-manager0.9.6.0-0ubuntu7
network-manager-gnome0.9.6.2-0ubuntu6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
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
Bugs, which is su
@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 a
Thanks, Stéphane.
It doesn't actually affect resolvconf — sorry if I gave that impression.
Because it is only the "down" script that is run at the wrong time (it
is currently run at pre-down time instead of post-down time), the effect
of the bug is minor: it only means that named is listening on t
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
This bug needs to be reopened because there are new reports of the
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/31286
Title:
Displays repeated keyring dialogs on resume from suspen
Update. The bug has been fixed, but not in Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/31286
Title:
Displays repeated keyring dialogs on resume from suspend and login
To manage n
401 - 500 of 3374 matches
Mail list logo
