Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net: TestLookupCNAME sometimes failing on Plan 9 #21335

0intro opened this issue Aug 7, 2017 · 1 comment


None yet
2 participants
Copy link

commented Aug 7, 2017

Sometimes, TestLookupCNAME is failing on Plan 9.

--- FAIL: TestLookupCNAME (0.24s)
	lookup_test.go:266: write /net/dns: dns: resource does not exist; negrcode 0
FAIL	net	19.087s

Indeed, resolving an nonexistent CNAME can result in either the "dns failure" or the "resource does not exist" error. This behavior can be reproduced with ndb/dnsquery:

cpu% ndb/dnsquery
> cname cname
> cname cname
> cname
!dns: dns failure
> cname
!dns: dns failure
> cname
!dns: dns failure
> ip
> cname
!dns: resource does not exist; negrcode 0
> cname
!dns: resource does not exist; negrcode 0

This is related to (closed) issue #18391.

@0intro 0intro added the OS-Plan9 label Aug 7, 2017

@0intro 0intro added this to the Go1.10 milestone Aug 7, 2017

@0intro 0intro self-assigned this Aug 7, 2017


This comment has been minimized.

Copy link

commented Aug 8, 2017

Change mentions this issue: net: fix LookupCNAME on Plan 9

@gopherbot gopherbot closed this in bd3dc9d Aug 8, 2017

@golang golang locked and limited conversation to collaborators Aug 8, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.