FS#59723 - [systemd] unset fallback DNS servers

Attached to Project: Arch Linux
Opened by nl6720 (nl6720) - Monday, 20 August 2018, 09:30 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 28 August 2018, 12:14 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
The choice of the fallback DNS servers will always be controversial.
Since there's no valid reason for DNS resolution to work if it's not configured either manually or by a network manager (*cough*  FS#59459  *cough*), why not just unset the fallback DNS servers addresses?

This can be done by providing no value to -Ddns-servers=

Additional info:
* package version(s)
* config and/or log files etc.
systemd 239.0-2

Steps to reproduce:
resolvectl status
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 28 August 2018, 12:14 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Please fix this locally if you'd prefer to have no fallback, or dislike our choice of defaults.
Comment by nl6720 (nl6720) - Monday, 20 August 2018, 09:33 GMT
Attached patch fixes this bug,  FS#59576 ,  FS#59459  and  FS#59186  .
   systemd.patch (2 KiB)
Comment by Dave Reisner (falconindy) - Monday, 27 August 2018, 18:38 GMT
> The choice of the fallback DNS servers will always be controversial.
Having working DNS out of the box isn't controversial. If you have specific allergies to whatever DNS backend is picked as a sane default, you can change it. Let's not politicize the issue at the cost of user experience for everyone.
Comment by nl6720 (nl6720) - Tuesday, 28 August 2018, 07:26 GMT
I have no further arguments.
If you deem that fallback DNS is a valid feature, close this bug.

Loading...