All Content tagged with Route 53 Private DNS
Private DNS is a Route 53 feature that lets you have authoritative DNS within your VPCs without exposing your DNS records (including the name of the resource and its IP address(es) to the Internet.
Content language: English
Filter content
Select tags to filter
Sort by
Sort by most recent
50 results
**Route 53 UPDATE_NAMESERVER operation stuck IN_PROGRESS for weeks — cannot submit new nameserver update**
I have a domain (`domain.com`) registered via Route 53, and a nameserver update operation ha...
We need to create a private hosted zone for a parent domain (e.g. `example.com`) in a consumer's VPC. However, there is an existing public subdomain record (`apigateway.example.com`) that must continu...
We have a public hosted zone with an A record at `apigateway.example.com` pointing to an API Gateway custom domain. We need to create a private hosted zone for the parent domain `example.com` in our V...
I'm running AWS SageMaker Processing jobs inside a VPC, and I want these jobs to resolve internal service names (e.g., internal.api.corp) using custom DNS rules. My VPC is configured with Route 53 Res...
asked 10 months ago
Hello
I have Route53 Profile shared from my networkHub account with other accounts in my Organization. There is Private Hosted zone associated with Route53 profile on NetworkHub account.
However when...
Hello,
I am trying to do a private integration between API GW in Account A and Route53 private route in Account B. I am using API Gateway REST API and this cannot be changed.
My target flow should loo...
asked a year ago
Hello community,
I would like to know how DNS Firewall billing works. I am planning to use this feature, but I am a bit worried about the cost since my idea is to use DNS Firewall to filter certain ty...
Upgraded to AWS VPN Client v5.0.0, and SSH connections to some EC2 instances stopped responding totally.
It seems that these non-accessible instances are the ones with Public Elastic IP's. Trying to...
I am experiencing issues with domain connectivity for both www.***.net and ***.net. Despite setting up the DNS records in Route 53 correctly, the domains are not resolving, and an NXDOMAIN error is di...
We migrated lymanwealth.com to Amazon AWS and the DNS records are all setup, but its been over a week now and many places (specifically xfinity) still cannot see the DNS records. If I check nslookup....
We are running into a problem where SOMETIMES our users connect to the VPN and all webpages fail to load. I can confirm this is a DNS problem. As soon as we change the DNS on the network adapter, it w...
I have multi account on AWS and in each account I have custom VPC connected through Transit Gateway and all of them talk to Azure environment through Site to Site VPN . I created EC2 instance in each ...