News for hackers. Stuff that matters.
Re:Google Chrome and (weird) DNS requests by kragen on Wednesday January 26, 2011 @03:11PM (#2144909)
Wildcard domains (*.bloggo.com) aren't nasty. Wildcard DNS servers are. They inject domain name data into zones owned by other entities; if you type news.ycombinator.com, you get this server, but nwes.ycombinator.com gives me a JS redirect to www.ayudaenlabusqueda.com.ar/?query=nwes.
Re:Google Chrome and (weird) DNS requests by uxp on Wednesday January 26, 2011 @03:36PM (#2145022)
This is what I gathered from the article, that it is looking for evidence of malware injecting itself between your browser and the DNS lookup, or poorly configured DNS servers doing similar.

On a similar thread, Googlebot will often request a page that it can safely assume will 404, like example.com/noexist_d6956f303b25361a.html, just to make sure that non existant pages actually return a 404 instead of a 301 to a page with dynamically generated content based on the request name.

Re:Google Chrome and (weird) DNS requests by Luyt on Wednesday January 26, 2011 @03:19PM (#2144945)
This is interesting news. My use case is indeed having many subdomains together with a wildcard DNS like '*.somesite.com', and I'm not designing some nefarious plot to redirect 'notexistant.somesite.com' to an ad-serving site. Instead, a page saying 'this subdomain can't be found', together with a registration form, would be shown.

(Speculation mode on) Would Google penalize this setup with a lower Pagerank?