Hi, I’m utilizing Twingate for secure access to my network resources hosted on AWS. I’ve run into an issue with DNS resolution of SRV records when connected through Twingate.
Issue Summary
When I attempt to use the dig command to query SRV records, it fails with a timeout error:
dig my-resource.sensitive-domain srv
;; connection timed out; no servers could be reached
However, if I specify a particular DNS server in the query, it works:
dig @172.31.0.2 my-resource.sensitive-domain srv
Furthermore, when I’m directly connected to the Twingate Connector without the Twingate Client, the SRV records resolve correctly.
For comparison, A record queries work properly without specifying the DNS server:
dig my-resource.sensitive-domain
;; ANSWER SECTION:
my-resource.sensitive-domain. 15 IN A 100.98.107.240
Request for Assistance
*I would appreciate guidance on how to configure Twingate so that DNS queries for SRV records are resolved correctly through the Twingate Client, without the need to specify the DNS server manually.
We do our best to monitor the forums and answer in a timely manner, so I apologize for the delay.
Would you please email me at arthur (at) twingate.com - the output of the following commands from both your Twingate client machine as well as the box the Connector is running on:
