Recently sites like archive.is and archive.ph are not resolving when using DNS providers from Mullvad and DNS4EU. Is it just me or does anyone else also experience this issue?

  • A_norny_mousse@feddit.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    6 days ago

    PPS: DNS4EU has an explicitly unfiltered one, also DoT-compatible: unfiltered.joindns4.eu (86.54.11.100) that resolves those archive links for me

    Not for me (Finland), haven’t tried DoT:

    $> dig archive.is
    ;; communications error to 86.54.11.100#53: timed out
    ^C
    $>
    $> dig archive.ph
    ;; communications error to 86.54.11.100#53: timed out
    ^C
    $>
    $> dig archive.today
    ;; communications error to 86.54.11.100#53: timed out
    ^C
    $>
    $> dig archive.org
    
    ; <<>> DiG 9.20.15-1~deb13u1-Debian <<>> archive.org
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25880
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 1400
    ;; QUESTION SECTION:
    ;archive.org.			IN	A
    
    ;; ANSWER SECTION:
    archive.org.		91	IN	A	207.241.224.2
    
    ;; Query time: 44 msec
    ;; SERVER: 86.54.11.100#53(86.54.11.100) (UDP)
    ;; WHEN: Wed Dec 24 19:10:20 EET 2025
    ;; MSG SIZE  rcvd: 56
    
    • Ooops@feddit.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      5 days ago

      Interesting. I just quickly changed my PC’s resolv.conf to use 86.54.11.100, so not DoT in that case either…

      ; <<>> DiG 9.20.17 <<>> archive.is
      ;; global options: +cmd
      ;; Got answer:
      ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2272
      ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
      
      ;; OPT PSEUDOSECTION:
      ; EDNS: version: 0, flags:; udp: 1232
      ;; QUESTION SECTION:
      ;archive.is.                    IN      A
      
      ;; ANSWER SECTION:
      archive.is.             300     IN      A       160.25.74.230
      
      ;; Query time: 249 msec
      ;; SERVER: 86.54.11.100#53(86.54.11.100) (UDP)
      ;; WHEN: Fri Dec 26 00:40:12 CET 2025
      ;; MSG SIZE  rcvd: 55
      

      Now I am slightly confused… For filtered entries I would not have expected a timeout on specific queries anyway, but a proper answer with an error.

      That’s a spontaneous slightly tin-foil idea, but can your provider block stuff with certain content before reaching the server? Can you try with DoT for encryption?

      Edit: Okay, there is definitely something strange going on with that server. If I try to use it over DoT I also get timeouts for archive.is

      So I’m going back to my original assessment before -surprisingly- DNS4EU resolved it properly for me. And I will keep to not expecting anything positive from that EU project…