1.1.1.1 does not resolve archive.is


#1

Hello,

1.1.1.1 returns SERVFAIL for archive.is, Google 8.8.8.8 is fine. The DNSViz report (just analyzed today) does show problems. All information from the troubleshooting post is below.

 $ dig archive.is @8.8.8.8

; <<>> DiG 9.8.3-P1 <<>> archive.is @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4695
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;archive.is.                    IN      A

;; ANSWER SECTION:
archive.is.             299     IN      A       46.17.42.43

;; Query time: 127 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Aug  9 13:06:40 2018
;; MSG SIZE  rcvd: 44

 $ dig archive.is @1.1.1.1

; <<>> DiG 9.8.3-P1 <<>> archive.is @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 41948
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;archive.is.                    IN      A

;; Query time: 2560 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Aug  9 13:06:48 2018
;; MSG SIZE  rcvd: 28

 $ dig archive.is @1.0.0.1

; <<>> DiG 9.8.3-P1 <<>> archive.is @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 14050
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;archive.is.                    IN      A

;; Query time: 203 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Thu Aug  9 13:06:59 2018
;; MSG SIZE  rcvd: 28

 $ dig +short CHAOS TXT id.server @1.1.1.1
"YYZ"
 $ dig +short CHAOS TXT id.server @1.0.0.1
"YYZ"

http://dnsviz.net/d/archive.is/W2x2lg/dnssec/


#2

Archive.is has chosen not to publish their IP addresses to Cloudflare DNS resolvers. You’ll need to take up the issue with them.


#3

Thanks for the reply, I will inquire with them.

I haven’t seen this before. Other than guessing based on the SERVFAIL, how would I know this is what’s happening?

Regards


#4

Cloudflare has decided not to support eDNS0 in its current form to protect the privacy of users. One company I am aware of has decided this is unacceptable and refuses to return an answer.

Unfortunately there is no polite way I can explain how you would know this is happening… You could follow their twitter feed where they have made it clear that’s what they are doing i suppose, but who would bother?


#5

That’s helpful enough, appreciated. Sorry for the noise, I was unaware of this until today.


#6

I see this has also been explained already elsewhere, but searching didn’t turn it up. I’ll drop a link here in case others have trouble with archive.is as well (seems common enough).

(I was unable to edit my last reply to amend with this…)


#7

No worries… until recently I was hopeful they’d simply correct the IP address they were advertising. Turns out they don’t want to do that.