Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by wolfgang42 on Saturday May 04, 2019 @03:45PM (#19828815)

I (random HN user) happen to know of lancaster.ac.uk (there was a comment thread a while back where this was mentioned).

[ Parent | on HN ]

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by Smylers on Sunday May 05, 2019 @02:35AM (#19831502)

In what way doesn't it work? This is with my ISP's DNS (using which I can visit https://www.lancaster.ac.uk/ in a browser):

  $ host -t a lancaster.ac.uk
  lancaster.ac.uk has address 148.88.65.80

and this is with Cloudflare's:

  $ host -t a lancaster.ac.uk 1.1.1.1
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  lancaster.ac.uk has address 148.88.65.80

Looks the same to me.

[ Parent | on HN ]

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by judge2020 on Saturday May 04, 2019 @03:54PM (#19828888)

This is a problem of the 1^4 resolver not implementing DNAME support (either not a priority, or just in the backlog): https://community.cloudflare.com/t/www-lancaster-ac-uk-not-r...

[ Parent | on HN ]