By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

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!

Topics
Networking & Content Delivery
Tags
Amazon Route 53
Language
English
BedrockBuilder
asked 4 months ago161 views
2 Answers
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
EXPERT
Mike_L
answered 4 months ago
  • Marcin Gondek
    4 months ago

    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
EXPERT
Riku_Kobayashi
answered 4 months ago
profile pictureAWS
EXPERT
Didier_Durand
reviewed 4 months ago
  • Didier_Durand EXPERT
    4 months ago

    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.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content