4 ms·
"As a result, when one types Facebook.com into a web browser, the browser has no idea where to find Facebook.com, and so returns an error page." Not quite. Ma
by 1vuio0pswjnm7 5y ago
"As a result, when one types Facebook.com into a web browser, the browser has no idea where to find Facebook.com, and so returns an error page."
Not quite.
Many DoH servers are working fine. DNS isn't a problem for the browser, but it seems to be a problem for Facebook's internal setup. It's like their proxy configuration is 100% reliant on DNS lookups in order to find backends.
The FB content servers are reachable. It is only the Facebook DNS servers that are unreachable.
Don't take my word for it, try for yourself
www.facebook.com 1 IN A 179.60.192.3 (content)
static.facebook.com 1 IN A 157.240.21.16 (content)
a.ns.facebook.com 1 IN A 129.134.30.12 (DNS)
ping -c1 157.240.21.16 |grep -A1 statistics
--- 157.240.21.16 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
ping -c1 179.60.192.3|grep -A1 statistics
--- 179.60.192.3 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
ping -c1 -W2 129.134.30.12 |grep -A1 statistics
--- 129.134.30.12 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
The browser, i.e., client, here, curl, has an idea where to find Facebook.com
curl -HUser-Agent --resolve www.facebook.com:443:179.60.192.3 https://www.facebook.com|sed windex.htm
Wait...
links -dump index.htm
[IMG]
Sorry, something went wrong.
We're working on it and we'll get it fixed as soon as we can.
Go Back
Facebook (c) 2020 . Help Center
grep HTTP index.htm
HTTP/1.1 503 No server is available for the request
- rbobby 5y agoIf I do: nslookup > server 8.8.8.8 Default Server: dns.google Address: 8.8.8.8 > facebook.com Server: dns.google Address: 8.8.8.8 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to dns.google timed-out Weird.
- chrononaut 5y agoAt the time, OP likely pulled cached DNS records to interrogate the associated IPs directly for their application (HTTP) level resources.
- rbobby 5y agoAnd thinking on this... a timeout is the right answer if facebook's dns servers are missing in action.
- 1vuio0pswjnm7 5y agoTheres no need to use a cache. Even if authoritative DNS servers are unreachable, there are, for example, multiple, authorised, public scans of port 53 available for free download. There are also passive DNS datasets also available for free. While recursive caches may be convenient, IMO they are the least trustworthy sources of DNS data.
- deleted 5y ago[deleted]