Solve real business challenges on Google Cloud and run workloads for free. For Slashdot users: Get $300 in free credits to fully explore Google Cloud. Get started for free today.
Twas brillig, and the slithy toves did gyre and gimble in the wabe All mimsy were the borogroves and the mome raths out grabe.
(in High School one of our English assignments was to memorize and recite a poem of our choosing. I chose Hard Mode, and memorized all of The Jabberwocky. For the next stanza I only remember Beware the Jabberwock, my son! The jaws that bite! The claws that catch! and something about a frumulous Bandersnatch. Third stanza starts something like So took he, his vorpal sword in hand and
I had an issue with packet loss a few months ago. I wrote it off as "line noise". But now latency is a huge problem, especially in DNS, where it sticks on resolving hosts. Help?
Take ye your vorpal sword in hand and and find that frumulous Lagbeest. One, two! Through and through!
Or if you're using your ISP's DNS servers, try an alternate set (Google's at 8.8.8.8/8.8.4.4, opendns is 208.67.222.222/208.67.220.220), maybe your ISP's server just sucks. Or set up your own local caching (or recursive, if you don't want to use Google or OpenDNS or your ISPs broken servers) nameserver.
Weirdness on the internet (Score:2)
Twas brillig, and the slithy toves
did gyre and gimble in the wabe
All mimsy were the borogroves
and the mome raths out grabe.
(in High School one of our English assignments was to memorize and recite a poem of our choosing. I chose Hard Mode, and memorized all of The Jabberwocky. For the next stanza I only remember Beware the Jabberwock, my son! The jaws that bite! The claws that catch! and something about a frumulous Bandersnatch. Third stanza starts something like So took he, his vorpal sword in hand and
Re: (Score:1)
I had an issue with packet loss a few months ago. I wrote it off as "line noise". But now latency is a huge problem, especially in DNS, where it sticks on resolving hosts. Help?
Re: (Score:2)
Take ye your vorpal sword in hand and and find that frumulous Lagbeest. One, two! Through and through!
Or if you're using your ISP's DNS servers, try an alternate set (Google's at 8.8.8.8/8.8.4.4, opendns is 208.67.222.222/208.67.220.220), maybe your ISP's server just sucks. Or set up your own local caching (or recursive, if you don't want to use Google or OpenDNS or your ISPs broken servers) nameserver.
moof (Score:1)
"If you experience severe packet loss, see your doctor immediately!" ;)
Where have you been trying to go on ole Al Gore's Information Superhighway?
Re: (Score:2)
Slashdot. My consulting company's timecard. Google. Does not seem to matter where I go. 88% packet loss has been happening most of the day.
Re: (Score:1)
You would have to head to your local Starbucks (or equivalent) to see if your whole neighborhood is suffering.