net: empty DNS answers should fail fast

[iangudger]

With Go 1.11, DNS queries which are responded to with an empty answers section will be tried on all name servers. This was not the case with Go 1.10. This is mostly an issue if one of the name servers is broken and results in a timeout.

This issue was first reported here: #21906 (comment)

I am filing a new issue because this is a regression in Go 1.11 and #21906 was filed prior to Go 1.10.

[iangudger]

This is similar to #25336.

[gopherbot]

Change https://golang.org/cl/133675 mentions this issue: net: treat no answers as NXDOMAIN

[bcmills]

I am filing a new issue because this is a regression in Go 1.11

Should this issue have a backport, then?

[iangudger]

I think backporting the fix would be a good idea.

[bcmills]

@gopherbot, please backport to 1.11: this is a regression of a previously-fixed issue.

[gopherbot]

Backport issue(s) opened: #27537 (for 1.11).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases.

[ssrikant20]

What is the ETA for this issue? This is slowing down DNS responses back to the client causing context deadline to exceed.

[iangudger]

I have been having trouble getting the fix reviewed. Brad is on vacation. Two different people have stated their intent to review it soon, so hopefully the fix will go in next week.

[ssrikant20]

I have been having trouble getting the fix reviewed. Brad is on vacation. Two different people have stated their intent to review it soon, so hopefully the fix will go in next week.

Thank you