20k Unexpected DNS Queries / Day - Expectations and Cost Avoidance

0

Hi AWS folks - I'm new to AWS. I recently registered a domain name with Route 53. Since the registration, I've received around 20,000 DNS queries / days, which has resulted in around $0.02 in charges. Obviously, this is a small amount; but, I want to manage my own expectations here. Is this normal and simply the cost of doing business (having a public domain name)? Or is this unexpected and there's a simple fix that's worth implementing? I do not have or intend to have a public website. I simply registered the domain name so I could use it to configure an API Gateway REST API. Thanks in advance for any help!

질문됨 4달 전177회 조회
2개 답변
1

You can create DNS records with longer TTL to increase caching and reduce queries.

To protect your hosted zone from NXDOMAIN DDoS attacks, you can refer to Configuring Route 53 for cost protection from NXDOMAIN attacks

AWS
전문가
Mike_L
답변함 4달 전
  • This help, but for me there is a one options which will be more helpfully for everyone, "ALIAS to null" or similar option which for specific subdomain will just reply with NXDOMAIN permanently, because now normal NXDOMAIN reply is PAID reply and NXDOMAIN also has smaller TTL forced by other DNS server, even if we setup high one, it's down to smaller one by public DNS resolvers for example... ;-(

0

Hello.

In my environment, even when DNS records are not linked to a service, about 5,000 queries occur per month, so I think it is normal to have about 20,000 queries when linked to API Gateway etc.

profile picture
전문가
답변함 4달 전
profile pictureAWS
전문가
검토됨 4달 전
  • Hi, agree with Riku: when a domain name gets public, you'll have multiple requests from other DNS servers in the world to create / refresh their cache about your domain info. To slightly reduce those requests, you can increase the allowed caching duration of your records.

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠