Bug 2054482 - dns resolution failure following TTL expiration
Summary: dns resolution failure following TTL expiration
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1889901
TreeView+ depends on / blocked
 
Reported: 2022-02-15 03:27 UTC by Chris Murphy
Modified: 2023-05-25 19:03 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 19:03:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Chris Murphy 2022-02-15 03:27:08 UTC
Description of problem:

I had just gone to https://qa.fedoraproject.org/blockerbugs/ which loaded, and I tried to authenticate which failed with a 502, and then all subsequent attempts to load the blocker bugs app failed. So I restarted resolved and then the page loaded OK. I got the idea to be quick on the trigger for resolved due to matanzaro's comment at https://bugzilla.redhat.com/show_bug.cgi?id=2006393#c34


Version-Release number of selected component (if applicable):
systemd-250.3-3.fc36.x86_64


How reproducible:
transient, seems related to TTL expiration

Steps to Reproduce:
no reproducer, just spontaneously happened on its own

Actual results:

spurious name resolution failures


Feb 14 19:40:23 fedora systemd-resolved[795]: Freeing transaction 48123.
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink: New incoming connection.
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink: Connections of user 993: 0 (of 576 max)
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink-22: Setting state idle-server
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink-22: New incoming message: {"method":"io.systemd.Resolve.ResolveHostname","parameters":{"name":"location.services.mozilla.com","flags":0}}
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink-22: Changing state idle-server → processing-method
Feb 14 19:44:17 fedora systemd-resolved[795]: idn2_lookup_u8: location.services.mozilla.com → location.services.mozilla.com
Feb 14 19:44:17 fedora systemd-resolved[795]: Looking up RR for location.services.mozilla.com IN A.
Feb 14 19:44:17 fedora systemd-resolved[795]: Looking up RR for location.services.mozilla.com IN AAAA.
Feb 14 19:44:17 fedora systemd-resolved[795]: Removing cache entry for prod.detectportal.prod.cloudops.mozgcp.net IN AAAA (expired 222s ago)
Feb 14 19:44:17 fedora systemd-resolved[795]: Removing cache entry for fedoraproject.org IN A (expired 206s ago)
Feb 14 19:44:17 fedora systemd-resolved[795]: Removing cache entry for fedoraproject.org IN AAAA (expired 175s ago)
Feb 14 19:44:17 fedora systemd-resolved[795]: Removing cache entry for prod.detectportal.prod.cloudops.mozgcp.net IN A (expired 158s ago)
Feb 14 19:44:17 fedora systemd-resolved[795]: Removing cache entry for locprod2-elb-us-west-2.prod.mozaws.net IN AAAA (expired 124s ago)
Feb 14 19:44:17 fedora systemd-resolved[795]: Cache miss for location.services.mozilla.com IN A
Feb 14 19:44:17 fedora systemd-resolved[795]: Firing regular transaction 25345 for <location.services.mozilla.com IN A> scope dns on wlp0s20f3/* (validate=yes).
Feb 14 19:44:17 fedora systemd-resolved[795]: Using feature level UDP+EDNS0 for transaction 25345.
Feb 14 19:44:17 fedora systemd-resolved[795]: Using DNS server 75.75.75.75 for transaction 25345.
Feb 14 19:44:17 fedora systemd-resolved[795]: Announcing packet size 1472 in egress EDNS(0) packet.
Feb 14 19:44:17 fedora systemd-resolved[795]: Emitting UDP, link MTU is 1500, socket MTU is 0, minimal MTU is 40
Feb 14 19:44:17 fedora systemd-resolved[795]: Sending query packet with id 25345 of size 58.
Feb 14 19:44:17 fedora systemd-resolved[795]: Cache miss for location.services.mozilla.com IN AAAA
Feb 14 19:44:17 fedora systemd-resolved[795]: Firing regular transaction 11345 for <location.services.mozilla.com IN AAAA> scope dns on wlp0s20f3/* (validate=yes).
Feb 14 19:44:17 fedora systemd-resolved[795]: Using feature level UDP+EDNS0 for transaction 11345.
Feb 14 19:44:17 fedora systemd-resolved[795]: Using DNS server 75.75.75.75 for transaction 11345.
Feb 14 19:44:17 fedora systemd-resolved[795]: Announcing packet size 1472 in egress EDNS(0) packet.
Feb 14 19:44:17 fedora systemd-resolved[795]: Emitting UDP, link MTU is 1500, socket MTU is 0, minimal MTU is 40
Feb 14 19:44:17 fedora systemd-resolved[795]: Sending query packet with id 11345 of size 58.
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink-22: Changing state processing-method → pending-method
Feb 14 19:44:17 fedora systemd-resolved[795]: Received dns UDP packet of size 206, ifindex=3, ttl=0, fragsize=0, sender=75.75.75.75, destination=10.0.0.85
Feb 14 19:44:17 fedora systemd-resolved[795]: Processing incoming packet of size 206 on transaction 25345 (rcode=SUCCESS).
Feb 14 19:44:17 fedora systemd-resolved[795]: Added positive unauthenticated non-confidential cache entry for location.services.mozilla.com IN CNAME 45s on wlp0s20f3/INET/75.75.75.75
Feb 14 19:44:17 fedora systemd-resolved[795]: Added positive unauthenticated non-confidential cache entry for locprod2-elb-us-west-2.prod.mozaws.net IN A 45s on wlp0s20f3/INET/75.75.75.75
Feb 14 19:44:17 fedora systemd-resolved[795]: Added positive unauthenticated non-confidential cache entry for locprod2-elb-us-west-2.prod.mozaws.net IN A 45s on wlp0s20f3/INET/75.75.75.75
Feb 14 19:44:17 fedora systemd-resolved[795]: Added positive unauthenticated non-confidential cache entry for locprod2-elb-us-west-2.prod.mozaws.net IN A 45s on wlp0s20f3/INET/75.75.75.75
Feb 14 19:44:17 fedora systemd-resolved[795]: Added positive unauthenticated non-confidential cache entry for locprod2-elb-us-west-2.prod.mozaws.net IN A 45s on wlp0s20f3/INET/75.75.75.75
Feb 14 19:44:17 fedora systemd-resolved[795]: Added positive unauthenticated non-confidential cache entry for locprod2-elb-us-west-2.prod.mozaws.net IN A 45s on wlp0s20f3/INET/75.75.75.75
Feb 14 19:44:17 fedora systemd-resolved[795]: Added positive unauthenticated non-confidential cache entry for locprod2-elb-us-west-2.prod.mozaws.net IN A 45s on wlp0s20f3/INET/75.75.75.75
Feb 14 19:44:17 fedora systemd-resolved[795]: Regular transaction 25345 for <location.services.mozilla.com IN A> on scope dns on wlp0s20f3/* now complete with <success> from network (unsigned; non-confidential).
Feb 14 19:44:17 fedora systemd-resolved[795]: Received dns UDP packet of size 192, ifindex=3, ttl=0, fragsize=0, sender=75.75.75.75, destination=10.0.0.85
Feb 14 19:44:17 fedora systemd-resolved[795]: Processing incoming packet of size 192 on transaction 11345 (rcode=SUCCESS).
Feb 14 19:44:17 fedora systemd-resolved[795]: Added positive unauthenticated non-confidential cache entry for location.services.mozilla.com IN CNAME 130s on wlp0s20f3/INET/75.75.75.75
Feb 14 19:44:17 fedora systemd-resolved[795]: Regular transaction 11345 for <location.services.mozilla.com IN AAAA> on scope dns on wlp0s20f3/* now complete with <success> from network (unsigned; non-confidential).
Feb 14 19:44:17 fedora systemd-resolved[795]: Freeing transaction 25345.
Feb 14 19:44:17 fedora systemd-resolved[795]: Following CNAME/DNAME location.services.mozilla.com → locprod2-elb-us-west-2.prod.mozaws.net.
Feb 14 19:44:17 fedora systemd-resolved[795]: Positive cache hit for locprod2-elb-us-west-2.prod.mozaws.net IN A
Feb 14 19:44:17 fedora systemd-resolved[795]: Regular transaction 25067 for <locprod2-elb-us-west-2.prod.mozaws.net IN A> on scope dns on wlp0s20f3/* now complete with <success> from cache (unsigned; non-confidential).
Feb 14 19:44:17 fedora systemd-resolved[795]: Cache miss for locprod2-elb-us-west-2.prod.mozaws.net IN AAAA
Feb 14 19:44:17 fedora systemd-resolved[795]: Firing regular transaction 62536 for <locprod2-elb-us-west-2.prod.mozaws.net IN AAAA> scope dns on wlp0s20f3/* (validate=yes).
Feb 14 19:44:17 fedora systemd-resolved[795]: Using feature level UDP+EDNS0 for transaction 62536.
Feb 14 19:44:17 fedora systemd-resolved[795]: Using DNS server 75.75.75.75 for transaction 62536.
Feb 14 19:44:17 fedora systemd-resolved[795]: Announcing packet size 1472 in egress EDNS(0) packet.
Feb 14 19:44:17 fedora systemd-resolved[795]: Emitting UDP, link MTU is 1500, socket MTU is 0, minimal MTU is 40
Feb 14 19:44:17 fedora systemd-resolved[795]: Sending query packet with id 62536 of size 67.
Feb 14 19:44:17 fedora systemd-resolved[795]: Freeing transaction 11345.
Feb 14 19:44:17 fedora systemd-resolved[795]: Received dns UDP packet of size 152, ifindex=3, ttl=0, fragsize=0, sender=75.75.75.75, destination=10.0.0.85
Feb 14 19:44:17 fedora systemd-resolved[795]: Processing incoming packet of size 152 on transaction 62536 (rcode=SUCCESS).
Feb 14 19:44:17 fedora systemd-resolved[795]: Added NODATA cache entry for locprod2-elb-us-west-2.prod.mozaws.net IN AAAA 267s
Feb 14 19:44:17 fedora systemd-resolved[795]: Regular transaction 62536 for <locprod2-elb-us-west-2.prod.mozaws.net IN AAAA> on scope dns on wlp0s20f3/* now complete with <success> from network (unsigned; non-confidential).
Feb 14 19:44:17 fedora systemd-resolved[795]: Freeing transaction 25067.
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink-22: Sending message: {"parameters":{"addresses":[{"ifindex":3,"family":2,"address":[52,40,22,163]},{"ifindex":3,"family":2,"address":[34,217,232,122]},{"ifindex":3,"family":2,"address":[54,187,53,15]},{"ifindex":3,"family":2,"address":[52,89,43,233]},{"ifindex":3,"family":2,"address":[54,187,205,23]},{"ifindex":3,"family":2,"address":[35,161,134,161]}],"name":"locprod2-elb-us-west-2.prod.mozaws.net","flags":9437185}}
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink-22: Changing state pending-method → idle-server
Feb 14 19:44:17 fedora systemd-resolved[795]: Freeing transaction 62536.
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink-22: Got POLLHUP from socket.
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink-22: Changing state idle-server → pending-disconnect
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink-22: Changing state pending-disconnect → processing-disconnect
Feb 14 19:44:17 fedora systemd-resolved[795]: varlink-22: Changing state processing-disconnect → disconnected
Feb 14 19:44:59 fedora sudo[6973]:    chris : TTY=pts/2 ; PWD=/home/chris ; USER=root ; COMMAND=/usr/bin/systemctl restart systemd-resolved



Expected results:

Should continue to resolve web pages


Additional info:

Comment 2 Ben Cotton 2023-04-25 16:54:03 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ludek Smid 2023-05-25 19:03:50 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.