Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
There are two basic ways I can think of that you could still end up using OpenDNS without setting it as your DNS server in the private DNS settings. The first is simply if it's the default DNS that your ISP (in this case the phone company, since you mention you're not on WiFi) supplies. If you don't set a DNS server, then your system will obtain one at the same time it obtains an IP address via DHCP during the initial handshake with the ISP, because it needs to use something to translate website names into IP addresses. So if the ISP is configured to suggest OpenDNS, that'll still be what you'll use. You can override this by manually setting another DNS server. Note though that many DNS services (including a Google, if I recall correctly) use OpenDNS as a fallback setting, so if the main DNS site is down for some reason, you might still get OpenDNS results.
The other possibility is if have a VPN enabled, like Adguard or DNS66. These often affect DNS resolution as part of an effort to block ads. Again, manually setting a DNS, or disabling the VPN, should override this.
One last note is that there's a setting in Chrome that lets it bypass your DNS settings and use Google's own DNS for that app, so if you're using Chrome and Google's DNS server is down or doesn't have an entry for a particular site, that could still lead to OpenDNS being used for resolution. I haven't really found turning off that setting to work in getting Chrome to use my configured DNS, which is part of why I now use Firefox on Android, but in theory it should be possible to fix with "settings->privacy and security->secure DNS->use current provider," or with a custom configuration in the same setting, in Chrome, or by turning off secure DNS in the same spot.
Note that all these settings do have privacy implications, so it might be worth reading about those before mucking with any of them!