Re:Chrome connects to three random domains at startup
by kmm on Saturday February 18, 2012 @03:20PM
(#3607636)
I don't understand. Why would your ISP block your IP for bogus DNS requests? And why are they monitoring your traffic to public DNS servers? I presume this means they have to look at all traffic that goes over port 53. Is there a security concern?
Re:Chrome connects to three random domains at startup
by brandon on Saturday February 18, 2012 @09:59PM
(#3608504)
This is common practice if the queries appear to be originating from worms like Conficker, etc. Others have reported that this behavior of Chrome's can set off false IDS alarms for the same reason.
Re:Chrome connects to three random domains at startup
by windsurfer on Sunday February 19, 2012 @01:36AM
(#3608807)
And it's also common practice to send all bad DNS queries to an ad-ridden search page. Go figure.
Re:Chrome connects to three random domains at startup
by cydonian_monk on Saturday February 18, 2012 @03:54PM
(#3607723)
I have no idea why they would want to block it, unless they considered it an attack vector for some reason. It was automatic - after a few of the bogus DNS requests, all DNS/port 53 traffic was dropped. Everything else worked, only DNS failed.
Re:Chrome connects to three random domains at startup
by ohashi on Saturday February 18, 2012 @03:36PM
(#3607675)
Can you name the ISP?
Re:Chrome connects to three random domains at startup
by cydonian_monk on Saturday February 18, 2012 @04:03PM
(#3607751)
It was originally SBC DSL (resold Yahoo!, resold etc...). The Chrome-induced resolution failures weren't the only issue - their primary DNS server never worked, always went to the failover.
Things didn't improve under AT&T.
Re:Chrome connects to three random domains at startup
by joelhaasnoot on Saturday February 18, 2012 @04:31PM
(#3607808)
Time for 8.8.8.8?
Re:Chrome connects to three random domains at startup
by sobbybutter on Sunday February 19, 2012 @12:54PM
(#3609833)
I put in a vote for the easyDNS public DNS service (205.210.42.205 and 64.68.200.20). No NXDOMAIN monkeying or anything of that nature.
Re:Chrome connects to three random domains at startup
by moreorless on Saturday February 18, 2012 @07:29PM
(#3608198)
I would rather go with 208.67.222.222 and 208.67.220.220 from http://opendns.com
Re:Chrome connects to three random domains at startup
by Dylan16807 on Saturday February 18, 2012 @08:42PM
(#3608343)
But opendns is one of the servers that gives you bogus results instead of NXDOMAIN.
Re:Chrome connects to three random domains at startup
by RexRollman on Saturday February 18, 2012 @09:35PM
(#3608460)
Really?? That's disappointing to hear.
Re:Chrome connects to three random domains at startup
by getsat on Sunday February 19, 2012 @02:31AM
(#3608876)
It's their primary monetisation vector from what I can see.
Re:Chrome connects to three random domains at startup
by sp332 on Sunday February 19, 2012 @10:09AM
(#3609482)
By default, the free service that anyone can use, they redirect nonexistent domains to a search page they control. If you pay (and register your IP address), you can turn that off. But the main reason for paying is to control which domains are blocked. You can choose categories, and/or maintain your own white or black list. http://www.opendns.com/web-filtering/ and http://www.opendns.com/internet-security/
Re:Chrome connects to three random domains at startup
by joelhaasnoot on Tuesday February 21, 2012 @03:06PM
(#3617857)
You can also filter without paying, including black or whitelisting domains. Works effectively to curb reddit addictions.
The easy solution was to stop using Chrome. The hard solution was to move. I've done both, but have yet to start using Chrome again.