iOS encrypted DNS guide: iCloud Private Relay & Little Snitch notes appear incorrect/outdated
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- ios
- Domain
- documentation
Research direction
Open docs/en/Setup_Guides/iOS/iOS_14_and_later_(Encrypted).md and review the “VPNs, iCloud Private Relay, Little Snitch” section against Apple’s iCloud Private Relay Overview, especially “Custom DNS settings.” Update the guide so its encrypted-DNS behavior is accurate and its iOS-specific software references are valid; done means the section no longer makes the reported claims.
Written by the indexing model from the issue text.
Description
Referenced Document
Summary
The section titled "VPNs, iCloud Private Relay, Little Snitch” appears to contain two issues specific to iOS:
- The statement about iCloud Private Relay not respecting DNS profiles is inaccurate when custom encrypted DNS (DoH / DoT) is used
- Little Snitch is mentioned in an iOS‑only guide, but Little Snitch is not available on iOS
iCloud Private Relay clarification
The document currently states:
“Apple private relay will use its own DNS servers at the system level, with no way to override it.”
However, Apple’s own iCloud Private Relay Overview documentation states:
If a user has configured custom‑encrypted DNS settings using a profile or an app, the DNS server specified will be used instead of ODoH.
Source (Apple):
https://www.apple.com/privacy/docs/iCloud_Private_Relay_Overview_Dec2021.PDF
(“Custom DNS settings” section)
Based on Apple’s documentation:
- Encrypted DNS (DoH / DoT) configured via profile or app is respected by iCloud Private Relay
- Unencrypted DNS (manual Wi‑Fi DNS / DHCP DNS) is not used for iCloud Private Relay traffic
Little Snitch mention
The heading and warning include Little Snitch, however:
- Little Snitch does not exist on iOS
- Dominant language
- No language data
- Stars
- 125
- Forks
- 19
- Avg merge
- 18h 31m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Quad9DNS/documentation
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Quad9DNS/documentation#15 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Quad9DNS/documentation#10 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
Quad9DNS/documentation#31 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
Quad9DNS/documentation#12 · 1 comment · 3 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in Quad9DNS/documentation
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100