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
Apple Services after not available after some time. Only renewing the internet connection will solve it. #777
Comments
Hello there! Please clarify the following information:
|
|
To start, the easiest test is to try to disable all third-party filters except AdGuard DNS and check if the issue persists. |
Will try to look at it with iOS 17.5 and macOS 14.5 installed. Maybe it's a Apple bug which has been resolved?! |
@Chinaski1 I can give you the update, that the issue just appeared again when changing WAN networks. I also checked the query logs and cannot see any block within this time and/or domains... So the blocklists shouldn't be the issue and it looks like it is something else. Changing DNS profile to some other provider solves the issue. Going back to AdGuard DNS after that also works. EDIT: |
Just do give you an update over here... When changing to an other DNS service (Contr...D, Ne...DNS) I do not have those issues (using nearly the same blocklists) and I think it's not related to blocklists itself, as there is nothing showing up within blocked queries. So something must be different within AdGuard DNS? |
At this stage it is difficult to say what may be causing the issue. It is not reproduced on our side, we are looking into it. |
I use AdGuard DNS via mobileconfig on 10 Apple devices, including iPhones, iPads, Macbooks and Apple TV and do not have this problem and cannot reproduce it. |
Thanks for your feedback. Really a strange behavior. For me I can more or less reproduce it on several devices with several kind of blocklists (don’t think the lists are the issue). What I (maybe) found out is, that it is eventually related to changing WAN networks with IPv4/IPv6 changing. Don’t know if this is maybe the case and has something to do with my issues. As it happended to several macOS/iOS versions I don’t think that this is the case. Especially while hagezi says that everything is fine for his devices. Don’t know how can look into more details to report it over here to find the reason why this is happening (and also only happening when using AdGuard DNS - with NextDNS and ControlD and other DNS services I don’t have those issues?!). As I said, I will try to narrow it down so that finding the reason is easier?! Thanks for your product and help over here. |
Platform
macOS
Protocol
DNS-over-HTTPS
Do you use AdGuard app?
No I don't
Your configuration
Traceroute to AdGuard DNS
./. doesn't matter
Issue Details
Expected Behavior
It should work all the time
Actual Behavior
When using AdGuard DNS (with some blocklists) the problem exists and reappears often.
Screenshots
No response
Additional Information
When using some other DNS services like NextDNS, ControlD etc. (nearly same blocklists enabled) the issue is not existent
It looks like it's something correlated to AdGuard DNS service at all?
The text was updated successfully, but these errors were encountered: