Privacy

31981 readers

453 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

Chat rooms

[Matrix/Element]Dead
Discord

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

Quad9 censoring DNS requests? (lemmy.world)

submitted 7 months ago by mypasswordis1234@lemmy.world to c/privacy@lemmy.ml

39 comments fedilink hide all child comments

I noticed that Quad 9 is not able to respond to the spy.pet query:

$ dig spy.pet @9.9.9.9 +short
;; communications error to 9.9.9.9#53: timed out

But Cloudflare DNS is able to do it:

$ dig spy.pet @1.1.1.1 +short
104.26.0.165
104.26.1.165
172.67.74.73

And to be sure, I checked another domain with the same TLD to rule out the option that Quad9 is unable to handle the .pet TLD, but I received a correct answer...

$ dig hello.pet @9.9.9.9 +short
3.64.163.50

Does Quad9 censor DNS queries?

you are viewing a single comment's thread
view the rest of the comments

[–] TCB13@lemmy.world -2 points 7 months ago (1 children)

The thing is, everything you said is correct. But if you think they can just solve this globally for everyone and everything without delays by just pushing things their root servers or the first line of authoritative ones then what else can I say.

[–] AmbiguousProps@lemmy.today 1 points 6 months ago (2 children)

They can, because that's how DNS works. This is why when you update a record for your domain it's updated globally in near real time with multiple providers. I don't know how else to tell you that it already works this way. I work in the cloud, and deal with this stuff on a daily basis.

[–] lemmyreader@lemmy.ml 1 points 6 months ago (1 children)

This is why when you update a record for your domain it’s updated globally in near real time with multiple providers.

Depending on the TTL, right ?

[–] AmbiguousProps@lemmy.today 2 points 6 months ago

Correct!

[–] TCB13@lemmy.world -2 points 6 months ago (1 children)

This is why when you update a record for your domain it’s updated globally in near real time with multiple provider

So, you know that "near real time" is different from actual real time.

[–] AmbiguousProps@lemmy.today 0 points 6 months ago (1 children)

You're clearly going keep nitpicking and changing the subject to things that don't matter and you're not willing to learn. Your misunderstanding of the fundamentals of DNS is no longer my issue.

[–] TCB13@lemmy.world -1 points 6 months ago

Okay, so tell me something, in your "ideal world" replication-based only scenario, what happens if they're ordered to take down a specific A record that has a very large TTL, more than a govt would like?