1 Answer
- Newest
- Most votes
- Most comments
0
This is not an AWS issue but how the Tailscale application works. Depending on your requirement for DNS, you may wish to enable SPLIT DNS in TailScale and set the DNS Server for the EC2 to be the local Route 53 resolved situated on the VPC CIDR+2 IP Address, i.e 172.31.0.2
To implement split DNS using Tailscale:
- Log in to your Tailscale account, then navigate to the DNS page on the admin console. This is where you can configure the split DNS setting for your network.
- On the DNS page, assign a name to your server using the Add Nameserver drop-down menu. From this drop-down, select the Custom option, then input the IPv4 or IPv6 address of the internal DNS server that is to be used to resolve internal queries.
- Finally, toggle the Restrict search domain button, fill the subsequent field with the desired web address name, and save the changes.
Its a known problem in TailScale https://tailscale.com/kb/1235/resolv-conf?q=dns
Another option You can manage DNS for your Tailscale network in at least three ways:
- Using MagicDNS, our automatic DNS feature
- Using the DNS settings page in the admin console
- Using public DNS records
Add a new GLOBAL Name Server in TailScale to be the route53 resolver IP similar to above https://tailscale.com/kb/1054/dns so that when your EC2 connects to the VPN it will use the same as per default
Relevant content
- Accepted Answerasked 9 months ago
- asked 10 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thank you, but my problem isn't internal queries but external domains. I did try the actions you mentioned, I still have the same problem.
Have you added the global name server? The AWS resolver resolves external domains