-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
DNS suffix isn't being honored on Linux #4
Comments
No, I'm not doing that and also not reading the configuration if available. Same as Could be a configuration option for the Also, the Linux specific code I have there right now for is meant to be removed. I added because there were a few bugs in .NET Core 1.0.0 which might be fixed now. Not sure if |
Got it. +search definitely would be nice to have. I can compensate in the meantime by handling my specific case in a wrapper. If I get spare time I might try to assist and open a PR. BTW..the last issue is working quite nicely now. ty! |
Sure go ahead, happy to accept PRs ;) |
Found this issue after some debugging. One challenge here is that running a dotnet-core app under Kubernetes, one doesn't necessarily know their search paths. If it was there as a configuration option to explicitly pass these in, we wouldn't (necessarily) know what to pass in. Some method of honoring the resolv.conf would be useful. |
@ingenthr @toddschilling I just added DnsSuffix to my NameServer type, if a network adapter has a DnsSuffix set, that property should be set, too. I might not build anything which uses that automatically with each Tested that on Ubuntu, at least under .NET5 see #122 |
I think I just got affected by the same issue.
I worked around it by specifying the FQDN, however it would be nice if the search-domains from /etc/resolv.conf were respected |
It appears that the DNS search suffix in the resolv.conf file isn't being appended to the hostname during query. I can see that the source code has a parser for it but didn't see any obvious places where it was being used.
The text was updated successfully, but these errors were encountered: