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

One subdomain not working

0

Hi Guys,

I have one subdomain that's not resolving in Route 53. The other subdomains work but this one simply refuses to resolve. I added it as an A-Record and even tried it as a CNAME pointing to an ec2. But frustratingly won't resolve. The NS records are fine, there an SOA, an A and a CNAME. Any ideas?

Thank you

  • Chris_G EXPERT
    4 years ago

    How are you testing whether it resolves? Have you tried running dig +trace yoursub.domain.com? Possibly it could be stuck in cache?

  • WDG
    4 years ago

    Not to piggyback but don't want to spam the list and I think I have the same issue. Multiple A records work (client1, client2, client3), but client4 dot returns a 503 (as opposed to 'site can't be reached').

    All of these resolve to the same page, set up is identical. Edit: Issue was authentication, not set up.

Topics
Networking & Content Delivery
Tags
Amazon Route 53
Language
English
asked 4 years ago395 views
1 Answer
0

Hi this is Abhi from AWS. Can you provide the following details:

a) Hosted Zone Domain name b) Subdomain name c) Records and record types not resolving d) dig +trace <record not resolving> <record type> e) dig <record not resolving< <record type>

We would need this information to start troubleshooting and ultimately resolving this issue

AWS
EXPERT
answered 3 years ago

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.

Relevant content