The response you’re getting back indicates that Twingate is not actively intercepting the lookup request, as that IP is the public IP for that particular hostname/resource.
I am unsure which user account is yours in the tenant so I can’t confirm security group assignments and such, but are you certain you have appropriate/equivalent access to the resource in question?
Can you DM me the full output of twingate resources
From private conversation it turned out that twingate sets up local DNS server which overrides all other DNS configurations basically intercepting all of the DNS queries. This solution was never intended for setups where local DNS server is used, since twingated tries to listen on 53 port, and it is not configurable.
I’ve disabled local DNS server and twingate was able to setup properly. However, I do not consider it a solution since
I need this local resolver, since I am using not only twingate. I am connecting to multiple VPNs from time to time and this is requirement of my job, so I don’t want to change my DNS configurations every time I connect to different VPN.
I do not feel comfortable when a closed-source program collects and reports all of my DNS queries.
I think that there can be a better solution where I could just use my local DNS server to redirect resource-specific queries to twingated, just on different port. But it is not configurable