New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to disable search domain entirely for specific DHCPv6 and/or DHCPv4 servers #6918
Comments
You will need to be a little more clear up front because DHCPv4 help text and code indicate it works as you expect: core/src/www/services_dhcp_edit.php Line 420 in 02b6085
core/src/etc/inc/plugins.inc.d/dhcpd.inc Lines 739 to 741 in 02b6085
Don't mind looking into it but I also don't want to spend time verifying otherwise. Cheers, |
The verification at https://github.com/opnsense/core/blob/02b6085023f9fa0a4b072d09da3c239bcf9bb985/src/www/services_dhcp.php#L235L237 says different, as it will not accept |
I've looked at |
I think both need to be able to have a dot only, aka disable sending |
|
Can you look at #6529 and maybe see if you can implement it. It would be quicker just to look at proposed changes. I don't have a lot of time at the moment due to 23.10 being released next week. |
This issue has been automatically timed-out (after 180 days of inactivity). For more information about the policies for this repository, If someone wants to step up and work on this issue, |
Now that I'm back on the opnsense train, I have a need to fix this particular problem. :) |
Nice. I’m back next week. Please ping me at the end of the week if I forget to merge your changes after a test drive and rechecking documentation. |
I tried this out with |
@fichtner ping, wasn't sure which end of week you meant. |
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
My FR is related to the problem that comes from having Kubernetes pods inherit the DNS settings from hosts that get an search-domain set, as it will result in unwanted behavior due to the default ndots of 5.
Describe the solution you like
I would like the ability to not set search domain at all in specific DHCP server settings for both v6 and v4.
I think that when disabled, the correct behavior would be to not send search domains at all.
Describe alternatives you considered
I have considered to just reconfigure the hosts to not accept DNS from DHCP, but that's not the right choice to me.
Additional context
This was specifically painful before alpine 3.18 due to musl related DNS stub resolver thing
The text was updated successfully, but these errors were encountered: