Can't Enable Adguard dns server with IPv4 DNS over HTTPS automatic template
Please answer the following questions for yourself before submitting an issue
- [x] Filters were updated before reproducing an issue
- [X] I checked the knowledge base and found no answer
- [X] I checked to make sure that this issue has not already been filed
AdGuard version
7.18.1 (4778)
Browser version
Chrome 129.0.6668.90
OS version
Windows 11, 23H2
Traffic filtering
- [X] yes, I do
Ad Blocking
AdGuard Base filter, EasyList
Privacy
No response
Social
No response
Annoyances
AdGuard Cookie Notices filter, AdGuard Popups filter
Security
No response
Other
No response
Language-specific
List-KR
Which DNS server do you use?
System default DNS
DNS protocol
DNS-over-HTTPS
Custom DNS
No response
What Stealth Mode options do you have enabled?
No response
Support ticket ID
No response
Issue Details
Steps to reproduce:
- Go into Ethernet settings.
- Change DNS server assignment to manual and enter the address of Adguard dns.
- Change Turn on DNS over HTTPS (Automatic Template) and click Save.
Expected Behavior
The correct address should be automatically entered in DNS via the HTTPS template and saved normally.
Actual Behavior
Incorrect address is automatically entered in DNS via HTTPS template and error occurs when saving.
Screenshots
Screenshot 1 (Turn on DNS over HTTPS (Automatic Template))
Screenshot 2 (Turn on DNS over HTTPS (Manuel Template))
Additional Information
This issue is 100% reproducible so I'm sure it will be fixed soon.
@MadeByPP
Cannot reproduce this case and seems that it's not related to AdGuard for Windows product.
@Aydinv13 It must be reproduced in the Windows settings and I even provided a screenshot and settings location, but you are saying that it is not reproduced without any screenshots.
And does it have to be a problem with the program? If there was an error in the OS settings related to the program, the option could be used to request corrections from the OS developer for the customer.
Then I have nothing more to comment :(
@MadeByPP
It must be reproduced in the Windows settings and I even provided a screenshot and settings location, but you are saying that it is not reproduced without any screenshots.
sure, here is the screenshot of Windows settings (tested with 23H2 and 24H2 Insider Preview)
screenshot
Anyway, we'll test this on other devices and let you know.
@Aydinv13 I realized from the images you provided that this problem may not be 100% reproducible.
In my case, the problem is still reproducible and if you need any information other than the information provided in the original post, please let me know. I am ready to actively contribute to solving the problem.
@MadeByPP
Can you connect to different network and check the behavior? Also, check other IP addresses, such as 8.8.8.8 and 8.8.4.4, or 1.1.1.1 and 1.0.0.1.
@MadeByPP any news on this?
@Aydinv13 Sorry. I forgot your request. I‘ll check it and upload it soon.
@Aydinv13
Screenshot 1 (Turn on DNS over HTTPS Google(Automatic Template))
Screenshot 2 (Turn on DNS over HTTPS Cloudflare(Automatic Template))
Sorry, there should be 8.8.8.8 instead of 8.8.8.8.8, it was a typo.
@Aydinv13 8.8.8.8 and 8.8.4.4 Both work fine.
Screenshot 1 (Turn on DNS over HTTPS Google(Automatic Template))
Also, I found a hint. The automatic template throws an error, but if you use the manual template with the same dns address, the dns address is entered correctly. That is, this only happens when using automatic templates.
Screenshot 2 (Turn on DNS over HTTPS(Automatic Template))
Screenshot 3 (Turn on DNS over HTTPS(Manuel Template))
- Try to connect to different network then repeat the steps with AdGuard servers
- Turn off AV/Firewall if you have ones
- Update Windows
None of the three options worked for me
This indicates that the automatic DNS settings may conflict with your current network settings or system policies. If manual template bypasses this limitation, it is better to use it for given DNS server. This problem is clearly not related to the dns server itself, much less to AdGuard for Windows so I'm closing this issue.