1183745 – google.com: resolve call failed: 'google.com' does not have any RR of the requested type

Bug 1183745 - google.com: resolve call failed: 'google.com' does not have any RR of the requested type

Summary: google.com: resolve call failed: 'google.com' does not have any RR of the req...

Status:	RESOLVED FIXED

Alias:	None

Product:	openSUSE Tumbleweed
Classification:	openSUSE
Component:	Network (show other bugs)
Version:	Current
Hardware:	x86-64 openSUSE Tumbleweed

Priority:	P5 - None Severity: Normal with 2 votes (vote)
Target Milestone:	---
Assignee:	systemd maintainers
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2021-03-19 02:57 UTC by André Werlang
Modified:	2023-04-06 10:01 UTC (History)
CC List:	5 users (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description André Werlang 2021-03-19 02:57:12 UTC

systemd-resolved stopped resolving many domains, including opensuse.org, google.com, github.com, etc.

Temporary workaround is to create a new /etc/resolve.conf including "nameserver 8.8.8.8" and restarting systemd-resolved.

$ rpm -q systemd
systemd-246.11-1.1.x86_64

Upstream report: https://github.com/systemd/systemd/issues/18917
It was reported that the defect was introduced in [1], which we can see was cherry-picked for the latest release [2].

[1] https://github.com/systemd/systemd/commit/18674159ebbf622a9e6e5a45cc36b38f74dae315
[2] https://github.com/openSUSE/systemd/compare/134cf1c8bc3e361a2641161aa11ac2b5b990480b...9753d1c17545a5d46530696cb14254f5f12024f1

Comment 1 Matthew Trescott 2021-03-20 15:30:35 UTC

I made a quick-and-dirty package to revert that patch so I could get my computer back, in case it's helpful.

https://download.opensuse.org/repositories/home:/matthewtrescott:/branches:/Base:/System/openSUSE_Factory/x86_64/systemd-network-246.11-6.1.x86_64.rpm.mirrorlist

Comment 2 Cristian Rodríguez 2021-03-22 21:16:03 UTC

Yes, it has stopped working for me as well..

Comment 3 Franck Bui 2021-03-23 08:11:27 UTC

(In reply to Matthew Trescott from comment #1)
> I made a quick-and-dirty package to revert that patch so I could get my
> computer back, in case it's helpful.

I'll do the same until this is properly fixed by upstream.

Comment 4 OBSbugzilla Bot 2021-03-24 08:30:06 UTC

This is an autogenerated message for OBS integration:
This bug (1183745) was mentioned in
https://build.opensuse.org/request/show/880868 Factory / systemd

Comment 5 Petr Kristof 2021-03-24 09:24:56 UTC

I can confirm this bug.

Workaround proposed by Andre does not work in my case. /etc/resolve.conf is rewrited back in several seconds.

I must disable systemd-resolved and created /etc/resolve.conf by hand.

Comment 7 OBSbugzilla Bot 2021-03-30 15:00:12 UTC

This is an autogenerated message for OBS integration:
This bug (1183745) was mentioned in
https://build.opensuse.org/request/show/882182 Factory / systemd

Comment 8 Franck Bui 2021-04-06 14:00:10 UTC

This should be fixed by the next update as the offending commit merged in the stable tree has been reverted.