New issue
Advanced search Search tips

Issue 622799 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: 2019-07-09
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

domain with empty AAAA record fails to resolve

Project Member Reported by ellyjo...@chromium.org, Jun 23 2016

Issue description

OS: Mac OS X 10.11.5
Chrome: 53.0.2777.0

An example of this configuration is dl.dropboxusercontent.com:

$ host -t A dl.dropboxusercontent.com
dl.dropboxusercontent.com is an alias for block-www.g1.dropbox.com.
block-www.g1.dropbox.com has address 108.160.173.5

$ host -t AAAA dl.dropboxusercontent.com
dl.dropboxusercontent.com is an alias for block-www.g1.dropbox.com.

Note that the domain *exists*, but there is no actual AAAA record for it.

On OS X, command line tools like dig(1) can resolve this domain without issue, but both Chrome and Safari report NXDOMAIN when trying to navigate to it. Chrome's HOST_RESOLVER_IMPL_JOB looks like this:

31270: HOST_RESOLVER_IMPL_JOB
dl.dropboxusercontent.com
Start Time: 2016-06-23 14:35:11.274

t=166896 [st=0] +HOST_RESOLVER_IMPL_JOB  [dt=2]
                 --> host = "dl.dropboxusercontent.com"
                 --> source_dependency = 31269 (CONNECT_JOB)
t=166896 [st=0]    HOST_RESOLVER_IMPL_JOB_STARTED
t=166896 [st=0]   +HOST_RESOLVER_IMPL_PROC_TASK  [dt=2]
t=166896 [st=0]      HOST_RESOLVER_IMPL_ATTEMPT_STARTED
                     --> attempt_number = 1
t=166896 [st=0]      HOST_RESOLVER_IMPL_JOB_REQUEST_ATTACH
                     --> priority = "HIGHEST"
                     --> source_dependency = 31269 (CONNECT_JOB)
t=166898 [st=2]      HOST_RESOLVER_IMPL_ATTEMPT_FINISHED
                     --> attempt_number = 1
                     --> net_error = -105 (ERR_NAME_NOT_RESOLVED)
                     --> os_error = 8
                     --> os_error_string = "nodename nor servname provided, or not known"
t=166898 [st=2]   -HOST_RESOLVER_IMPL_PROC_TASK
                   --> net_error = -105 (ERR_NAME_NOT_RESOLVED)
                   --> os_error = 8
                   --> os_error_string = "nodename nor servname provided, or not known"
t=166898 [st=2] -HOST_RESOLVER_IMPL_JOB
                 --> net_error = -105 (ERR_NAME_NOT_RESOLVED)

This suggests that the system resolver is returning EAI_NONAME ("hostname nor servname provided, or not known") instead of EAI_NODATA ("no address associated with hostname") in this situation.
 
This may be the root cause of  bug 291198 .

I'd like to experiment with falling back to explicitly asking the OS for IPv4 addresses if asking for IPv4 and IPv6 returned EAI_NONAME, and then seeing how often that results in an eventual success.
Owner: ----
Labels: Pri-3
NextAction: 2019-07-09
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.
Status: Untriaged (was: Assigned)
Assigned, but no owner or component? Please find a component and/or owner
Components: Internals>Network>DNS

Sign in to add a comment