[Bug 1668296] Re: not failing back to IPv4 when AAAA returns SERVFAIL

Steve Langasek steve.langasek at canonical.com
Fri Jan 26 20:59:13 UTC 2018


I cannot reproduce this with the libnss-resolve in Ubuntu 17.04 or
17.10.  The original problem was reported with systemd 231; 17.04
shipped with 232.  It is possible that this has been fixed in systemd
upstream (the linked upstream bug has been closed), or it's possible
that the DNS configuration for www.fidelityrewards.com has changed.  I'm
closing this fix-released, but if you know of another DNS name that is
still broken because of this, please reopen.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1668296

Title:
  not failing back to IPv4 when AAAA returns SERVFAIL

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  A reocrd exists, AAAA returns SERVFAIL, in this case resolution fails
  instead of falling back to IPv4 A record

  
  $ host www.fidelityrewards.com
  www.fidelityrewards.com has address 170.135.184.45
  Host www.fidelityrewards.com not found: 2(SERVFAIL)

  $ wget www.fidelityrewards.com
  --2017-02-27 07:41:57--  http://www.fidelityrewards.com/
  Resolving www.fidelityrewards.com (www.fidelityrewards.com)... failed: Name or service not known.
  wget: unable to resolve host address ‘www.fidelityrewards.com

  /etc/nsswitch.conf
  hosts:          files myhostname mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns wins 

  
  libnss-resolve 231-9ubuntu3

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



More information about the foundations-bugs mailing list