please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699660
Title:
systemd-resolve breaks
Plain vanilla install of Kubuntu 20.04 and this still seems to be a problem.
Tried @peci1 solution, but didn't do anything. I still can't resolve names to
IP-addresses.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Martin, your solution to disable systemd-resolve allowed me to
finally resolve hosts on my local network again... I was using a
temporary workaround of replacing "echo 'nameserver 192.168.1.1' >
/etc/resolv.conf", however that doesn't survive reboots.
This issue should be addressed by
I successfully work around this issue by the steps described at
https://askubuntu.com/a/907249/153828 :
Disable and stop the systemd-resolved service:
sudo systemctl disable systemd-resolved.service
sudo systemctl stop systemd-resolved
Then put the following line in the [main] section of your
Try using this:
https://www.freedesktop.org/software/systemd/man/resolved.conf.html#Domains=
"Use the construct "~." (which is composed of "~" to indicate a routing domain
and "." to indicate the DNS root domain that is the implied suffix of all DNS
domains) to use the system DNS server defined
IIRC what could be happening is that the additional timeout introduced
by systemd-resolved first doing the newly implemented LLMNR lookup
(which fails if not implemented by any device) causes some network tools
to not even try doing a DNS lookup using the DHCP- or user-supplied DNS
search domain
Hi,
Ubuntu 18.10 using systemd version 239-7ubuntu10.5:
I also see random results for dot-less domain or host names, i.e. it
seems after a certain timeout, a hostname is not found e.g. when trying
to establish an SSH connection to that machine using a single-label
name. Immediately followed by a
After testing further I get somewhat random results. Sometimes it fails
and sometimes after running "sudo service systemd-resolved restart" I
can resolve domains. Very weird.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just got bitten by this bug on 18.04 upgrade. This is the default config
on LEDE/OpenWRT that gets broken by this upstream decision. Ubuntu
should definitely ship a fix of some sort.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
One more affected usecase - wired LAN connection is not working properly for
VMWare Virtual Machine.
I use laptop with Win10 and run Ubuntu 18.04 as guest OS with VMWare.
Everything worked fine with Ubuntu 16 and 14, but with the current version the
DNS resolution is now broken and I cannot run
This is still a problem in 18.04. Like the OP, I have localhosts on my
LAN, but have no local domain configured. I had to disable systemd-
resolved on each of my LXC containers. What's worse, resolvconf creates
an empty /etc/resolv.conf file. So I had to create resolv.conf by hand
and point to
There is a regression with dns handling between xenial and zesty. There
are updates/improvements made in artful that will be published soon. It
may not solve your issue, but maybe/hopefully it will improve things a
lot.
systemd (234-1ubuntu2) artful; urgency=medium
* Set UseDomains to true, by
Same here. After upgrading somes pcs in my company from 16.04 to 17.10 :
lots of local services are not working anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699660
Title:
systemd-resolve
Ok, i see what you mean now. I will test this locally to verify.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
No, that won't help either.
You don't seem to understand: Adding a domain search list will not help
because the local machines do not have domains. They only have names,
like "host1" or "beetle", even on the network's DNS servers.
Since systemd's resolver refuses to consult the name servers for
You can adjust /etc/systemd/resolve.conf to add Domains= that you want
to use for single domain resolution for non-DHCP specified DNS server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699660
Sorry, typpo /etc/systemd/resolved.conf
https://www.freedesktop.org/software/systemd/man/resolved.conf.html#Domains=
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699660
Title:
systemd-resolve
According to the systemd documentation, UseDomains only affects systems
that get their network setup from DHCP, which is not the case at my
site. Furthermore, it is documented as a way to add a DNS search
domain, which would not help resolve hosts that have no domains.
So far, the only way I
you should be able to opt-into UseDomains by creating
/etc/systemd/network/usedomains.network
[DNS]
UseDomains=true
I believe. does above help you resolve things?
Can you tar up and attach the tarball of /run/systemd to investigate
which links you have available, and what domains they have?
19 matches
Mail list logo
