"can't use event page any more" -> issue 447270 aims to change this.

"Many extensions need to access the ip address corresponding to the current tab's url." - what are the use cases, and why is it absolutely necessary to have an API that lists the IP addresses in the current tab? I don't think that the list of IP addresses is separately stored per tab.

And you're mixing tab and tab URL. Which of the two do you mean? I think that it is meaningless to offer the "IP addresses in the tab", but somehow getting access to the (cached) DNS results (e.g. as visible in chrome://net-internals/#dns ) might be useful. But again, that is not specific to a tab.

Sorry for the confusion, every time i said "tab", i meant "tab URL".

Good to hear there is #447270, but it still doesn't solve #3.

A cached DNS resolver is a good idea. I think Firefox has that.

We already provide the chrome.tabs API that can get you the URLs of all tabs and fires events when they change, so the remaining thing needed is a DNS resolving API. It turns out we implemented an experimental one but never launched it to stable; instead it's experimental and only available on chrome dev/canary channels. So I'm changing the title of this bug to be "Take the DNS API out of experimental", with the expectation that there may or may not be changes required to the API to get it into a form we'd be happy releasing and supporting. 

I can't recall what the remaining issues were preventing us from launching it - IIRC we first implemented it because the (apps-only) chrome.sockets API initially only supported ip addresses, so you needed a way to do DNS resolution, but we changed the sockets API to take hostnames as well as ip addresses. We may have not launched it just due to relatively low amounts developer interest. 

Anyhow, the current experimental implementation is mostly in these files:

extensions/common/api/dns.idl
extensions/browser/api/dns/dns_api.h
extensions/browser/api/dns/dns_api.cc

in case someone wants to try and take on launching this API to stable. 

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Assigning to Devlin. Devlin: What's the status of this API? It seems it is enabled just on Dev but whitelisted on Stable for something called CCD.