[Touch-packages] [Bug 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails

2018-01-26 Thread Steve Langasek
*** This bug is a duplicate of bug 1731522 ***
https://bugs.launchpad.net/bugs/1731522

** This bug has been marked a duplicate of bug 1731522
   systemd-resolved does not listen on TCP port, cannot serve large records 
(Cannot ping pod51041.outlook.com but can dig.)

-- 
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/1665394

Title:
  DNS resolution of irc.freenode.net or chat.freenode.net fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.10 (from a base install upgraded several
  times), with proposed-updates enabled. Recently, I started having
  problems where I am unable to resolve irc.freenode.net.

  This is unrelated to the networks. I have been able to confirm that
  systemd-resolved is able to perform the name resolution. Yet,
  getaddrinfo() call returns -EAI_AGAIN error.

  This can be reproduced using getent:
  > $ getent ahosts irc.freenode.net
  > $

  While testing v4 or v6 directly returns something valid:
  > $ getent ahostsv4 irc.freenode.net
  > 38.229.70.22STREAM chat.freenode.net
  > 38.229.70.22DGRAM  
  > 38.229.70.22RAW
  > 130.239.18.119  STREAM 
  > 130.239.18.119  DGRAM  
  > 130.239.18.119  RAW
  [...]
  > $

  > $ getent ahostsv6 irc.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 DGRAM  
  > 2001:5a0:3604:1:64:86:243:181 RAW
  > 2001:6b0:e:2a18::118 STREAM 
  > 2001:6b0:e:2a18::118 DGRAM  
  > 2001:6b0:e:2a18::118 RAW
  [...]
  > $

  dpkg.log shows there has been some upgrade of systemd recently, though
  I cannot tell for sure if that directly relates to the problem, I do
  use suspend-to-ram a lot and reboot not that often.

  > $ lsb_release -a
  > LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  > Distributor ID: Ubuntu
  > Description:Ubuntu 16.10
  > Release:16.10
  > Codename:   yakkety

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails

2017-02-21 Thread Pirouette Cacahuète
It is likely to be an upstream problem. Given a zone with A/ records
with enough addresses, I can reproduce the problem.

Hacking in systemd source code, I could find those STR:
 - disable "resolve" in nsswitch.conf
 - add a resolution against a record with a lot of addresses in 
src/libsystemd/sd-resolve/test-resolve.c
 - build test-resolve tool
 - run ./test-resolve

e.g.:
> r = sd_resolve_getaddrinfo(resolve, , "test.neteffmon.eu", NULL, , 
> getaddrinfo_handler, NULL);

Running this results in:
> Assertion '*length <= maxlength' failed at 
> src/libsystemd/sd-resolve/sd-resolve.c:203, function serialize_addrinfo(). 
> Aborting.

Changing BUFSIZE in src/libsystemd/sd-resolve/sd-resolve.c to something
bigger (e.g. 65536U), rebuild and restart ./test-resolve, the resolution
succeeds.

-- 
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/1665394

Title:
  DNS resolution of irc.freenode.net or chat.freenode.net fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.10 (from a base install upgraded several
  times), with proposed-updates enabled. Recently, I started having
  problems where I am unable to resolve irc.freenode.net.

  This is unrelated to the networks. I have been able to confirm that
  systemd-resolved is able to perform the name resolution. Yet,
  getaddrinfo() call returns -EAI_AGAIN error.

  This can be reproduced using getent:
  > $ getent ahosts irc.freenode.net
  > $

  While testing v4 or v6 directly returns something valid:
  > $ getent ahostsv4 irc.freenode.net
  > 38.229.70.22STREAM chat.freenode.net
  > 38.229.70.22DGRAM  
  > 38.229.70.22RAW
  > 130.239.18.119  STREAM 
  > 130.239.18.119  DGRAM  
  > 130.239.18.119  RAW
  [...]
  > $

  > $ getent ahostsv6 irc.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 DGRAM  
  > 2001:5a0:3604:1:64:86:243:181 RAW
  > 2001:6b0:e:2a18::118 STREAM 
  > 2001:6b0:e:2a18::118 DGRAM  
  > 2001:6b0:e:2a18::118 RAW
  [...]
  > $

  dpkg.log shows there has been some upgrade of systemd recently, though
  I cannot tell for sure if that directly relates to the problem, I do
  use suspend-to-ram a lot and reboot not that often.

  > $ lsb_release -a
  > LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  > Distributor ID: Ubuntu
  > Description:Ubuntu 16.10
  > Release:16.10
  > Codename:   yakkety

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails

2017-02-17 Thread Pirouette Cacahuète
So, comment #5 is somehow invalid, I got the whole story on why it
started to work again: Schiggn (comment #4) contacted some Freenode
staff, and they changed the DNS records to expose less addresses. This
indeed proved to workaround the issue.

-- 
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/1665394

Title:
  DNS resolution of irc.freenode.net or chat.freenode.net fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.10 (from a base install upgraded several
  times), with proposed-updates enabled. Recently, I started having
  problems where I am unable to resolve irc.freenode.net.

  This is unrelated to the networks. I have been able to confirm that
  systemd-resolved is able to perform the name resolution. Yet,
  getaddrinfo() call returns -EAI_AGAIN error.

  This can be reproduced using getent:
  > $ getent ahosts irc.freenode.net
  > $

  While testing v4 or v6 directly returns something valid:
  > $ getent ahostsv4 irc.freenode.net
  > 38.229.70.22STREAM chat.freenode.net
  > 38.229.70.22DGRAM  
  > 38.229.70.22RAW
  > 130.239.18.119  STREAM 
  > 130.239.18.119  DGRAM  
  > 130.239.18.119  RAW
  [...]
  > $

  > $ getent ahostsv6 irc.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 DGRAM  
  > 2001:5a0:3604:1:64:86:243:181 RAW
  > 2001:6b0:e:2a18::118 STREAM 
  > 2001:6b0:e:2a18::118 DGRAM  
  > 2001:6b0:e:2a18::118 RAW
  [...]
  > $

  dpkg.log shows there has been some upgrade of systemd recently, though
  I cannot tell for sure if that directly relates to the problem, I do
  use suspend-to-ram a lot and reboot not that often.

  > $ lsb_release -a
  > LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  > Distributor ID: Ubuntu
  > Description:Ubuntu 16.10
  > Release:16.10
  > Codename:   yakkety

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails

2017-02-17 Thread Pirouette Cacahuète
Adding back "[NOTFOUND=return] resolve" to /etc/nsswitch.conf, setting 
DNSSEC=no in /etc/systemd/resolved.conf, restarting systemd-resolved process 
and then:
> $ getent ahosts irc.freenode.net
Gives proper list of hosts

Commenting again the DNSSEC line of resolved.conf, restarting the
service, and the resolution is still working. I'm a bit puzzled.

-- 
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/1665394

Title:
  DNS resolution of irc.freenode.net or chat.freenode.net fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.10 (from a base install upgraded several
  times), with proposed-updates enabled. Recently, I started having
  problems where I am unable to resolve irc.freenode.net.

  This is unrelated to the networks. I have been able to confirm that
  systemd-resolved is able to perform the name resolution. Yet,
  getaddrinfo() call returns -EAI_AGAIN error.

  This can be reproduced using getent:
  > $ getent ahosts irc.freenode.net
  > $

  While testing v4 or v6 directly returns something valid:
  > $ getent ahostsv4 irc.freenode.net
  > 38.229.70.22STREAM chat.freenode.net
  > 38.229.70.22DGRAM  
  > 38.229.70.22RAW
  > 130.239.18.119  STREAM 
  > 130.239.18.119  DGRAM  
  > 130.239.18.119  RAW
  [...]
  > $

  > $ getent ahostsv6 irc.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 DGRAM  
  > 2001:5a0:3604:1:64:86:243:181 RAW
  > 2001:6b0:e:2a18::118 STREAM 
  > 2001:6b0:e:2a18::118 DGRAM  
  > 2001:6b0:e:2a18::118 RAW
  [...]
  > $

  dpkg.log shows there has been some upgrade of systemd recently, though
  I cannot tell for sure if that directly relates to the problem, I do
  use suspend-to-ram a lot and reboot not that often.

  > $ lsb_release -a
  > LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  > Distributor ID: Ubuntu
  > Description:Ubuntu 16.10
  > Release:16.10
  > Codename:   yakkety

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails

2017-02-16 Thread Schiggn
iputils/ping was wrong.

On machines with this bug a "getent hosts chat.freenode.net" results in
no output! Perhaps we have to look at getaddrinfo()!

Thanks to the french ubuntu-channel #ubuntu-fr for this hint :)

** No longer affects: iputils (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1665394

Title:
  DNS resolution of irc.freenode.net or chat.freenode.net fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.10 (from a base install upgraded several
  times), with proposed-updates enabled. Recently, I started having
  problems where I am unable to resolve irc.freenode.net.

  This is unrelated to the networks. I have been able to confirm that
  systemd-resolved is able to perform the name resolution. Yet,
  getaddrinfo() call returns -EAI_AGAIN error.

  This can be reproduced using getent:
  > $ getent ahosts irc.freenode.net
  > $

  While testing v4 or v6 directly returns something valid:
  > $ getent ahostsv4 irc.freenode.net
  > 38.229.70.22STREAM chat.freenode.net
  > 38.229.70.22DGRAM  
  > 38.229.70.22RAW
  > 130.239.18.119  STREAM 
  > 130.239.18.119  DGRAM  
  > 130.239.18.119  RAW
  [...]
  > $

  > $ getent ahostsv6 irc.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 DGRAM  
  > 2001:5a0:3604:1:64:86:243:181 RAW
  > 2001:6b0:e:2a18::118 STREAM 
  > 2001:6b0:e:2a18::118 DGRAM  
  > 2001:6b0:e:2a18::118 RAW
  [...]
  > $

  dpkg.log shows there has been some upgrade of systemd recently, though
  I cannot tell for sure if that directly relates to the problem, I do
  use suspend-to-ram a lot and reboot not that often.

  > $ lsb_release -a
  > LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  > Distributor ID: Ubuntu
  > Description:Ubuntu 16.10
  > Release:16.10
  > Codename:   yakkety

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails

2017-02-16 Thread Schiggn
Perhaps this is an issue in iputils/ping if the response is to big. You
can try this with normal ping command too.

ping c1 chat.freeenode.net results in a "ping: chat.freenode.net:
Temporary failure in name resolution"

Using expicit -4 or -6 does work instead.

Workaround as mentioned above: switch "resolve [!UNAVAIL=return]" to
"resolve [UNAVAIL=return]" or place "resolve [!UNAVAIL=return]" after
"dns".

** Also affects: iputils (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1665394

Title:
  DNS resolution of irc.freenode.net or chat.freenode.net fails

Status in iputils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.10 (from a base install upgraded several
  times), with proposed-updates enabled. Recently, I started having
  problems where I am unable to resolve irc.freenode.net.

  This is unrelated to the networks. I have been able to confirm that
  systemd-resolved is able to perform the name resolution. Yet,
  getaddrinfo() call returns -EAI_AGAIN error.

  This can be reproduced using getent:
  > $ getent ahosts irc.freenode.net
  > $

  While testing v4 or v6 directly returns something valid:
  > $ getent ahostsv4 irc.freenode.net
  > 38.229.70.22STREAM chat.freenode.net
  > 38.229.70.22DGRAM  
  > 38.229.70.22RAW
  > 130.239.18.119  STREAM 
  > 130.239.18.119  DGRAM  
  > 130.239.18.119  RAW
  [...]
  > $

  > $ getent ahostsv6 irc.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 DGRAM  
  > 2001:5a0:3604:1:64:86:243:181 RAW
  > 2001:6b0:e:2a18::118 STREAM 
  > 2001:6b0:e:2a18::118 DGRAM  
  > 2001:6b0:e:2a18::118 RAW
  [...]
  > $

  dpkg.log shows there has been some upgrade of systemd recently, though
  I cannot tell for sure if that directly relates to the problem, I do
  use suspend-to-ram a lot and reboot not that often.

  > $ lsb_release -a
  > LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  > Distributor ID: Ubuntu
  > Description:Ubuntu 16.10
  > Release:16.10
  > Codename:   yakkety

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1665394/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails

2017-02-16 Thread Pirouette Cacahuète
A workaround is to remove "[NOTFOUND=return] resolve" from
/etc/nsswitch.conf, though it may break other things (but nothing
visible so far).

-- 
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/1665394

Title:
  DNS resolution of irc.freenode.net or chat.freenode.net fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.10 (from a base install upgraded several
  times), with proposed-updates enabled. Recently, I started having
  problems where I am unable to resolve irc.freenode.net.

  This is unrelated to the networks. I have been able to confirm that
  systemd-resolved is able to perform the name resolution. Yet,
  getaddrinfo() call returns -EAI_AGAIN error.

  This can be reproduced using getent:
  > $ getent ahosts irc.freenode.net
  > $

  While testing v4 or v6 directly returns something valid:
  > $ getent ahostsv4 irc.freenode.net
  > 38.229.70.22STREAM chat.freenode.net
  > 38.229.70.22DGRAM  
  > 38.229.70.22RAW
  > 130.239.18.119  STREAM 
  > 130.239.18.119  DGRAM  
  > 130.239.18.119  RAW
  [...]
  > $

  > $ getent ahostsv6 irc.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 DGRAM  
  > 2001:5a0:3604:1:64:86:243:181 RAW
  > 2001:6b0:e:2a18::118 STREAM 
  > 2001:6b0:e:2a18::118 DGRAM  
  > 2001:6b0:e:2a18::118 RAW
  [...]
  > $

  dpkg.log shows there has been some upgrade of systemd recently, though
  I cannot tell for sure if that directly relates to the problem, I do
  use suspend-to-ram a lot and reboot not that often.

  > $ lsb_release -a
  > LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  > Distributor ID: Ubuntu
  > Description:Ubuntu 16.10
  > Release:16.10
  > Codename:   yakkety

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails

2017-02-16 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.
https://bugs.launchpad.net/bugs/1665394

Title:
  DNS resolution of irc.freenode.net or chat.freenode.net fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.10 (from a base install upgraded several
  times), with proposed-updates enabled. Recently, I started having
  problems where I am unable to resolve irc.freenode.net.

  This is unrelated to the networks. I have been able to confirm that
  systemd-resolved is able to perform the name resolution. Yet,
  getaddrinfo() call returns -EAI_AGAIN error.

  This can be reproduced using getent:
  > $ getent ahosts irc.freenode.net
  > $

  While testing v4 or v6 directly returns something valid:
  > $ getent ahostsv4 irc.freenode.net
  > 38.229.70.22STREAM chat.freenode.net
  > 38.229.70.22DGRAM  
  > 38.229.70.22RAW
  > 130.239.18.119  STREAM 
  > 130.239.18.119  DGRAM  
  > 130.239.18.119  RAW
  [...]
  > $

  > $ getent ahostsv6 irc.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 DGRAM  
  > 2001:5a0:3604:1:64:86:243:181 RAW
  > 2001:6b0:e:2a18::118 STREAM 
  > 2001:6b0:e:2a18::118 DGRAM  
  > 2001:6b0:e:2a18::118 RAW
  [...]
  > $

  dpkg.log shows there has been some upgrade of systemd recently, though
  I cannot tell for sure if that directly relates to the problem, I do
  use suspend-to-ram a lot and reboot not that often.

  > $ lsb_release -a
  > LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  > Distributor ID: Ubuntu
  > Description:Ubuntu 16.10
  > Release:16.10
  > Codename:   yakkety

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665394/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp