General Discussion
Related: Editorials & Other Articles, Issue Forums, Alliance Forums, Region ForumsWashingtonpost.com appears to be down. Any others out?
Might be standard snafu, but I smell a big fat commie rat.
https://www.washingtonpost.com/
C_U_L8R
(44,997 posts)longship
(40,416 posts)And I don't care if this post hare-lips everybody on Bear Creek.
Foggyhill
(1,060 posts)Or the like
If someone knows the sites IP address they could verify if it's the DNS that is affected
regnaD kciN
(26,044 posts)Foggyhill
(1,060 posts)Attention to the news so that would be pretty dumb
milestogo
(16,829 posts)Foggyhill
(1,060 posts)If they are attacking the DNS, you would get this kind of spotty failure especially ibecausr there local caching of DNS dada
marybourg
(12,611 posts)Foggyhill
(1,060 posts)Just either a major path to it
Or DNS servers had a denial of service attaclk like what happened last week
marybourg
(12,611 posts)Foggyhill
(1,060 posts)But it's the web browsers that are looking up its name that could not get its ip address
If you had this IP address already, having it in a ststic file or a local DNS server that caches this data, you could still use the site
That's why DNS failures are not seen universally the same way by everyone
sarcasmo
(23,968 posts)Tactical Peek
(1,208 posts)And I can reach it now through the non-mobile link.
Funny that their page 1 story is about the Russians meddling in the election.
FreeStateDemocrat
(2,654 posts)This site cant be reached
www.washingtonpost.coms server DNS address could not be found.