Bug 1462505

Summary:	systemd-resolved falls back to google public DNS servers
Product:	Red Hat Enterprise Linux 7	Reporter:	Ahmed Nazmy <anazmy>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	fcami, msekleta, pablo.iranzo, systemd-maint-list
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-15 07:38:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ahmed Nazmy 2017-06-18 08:07:09 UTC

Description of problem:


Version-Release number of selected component (if applicable):
systemd-219-19.el7_2.13
systemd-resolved-219-19.el7_2.13

How reproducible:
always

Steps to Reproduce:
1. Remove namserserver from /etc/resolv.conf
2. Remove DNS settings from /etc/sysconfig/network-scripts/ifcfg-*
3. systemctl restart systemd-resolved
4. Enable systemd-resolved in /etc/nsswitch.conf:  "hosts: files dns resolve"
5. Perform any task that requires name resolution .


Actual results:
the logs shows clearly the query is directed to google DNS server :
~~~
Jun 18 08:01:52 rhel7 systemd: Started Network Name Resolution.
Jun 18 08:01:56 rhel7 systemd-resolved: Switching to system DNS server 8.8.8.8.
~~~

tcpdump confirms it :

~~~
08:01:56.600174 IP google-public-dns-a.google.com.domain > rhel7.example.com.60568: 50314 1/0/0 A 209.132.183.105 (44)
08:01:56.750680 IP rhel7.example.com.60568 > google-public-dns-a.google.com.domain: 2601+ PTR? 105.183.132.209.in-addr.arpa. (46)
08:01:56.778265 IP google-public-dns-a.google.com.domain > rhel7.example.com.60568: 2601 1/0/0 PTR redirect.redhat.com. (79)
~~~


Expected results:
systemd-resolved doesn't use fallback nameservers and reports an error instead

Comment 9 RHEL Program Management 2021-01-15 07:38:28 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.