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?

  • Ooops@feddit.orgEnglish
    1·
    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…