FS#35453 - [netctl] DNSSearch option not being set in resolv.conf

Attached to Project: Arch Linux
Opened by Walter (PreparationH67) - Thursday, 23 May 2013, 22:59 GMT
Last edited by Jouke Witteveen (jouke) - Monday, 27 May 2013, 21:28 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 2
Private No

Details

Description:
I can't seem to find anyone else reporting this problem, but with a static Ethernet profile then DNSSearch option is not ending up in the auto generated resolv.conf file. The DNSDomain option is also set and this is being inserted. The option itself is not being completely ignore since running 'resolvconf -l' shows the correct output with a search line. This problem shows up on machines that have multiple configured static Ethernet profiles as well just one. I have been unable to find any mention of this behavior any log files.

Additional info:
* netctl 1.0-1

Steps to reproduce:
Set
DNSSearch='some domain'
Launch network profile and inspect the resulting resolv.conf file.
This task depends upon

Closed by  Jouke Witteveen (jouke)
Monday, 27 May 2013, 21:28 GMT
Reason for closing:  Deferred
Additional comments about closing:  This is getting nowhere. If someone comes up with a patch, please reopen this bug. I do want to have it fixed.
Comment by Jouke Witteveen (jouke) - Sunday, 26 May 2013, 21:22 GMT
`man resolvconf.conf` suggests that you might want to set search_domains or search_domains_append in /etc/resolvconf.conf. Does that help?
Comment by Walter (PreparationH67) - Sunday, 26 May 2013, 21:29 GMT
I already had a work around in place, but this one seems to be a better option for now. Thanks.
Comment by Jouke Witteveen (jouke) - Sunday, 26 May 2013, 21:30 GMT
If this works, it is not a workaround. Does it work?
Comment by Walter (PreparationH67) - Sunday, 26 May 2013, 21:34 GMT
I haven't tried it yet, but I don't understand what you mean. I understand it may solve the problem, it's still a work around if it's not actually solving the problem of netctl profiles not behaving as documented and defeats the purpose of a centralized network configuration utility.
Comment by Jouke Witteveen (jouke) - Sunday, 26 May 2013, 21:35 GMT
The DNS functionality of netctl is a frontend to resolvconf. It is up to the user to configure resolvconf correctly.
Comment by Walter (PreparationH67) - Monday, 27 May 2013, 04:52 GMT
Ok, except the point of this bug report is that the front-end provided by netctl ISN'T functioning correctly. This is not an issue with resolvconf being configured incorrectly, the method you offered just states that the options will be set statically as it says in the resolvconf.conf man page IE prepending or appending to the dynamically generated list using one of those 2 options. I don't understand why you seem to be ignoring the fact that netctl is not behaving as configured and as it is documented in its man page. The DNSSearch option available as part of the netctl profile should still be function regardless of those options in resolvconf.conf
Comment by Jouke Witteveen (jouke) - Monday, 27 May 2013, 09:23 GMT
No, it should not. As I said: netctl interfaces openresolv. This gives netctl great power, but gives the end-user the 'burden' of having to know what he/she is doing. I agree that the documentation might be a bit suggestive. Either you could try to change the default configuration we ship with openresolv, or you could propose alternative documentation for netctl.
Comment by Walter (PreparationH67) - Monday, 27 May 2013, 17:10 GMT
So what you are literally saying is the software should not function as documented, by you. As I have read those options in openresolv.conf are meant to override or add to options generally given by DHCP, for example the DNS server blacklist option. I don't see how that is "suggestive", its says the front end provides this ability, it doesn't work, thus there is a bug with it. Instead of end-user blaming can we maybe take some actually sets to trying to solve the real problem here, because this is getting terribly frustrating.
https://github.com/joukewitteveen/netctl/blob/master/docs/netctl.profile.5.txt
'DNSSearch='::
A `++search++' line for '/etc/resolv.conf'.
or even better this line
'DNSOptions=()'::
An array of `++options++' lines for '/etc/resolv.conf'.


Loading...