I'm running a Windows Server 2022 EC2 instance on AWS with a public IP (x.y.a.b) and I've enabled the DNS server on it. I've also set up the security group to allow all traffic from my public IP. I can connect to the instance via RDP with no issues. I've configured my laptop to use the EC2 instance's public IP as its DNS server. While it can resolve public domain names, it fails to resolve an internal domain I set up. After running Wireshark on the EC2 instance, I found that DNS queries aren't reaching the server, although other traffic like ping and RDP is working fine. It looks like AWS is resolving these DNS queries instead of my instance. How can I get the DNS queries to my EC2 instance instead of AWS answering them?
2 Answers
What tool are you using to check your DNS queries? If you're using a web browser, it might be redirecting your DNS requests to its own DNS-over-HTTPS servers rather than respecting your DNS settings. Just a heads up, AWS typically doesn't intercept DNS traffic, so you should be good on that front.
Have you checked if TCP and UDP port 53 are open on your security group? Also, when you run nslookup or dig, what result are you getting? If nslookup for something like google.com works but queries don't hit your DNS server, it looks like AWS is handling DNS resolution instead.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures