this post was submitted on 09 Apr 2024
1019 points (98.8% liked)

Technology

34971 readers
110 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Aria@lemmygrad.ml 1 points 7 months ago

If a device makes an encrypted connection to a server the device makers own, there's nothing further you can gleam from studying the DNS lookups. They can route traffic through the first server, and they can resolve any IPs through the first server. And since you insist the person you're replying to doesn't know what DNS is because they said it's encrypted, I feel you might also not know that DNS can be encrypted. In that case, the network owner can see that a device makes a connection to the nameserver, but they can't see which addresses the nameserver was asked to resolve. And similarly, the device can refuse a connection to the wrong nameserver.