"Just FYI everybody, there's been a response from a Google employee [on the user forums page](https://productforums.google.com/d...). It appears that they've concluded that this is purely a DNS poisoning issue and they're encouraging users to switch to Google DNS. [I responded as best I could](https://productforums.google.com/d...) suggesting that it might not be a bad idea to keep investigating. It might be worth it for others to chime in on that thread as well. **EDIT (unrelated but possibly interesting):** Remember how someone -- I forget who -- noticed that the original chrome-navigation-error page, the destination for the redirect, appeared to be attempting to load a Chrome extension? Well, Google is an amazing thing, and I finally figured out that that part of the source code (which you can see [in this pastebin](http://pastebin.com/kR5J29du)) duplicates [part of the network error rendering..."
- Nathan Rein
"I sent an email according to the instructions at the bottom of that page under "Report other AWS abuse." I don't have the technical knowledge to fill out all the data on the full-length abuse form. If anyone knows and could provide guidance, I could give it another shot."
- Nathan Rein
"A few days back I edited my hosts file by adding the line 127.0.0.1 chrome-navigation-error [dot] info When I did that and then ran netstat, I found lots and lots of connections to the chrome-navigation-error domain. Does that mean that the hosts file was directing netstat to *display* connections to or from the local host *as if they were* connections to chrome-navigation-error? When I re-edited the hosts file to say 0.0.0.0 chrome-navigation-error [dot] info those connections vanished. Just curious, really. But it was alarming at the time."
- Nathan Rein
"I used Godaddy's contact form to make a complaint and they told me to complain to the webhost instead. Any ideas about how to file a complaint they'll actually take seriously? [Here's their response](http://imgur.com/lcD2MOw)."
- Nathan Rein
"To be honest, I don't know -- when I run whois queries for the numerical IP addresses that show up repeatedly, I find there are no entries for them. Here, more or less randomly, is a selection of some of the IPs that have been cropping up repeatedly: 165.254.34.209 165.254.34.223 165.254.34.234 165.254.34.247 176.32.98.166 199.16.156.38 205.251.242.54 72.21.215.34 Don't know if that tells you anything useful..."
- Nathan Rein
"If I understand what you're describing, I think I'm very likely seeing the exact same thing on my machine as well. Here's a [screenshot of TCPView](http://imgur.com/xOxEJvE)."
- Nathan Rein
"This is my concern as well. As a home user without any technical background to draw on, I really haven't got a clue what I should be doing to protect myself."
- Nathan Rein
"Being brand-new to Reddit, I can't help wondering (and I know this is off-topic), why are there 11 downvotes on this thread? Why would someone vote this down?"
- Nathan Rein
"Yeah, it's been a while since I've used it on this machine. Maybe it's just slower than I remember. This is a newly created empty profile though, no extensions or anything. What I really wonder about, and have no way of assessing, are all these entries in netstat of the form: TCP 127.0.0.1:49718 [my machine name]:49719 ESTABLISHED 5304 (that last number is a process ID) Are those normal? What does it mean? There are dozens of them."
- Nathan Rein
"Hi all ... couple of things I wanted to add, then I sort of have to try and get back to my real life, as much as possible. Keep in mind that these are coming from someone with little to no technical comprehension of the issues involved. * I went back through my Chrome history and found the Myspace video link that has been mentioned previously. [Here is a screenshot](http://imgur.com/daO7uI5). It was accessed during a time when the computer was unattended and locked (at about 2 a.m., when no one had touched the machine for at least four hours previously). * I also edited the hosts file as mentioned previously, to add a line as follows: >127.0.0.1 chrome-navigation-error.info * What happened after that was that every time I hit netstat, I saw a huge number of connections to that URL. I then edited the hosts file again to read: >0.0.0.0 chrome-navigation-error.info * Since then, I haven't seen any more connections to that URL. However, I am still seeing tons and tons of connections from..."
- Nathan Rein
"There is now a post up on the Chrome user forum. There are also three Twitter users reporting the issue: @AustinSJones , @CreativeDojo , and @rhythmofself (plus me, @nbr ). https://productforums.google.com/forum..."
- Nathan Rein
"I just saw this behavior on a PC (Windows 7, work-issued, with Chrome 32) about two hours ago. I know enough to have spotted the URL and to know it's fishy, but I don't know enough to understand how DNS works or how to interpret the source code that ocdude posted to the pastebin. I'm in the eastern US (near Philadelphia) and I'm on Verizon as well. I have my router set to use OpenDNS. I am currently also connected through my employer's VPN. Any suggestions about what I should do next to protect myself would be welcome... I'm completely mystified. Glad I found this thread, and thanks everybody."
- Nathan Rein
"I'd be interested to know how the actual numbers compare to the classic high-achieving stereotype of Asian kids, and particularly how it breaks down more granularly (e.g., families of Chinese, Korean, or Southeast Asian origin, etc.). I went to a school where there was a large Asian population, most of whom were children of Vietnamese and Cambodian refugee families. Locally they were NOT stereotyped as academic high achievers -- but rather as dangerous gangsters. But that was a long time ago ..."
- Nathan Rein
"Tried the brisket and the ribs. I'm not really a connoisseur of barbequed ribs, but I thought these were delicious. The level of smoke was just right for me, and the meat was very tender and full of…"
- Nathan Rein
"Well, then you're not really talking about the charge of cultural appropriation; you're saying there's something fundamentally wrong with the legal idea of trademarks that use common words. It doesn't really have anything to do with the fact that it's "culturally embedded," as you said above -- it's just the fact that it's a common word. But that's how our trademark law works -- you can, in fact, trademark common words. If you think that ought to change, that's a whole other issue, but it's not Dogfish's fault."
- Nathan Rein
"Why? There are trademarks on "Hello," on "Zen," on "Moses," on "Apple" .... I mean, hell, UPS has a trademark on the color brown. How is this any more ridiculous?"
- Nathan Rein
"I'm not trying to be obstreperous, but libel is a crime, right? So aren't you publicly alleging that the Daily Record violated the law? Honestly, I'm asking out of curiosity. I don't know how the law works in these situations. Presumably, if a newspaper published an article with the headline that, say, "George Conger embezzles funds from Patheos" and it turned out not to be true, wouldn't the paper be exposing itself to criminal liability (for libelling you), even if they claimed it were merely an opinion and not malicious in intent?"
- Nathan Rein