Skip to content
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

Resolver Mangles Case #3508

Closed
3 tasks done
gyCfjSnO opened this issue Aug 27, 2021 · 1 comment
Closed
3 tasks done

Resolver Mangles Case #3508

gyCfjSnO opened this issue Aug 27, 2021 · 1 comment
Labels
duplicate Duplicate or merged issues.

Comments

@gyCfjSnO
Copy link

Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed

Issue Details

  • Version of AdGuard Home server:
    • v0.106.3
  • How did you install AdGuard Home:
    • AdGuard Ubuntu Appliance for Raspberry Pi
  • How did you setup DNS configuration:
    • Router
  • If it's a router or IoT, please write device model:
    • Asus RT-AX58U Asuswrt-merlin 386.3_2
  • CPU architecture:
    • N/A
  • Operating system and version:
    • N/A

Expected Behavior

RFC 1034, which defines DNS, states in Section 3.1 that the letter case of a query (i.e. whether the domain name is spelled in upper case, lower case or a mix of the two) should be preserved.

Actual Behavior

AdGuard Home does not preserve the letter case of queries

Additional Information

I discovered this as the RIPE Atlas Probe I am running gives an error message that the DNS queries it is sending out is not coming back in the same letter case.

I confirmed it to be AdGuard Home causing the issue as I first did nslookup on my PC using AdGuard Home using a mangled query to 'GooGle.com' but the result comes back as 'google.com'. When changing my DNS to 9.9.9.9 or 1.1.1.1 for example the mangled query comes back the same.

@ainar-g
Copy link
Contributor

ainar-g commented Aug 27, 2021

Sounds like a duplicate of #3194, which is fixed in the edge and beta channels.

@ainar-g ainar-g closed this as completed Aug 27, 2021
@ainar-g ainar-g added the duplicate Duplicate or merged issues. label Aug 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicate or merged issues.
Projects
None yet
Development

No branches or pull requests

2 participants