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?

  • AmbiguousProps@lemmy.todayEnglish
    0·
    7 months ago

    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.mlEnglish
      0·
      7 months ago

      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 ?

    • TCB13@lemmy.worldEnglish
      0·
      7 months ago

      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.todayEnglish
        0·
        7 months ago

        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.worldEnglish
          0·
          7 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?