1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 10 Monaten

How are you testing whether it resolves? Have you tried running dig +trace yoursub.domain.com? Possibly it could be stuck in cache?
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.