Recent submissions

Comment · 1 year ago
Wait, Namecheap deactivates your domain name if you have a temporary DNS outage?
Comment · 1 year ago
You should email them about the form and about your domain. Their email address is listed on the website. <https://quad9.net/support/contact/>

Sometimes the upstream blocklist provider will be easy to contact directly as well. Sometimes not so much.

Comment · 1 year ago
Even without "all-servers", DNSMasq will race servers frequently (after 20 seconds, unless it's changed), and when retrying. A sudden outage should only affect you for a few seconds, if at all.
Comment · 1 year ago
Unless the privacy policy changed recently, Google shouldn't be doing anything nefarious with 8.8.8.8 DNS queries.
Comment · 1 year ago
This sounds like a very serious security vulnerability...?
Comment · 1 year ago
Wellp. Incident report: "We posted our first incident report to Cloud Service Health about ~1h after the start of the crashes, due to the Cloud Service Health infrastructure being down due to this outage."
Comment · 2 years ago
Related: <https://www.sprint.net/>'s IP address was 2600:: for many years, but they sadly started using a DDoS mitigation service with different IPs.
Comment · 3 years ago
Is collecting a shipping address because PayPal's JavaScript is broken legal under the GDPR?
Comment · 3 years ago
Comment · 4 years ago
Maybe not the entire region. Amazon was reportedly building a data center complex next to the natural gas Hermiston Generating Plant some distance from the river.
Comment · 4 years ago
I have bad news for you, Linode's authoritative DNS service also uses Cloudflare DNS Firewall.

  $ dig +short ns1.digitalocean.com aaaa
  2400:cb00:2049:1::adf5:3a33
  $ dig +short ns1.linode.com aaaa
  2400:cb00:2049:1::a29f:1a63
Comment · 4 years ago
As I understood it, the difference between the $2.50 and $3.50 Vultr VPSes is an IPv4 address. I don't know why that page doesn't explain. Maybe it's changed.
Comment · 4 years ago
This has a couple bugs:

1.1.1.2 and 1.1.1.3 both return the SVCB records for 1.1.1.1. (I don't know if clients would ignore them, or actually switch to 1.1.1.1.)

Non-SVCB-type queries for _dns.resolver.arpa return NXDOMAIN instead of NOERROR. (This probably doesn't have significant impact, but might break it for some clients, e.g. if they can be tricked into making queries for _dns.resolver.arpa, or if a downstream resolver makes DS queries.)

Comment · 4 years ago
They moved data centers (to Hurricane Electric Fremont 2). It's not unusually unreliable.
Comment · 4 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton