I have replied to the upstream comment, however with Zesty I am seeing a
slightly different symptom. Both systemd-resolve and nslookup both
timeout rather than just being slow. Disabling DNSSEC still fixes it
however.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Colin, can you please reply to what upstream asked?
https://github.com/systemd/systemd/issues/3980#issuecomment-279779991
** Summary changed:
- nslookup doesn't works
+ Slow DNS lookup through Netgear DG834G V4 router
--
You received this bug notification because you are a member of Ubuntu
Hello. I'm recently upgraded to Zesty and the same messages in
journalctl (too many):
бер 05 14:33:56 p5q3 systemd-resolved[1223]: Using degraded feature set
(UDP) for DNS server 127.0.1.1.
Also:
~$ nslookup google.com
;; connection timed out; no servers could be reached
But:
~$
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609546
Title:
Slow DNS lookup through Netgear DG834G V4 router
To manage notifications about this bug go to:
I'm seeing a similar issue on current Ubuntu Yakkety with Android phone
AP via WPA2-personal:
$ systemd-resolve www.guugle.com
www.guugle.com: 208.73.210.200
208.73.210.214
208.73.211.178
208.73.210.217
-- Information acquired via protocol DNS in
Thanks Martin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609546
Title:
Slow DNS lookup through Netgear DG834G V4 router
To manage notifications about this bug go to:
Thanks for checking. So you can keep this workaround in place for the
time being.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Disabling DNSSEC appears to have solved the problem.
(I had to manually create /etc/systemd/resolved.conf.d/ before the command
would run)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609546
Thanks! I forwarded this to
https://github.com/systemd/systemd/issues/3980 .
Can you please try how this behaves when disabling DNSSEC?
printf '[Resolve]\nDNSSEC=no\n' | sudo tee
/etc/systemd/resolved.conf.d/nodnssec.conf
sudo systemctl restart systemd-resolved
and then resolve something?
** Attachment added: "systemd-resolve debug log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1609546/+attachment/4723282/+files/debug.txt
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Can you please generate a debug log for resolving a name when this takes
a long time?
sudo systemctl stop systemd-resolved
sudo SYSTEMD_LOG_LEVEL=debug script -c /lib/systemd/systemd-resolved
/tmp/debug.txt
then in another terminal
systemd-resolve www.google.com
Control-C the resolved
I am marking this New again as it has not actually been fixed by
upgrading the router. It now appears that the symptom is intermittent. I
have not been able to determine what it is that triggers it to fail or
work.
** Changed in: systemd (Ubuntu)
Status: Invalid => New
--
You received
Having updated the router to the latest firmware (5.01.17) the problem
appears to be resolved (even though the release notes made no mention of
DNS. Marking this bug as invalid.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
13 matches
Mail list logo
