-
Notifications
You must be signed in to change notification settings - Fork 426
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
options to bypass domain validation? #2009
Comments
This looks like an error from the idna crate. I'm not sure why/where that gets invoked, though. Can you provide some sample code for how your |
hi @djc thanks for you response. actually I was being misleading - I had two implementations of my DNS client and the manual crafting with bad names is actually working fine. and the error was actually returned by the default system client, and the minimum repro is :
and looking at the options here https://docs.rs/trust-dns-resolver/latest/trust_dns_resolver/config/struct.ResolverOpts.html I also don't see it's able to bypass the validation - any thoughts? |
This allows DNS labels used for lookups to contain underscores, which may not be allowed as host names. Prevents false TempError result, which masks underlying "proto error: Label contains invalid characters: Err(Errors { invalid_mapping, disallowed_by_std3_ascii_rules })" See also hickory-dns/hickory-dns#1904 hickory-dns/hickory-dns#2009
This allows DNS labels used for lookups to contain underscores, which may not be allowed as host names. Prevents false TempError result, which masks underlying "proto error: Label contains invalid characters: Err(Errors { invalid_mapping, disallowed_by_std3_ascii_rules })" See also hickory-dns/hickory-dns#1904 hickory-dns/hickory-dns#2009
I was able to build a "bad name" with
rr::Name::from_str_relaxed
for example: some_domain.understorehowever when I use the client to exchange the message I got this error
does it mean the client is validating the domain and failing with invalid char - is there a way to bypass the validation?
The text was updated successfully, but these errors were encountered: