Hi, at this time (02 Sept 10:45 Chilean time), the package currently 20%
phased (in Jammy), meaning it will be 100% phased in 8 x 6h = 48h if the
phasing is still 6 hours per 10%, which is roughly 10 hours after the
original DST for Chile. So some people will have their clocks incorrect
for some ti
Launchpad does not let me reopen this bug, but it should be reopened
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1716976
Title:
DNS resolver mixes IPv6 and IPv4 caches
Hi, this is still happening on 20.04.3. The reason I thought it had been
fixed is that I had implemented, and then forgot about, the workaround I
mentioned at the end of comment #9: I added records to our local
resolver. But if I remove them, the problem is still here.
--
You received this b
I'm currently on 18.10 and this bug seems to have been fixed. Abam, the
bug you point to does not currently happen on my system, so maybe both
have been fixed in 18.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd i
** Attachment added: "Wireshark capture of successful resolution, showing IPv6
stuff happening"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+attachment/4997138/+files/Screenshot%20from%202017-10-26%2018-36-23.png
** Summary changed:
- DNS resolver silently switches to an u
This is still happening with 17.10 final. I have been digging a bit and
found something that makes me think that this is a caching / IPv6 issue.
Attached is the screenshot of a Wireshark capture of the DNS packets on
all interfaces on the affected machine (the IP address of the machine is
192.168.0
Sorry, sorry, it does still happen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1716976
Title:
DNS resolver silently switches to an unknown DNS server
Status in system
It looks like this has been fixed, it is not occurring anymore.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1716976
Title:
DNS resolver silently switches to an unknown
Output of systemd-resolve --status when the problem does not occur
** Attachment added: "sr-ok.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+attachment/4954625/+files/sr-ok.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
Output of systemd-resolve --status when the problem occurs
** Attachment added: "sr-bad.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+attachment/4954624/+files/sr-bad.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
I attached the output of systemd-resolve --status in both cases. There
is no difference. In both cases it says the DNS server is 192.168.0.2
(our local resolver), although it seems it is using another, external
DNS server after a while.
Indeed the cache seems to be flushed when changing networking
Maybe interesting: systemd-resolve --status eth2 always reports the
correct, internal DNS server, even though names are incorrectly resolved
to their public IPs (I tried resolving with both dig and systemd-
resolve).
gpothier@tadzim3:~$ systemd-resolve --status eth2
Link 3 (eth2)
Current
Public bug reported:
In our network we have a DNS server that resolves some names to local
addresses, while the same names are resolved to our public IP when
public DNSs are used. For instance (using fictitious names and IPs),
xyz.mydomain.com resolves to the public IP 65.254.242.180 when using an
The problem persists in 17.10 as of today.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1667825
Title:
Requesting Cherry Pick: dns/resolved: consider configurati
Maybe this is related?
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1667825
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624317
Title:
systemd-resolve
Well actually I'm lost now. The code I obtain with apt-get source
network-manager is different from the one I obtain with bzr branch lp
:network-manager. The latter is supposed to be the most current way of
getting sources, but it doesn't have the file nm-dns-systemd-resolved.c.
Any ideas?
--
You
I tried applying the patch in the version of network-manager that comes in
Ubuntu 17.04 (1.4.4), and it didn't seem to work. In this version, the file
nm-dns-systemd-resolved.c is in src/dns-manager instead of src/dns, but I
assume it is the same.
Daniel, did it work for you?
--
You received t
Hi:
Regarding why I believe this is a bug in Ubuntu: it used to work, and stopped
working after an update, without any configuration change on my part. Besides,
there has been some flux in the resolvconf/dnsmasq systems, see for instance
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/164
Public bug reported:
I have been using 17.04 for a few weeks now, but a recent update seems
to have broken DNS resolution for VPN hosts. The local network is
192.168.50.*, with DNS at 192.168.50.2. The remote network is
192.168.0.*, with DNS at 192.168.0.2. I can ping remote hosts, but I
can't res
The problem seems to have been resolved in 17.04, I haven't hit it since
I upgraded.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1642973
Title:
DNS stops working when c
Any idea of how I could help debug this issue? It is 100% reproducible,
so I can do whatever testing is needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1642973
Tit
Yes, 192.168.0.2 is the gateway and DNS server for this connection.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1642973
Title:
DNS stops working when changing networ
Ok, here it goes. /run/resolvconf is attached.
It looks like there are several dnsmasq processes, but it is also the
case when things work. Here are the processes when it doesn't work:
gpothier@tadzim3:addons$ ps aux |grep dnsmasq
libvirt+ 1614 0.0 0.0 50200 1324 ?Snov14
Public bug reported:
Since upgrading to 16.10 I am having frequent DNS failures. It usually happens
when I change networks and after resume from suspend, for example going to home
from work, or vice versa. When this happens, connectivity is fine (I can ping
8.8.8.8 for instance), but I cannot r
PS: Restarting network-manager an reconnecting to the VPN works around
the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1592721
Title:
Don't write search
zim3 dnsmasq[1671]: using nameserver 192.168.0.2#53 for
domain 0.168.192.in-addr.arpa
Nov 1 23:09:28 tadzim3 dnsmasq[1450]: reading /etc/resolv.conf
Nov 1 23:09:28 tadzim3 dnsmasq[1450]: using nameserver 127.0.1.1#53
^C
gpothier@tadzim3:~$ ping somehost.ozone.caligrafix.cl
ping: somehost.ozone.calig
that tar thought there was a
hard link:
hrw--- libvirt-qemu/kvm0 2016-06-30 16:42
/tambor/pub/.zfs/snapshot/backup/gallery.img link to
tambor/luki/.zfs/snapshot/backup/vms/luki-odoo.qcow2
On the actual filesystem, stat shows the following about these files:
gpothier@lerne
I just noticed that I can do this instead of rebooting to work around the issue:
sudo hciconfig hci0 down
sudo hciconfig hci0 up
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
I have a bluetooth mouse (Genius Traveller 9005BT) that I have been
using without problems with Ubuntu for over a year. Since a few weeks
ago, however, it started disconnecting and reconnected from the
computer. The symptoms are like this:
1. The mouse works, and the bluetoot
29 matches
Mail list logo
