[beacon] dns connection error The file name is too long.

[rayaar]

Describe the bug
I have tried setting up sliver for DNS beacons for a project I am working on. I have installed the server, and it works great with HTTP(s) listener. But trying to set up a DNS beacon i get [beacon] dns connection error The file name is too long.. I checked the sliver server logs and no indication that it actually receives any DNS requests. this is also verified using wireshark.

To Reproduce
Steps to reproduce the behavior:

1. Open sliver
2. generate implant generate beacon -G -l --dns test.test.com --debug
3. download and run the file
4. See error (changed the domain name for privacy)

PS C:\Users\user\Downloads> .\IMPRESSED_MEZZANINE.exe
2023/09/20 21:30:39 sliver.go:97: Hello my name is IMPRESSED_MEZZANINE
2023/09/20 21:30:39 limits.go:58: Limit checks completed
2023/09/20 21:30:39 sliver.go:114: Running in Beacon mode with ID: 4463d856-b2f1-458b-9679-af01b45030e4
2023/09/20 21:30:39 beacon.go:102: Starting beacon loop ...
2023/09/20 21:30:39 transports.go:41: Starting c2 url generator () ...
2023/09/20 21:30:39 transports.go:104: Return generator: (chan *url.URL)(0xc00007c7e0)
2023/09/20 21:30:39 beacon.go:118: Recv from c2 generator ...
2023/09/20 21:30:39 transports.go:92: Yield c2 uri = 'dns://test.test.com'
2023/09/20 21:30:39 transports.go:92: Yield c2 uri = 'dns://test.test.com'
2023/09/20 21:30:39 beacon.go:122: Next CC = dns://test.test.com
2023/09/20 21:30:39 beacon.go:122: Next CC = dns://test.test.com
2023/09/20 21:30:39 transports.go:92: Yield c2 uri = 'dns://test.test.com'
2023/09/20 21:30:39 sliver.go:123: Next beacon = &{0xce1f60 0xce5f80 0xce1e20 0xce1ea0 0xce5fc0 0xce1dc0 dns://test.test.com }
2023/09/20 21:30:39 dnsclient.go:152: DNS client connecting to 'test.test.com' (timeout: 5s) ...
2023/09/20 21:30:39 beacon.go:177: [beacon] dns connection error The file name is too long.
2023/09/20 21:30:39 sliver.go:150: Beacon init error: The file name is too long.
2023/09/20 21:30:39 sliver.go:136: Reconnect sleep: 1m0s
2023/09/20 21:31:39 sliver.go:123: Next beacon = &{0xce1f60 0xce5f80 0xce1e20 0xce1ea0 0xce5fc0 0xce1dc0 dns://test.test.com }
2023/09/20 21:31:39 beacon.go:122: Next CC = dns://test.test.com
2023/09/20 21:31:39 transports.go:92: Yield c2 uri = 'dns://test.test.com'
2023/09/20 21:31:39 dnsclient.go:152: DNS client connecting to 'test.test.com' (timeout: 5s) ...
2023/09/20 21:31:39 beacon.go:177: [beacon] dns connection error The file name is too long.
2023/09/20 21:31:39 sliver.go:150: Beacon init error: The file name is too long.
2023/09/20 21:31:39 sliver.go:136: Reconnect sleep: 1m0s

I have tried on 3 different servers and using 3 different domains, all with the same issue. I dont think the DNS setup is the issue as it never actually send any dns requests.

[michelbf]

Having the same issue. Any resolutions?