6 ms·
Isn’t there an easy fix to just add a bullshit record for FB to DNS until this blows over? I am also thinking that all the poorly coded sites that don’t work u
by IgorPartola 5y ago
Isn’t there an easy fix to just add a bullshit record for FB to DNS until this blows over?
I am also thinking that all the poorly coded sites that don’t work unless the Share on Facebook button loads are also going to hemorrhage money. So are all the e-commerce sites that rely on Login with FB.
I hope this results in everyone rethinking adding all that shit to their infrastructure before the next time.
- noahtallen 5y agoMy understanding is that the Facebook network itself was unreachable from the internet because of BGP. So even if an IP was resolved from DNS, that IP wouldn’t get routed to Facebook because it withdrew its routes from its peers where it connects to ISPs via BGP
- AnimalMuppet 5y agoNot if the IP was 127.0.0.1...
- messe 5y agoThat's precisely what my ISP did. In fact, they went a step further and appear to have hijacked all unencrypted DNS queries. I was able to run DNS queries using 'example.com' as my DNS server and get a response.
- jbotz 5y agoThe problem isn't (wasn't) facebook.com's A records, it's that the authoritative nameservers for facebook.com are (were) unreachable. In theory someone could change the NS records for facebook on the .com nameservers to point somewhere else and serve up a fake facebook.com domain, but... 1) those NS records have a 6 hour TTL, so it would take a while be effective, and 2) who has the authority to do that?
- junon 5y agoI would assume DNS providers were on call with FB staff to manually trigger flushes across the system to prop the records ASAP. Of course this doesn't affect client TTLs but resolution failures generally aren't cached anyway.
- yourad_io 5y agoSpeaking of flushing, today I learned that Google public DNS has an open "flush" function: https://dns.google.com/cache https://dns.google.com/cache
- celsoazevedo 5y agoCloudflare: https://1.1.1.1/purge-cache/ https://1.1.1.1/purge-cache/ OpenDNS: https://cachecheck.opendns.com/ https://cachecheck.opendns.com/
- hamilyon2 5y agoDns providers are basically every ISP in existence, it would be impractical to communicate with by phone calls
- DaiPlusPlus 5y ago> those NS records have a 6 hour TTL Why on earth would any system need a TTL beyond 1 hour? The longer the TTL the longer your outage period will be if a cache is poisoned.