Open Bug 728670 Opened 9 years ago Updated 2 years ago

Detect DNS hijack redirection, and allow users to block it

Categories

(Core :: Networking, enhancement, P5)

enhancement

Tracking

()

People

(Reporter: dindog, Unassigned)

References

Details

(Whiteboard: [lame-network][necko-would-take])

My ISP DNS will redirect me to a page full of ADs when wrong domain query was requested.
For speed concern, I have to stick with them instead of using OpenDNS or Google's DNS.

Chrome won't. And it achieves that very simple: raises some non-exist domain request in background when Chrome starts, then record the DNS reaction.( mostly 302 redirect) Next time it meets that, block it.

Would love to see this on Firefox too.
Source:

Chrome Connecting To Random Domains On Start? Here Is Why!
http://www.ghacks.net/2012/02/18/chrome-connecting-to-random-domains-on-start-here-is-why/
Component: Untriaged → Networking
Product: Firefox → Core
QA Contact: untriaged → networking
this is a reasonable feature for the lame-network project, although it has arms-race written all over it.

some philosophical overlap with captive portal detection too.
Whiteboard: [lame-network]
Note that Chrome's behavior causes serious problems on some networks because it looks exactly like a botnet node looking for a command&control node....
Summary: Detect DNS hijack rediection, and allow users block it → Detect DNS hijack redirection, and allow users block it
Whiteboard: [lame-network] → [lame-network][triage]
See Also: → 878566
Blocks: useragent
Is DNS hijacking also what public wi-fi providers (such as The Cloud) use to redirect all URLs to their websites until you log in?  This is something to consider if we're going to implement such a feature.
Flags: needinfo?
Summary: Detect DNS hijack redirection, and allow users block it → Detect DNS hijack redirection, and allow users to block it
Depends on the implementation - could be a transparent HTTP proxy, too -, but I think generally yes.
Flags: needinfo?
I just wanted to CC myself, but it looks like I canceled a needinfo. It wasn't my intention, though. I don't know who it was directed to, so I don't know how to set it back.
Apologies for this issue beyond my control.
That must be a bugzilla bug. I removed the needinfo in my comment 5.
Whiteboard: [lame-network][triage] → [lame-network]
Whiteboard: [lame-network] → [lame-network] p=0
No longer blocks: fxdesktopbacklog
Whiteboard: [lame-network] p=0 → [lame-network]
Flags: firefox-backlog-
Whiteboard: [lame-network] → [lame-network][necko-would-take]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
See Also: → 1333191
You need to log in before you can comment on or make changes to this bug.