[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

2018-05-17 Thread Steve Langasek
I can reproduce @earth2mark-eeepc's findings at another Starbucks. -- 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/1766969 Title: DNS cannot be resolved in Hotel Hotspot

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

2018-05-15 Thread Mark Schroeder
I have the latest systemd recommended by #1727237, and this issue still occurs at Starbucks as well. The Starbucks WIFI defect is #1767900 which appears to be a duplicate of this one. ii systemd237-3ubuntu10 amd64system and service manager I'm in a

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

2018-05-12 Thread Steve Langasek
> The internal resolver of systemd does not properly search the local dns. > Only fqdn's will resolve. This is easily mitigated and does not require > a whole bunch of enabling or disabling of things. That is unrelated to this bug report. -- You received this bug notification because you are a

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

2018-05-11 Thread Mark Daku
I have encountered this bug as well. I have raised it with systemd-resolved. The internal resolver of systemd does not properly search the local dns. Only fqdn's will resolve. This is easily mitigated and does not require a whole bunch of enabling or disabling of things. The DHCP process

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

2018-05-01 Thread Dimitri John Ledkov
I'm now questioning if it is at all sensible to use EDNS by default. It seems like the fallback should be widened for all NXDOMAIN lookups. I've validated, that lookups fail, when DNSSEC enabled (however with a SERVFAIL, rather than NXDOMAIN). Note DNSSEC is not enabled by default. -- You

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

2018-04-25 Thread Steve Langasek
Can confirm that the dns logs indicate that systemd-resolved is not falling back from UDP+EDNS0 to UDP in response to these NXDOMAIN answers. The existing patch only implements this fallback when the portal name being looked up includes 'secure' as a substring: +if

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

2018-04-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

2018-04-25 Thread Pete
Wireshark logs for default conf of Kubuntu and logs with workaround ** Attachment added: "wireshark logs" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+attachment/5127251/+files/dnsresolv.7z ** Tags added: dns systemd systemd-resolv ** Description changed: I was asked