- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello.
Are there any NS records set up outside of the host zone created by Route53?
Other possibilities are that the TTL of the record is long and it is taking a long time to be changed.
On the local PC side, there is a possibility that DNS cache, etc. may remain, so please try clearing the cache, etc.
About a week ago, I started a process to move my domain name on route 53 to clouflare to use cloudflare protection. According to the instructions, I replaced the ns records on route 53 with cloudflare server addresses. I waited 2 days but nothing changed. When I used the dig command, I was seeing the aws ns server addresses. Thereupon, I wanted to delete the hosted zone that I created in cloudflare and continue from route 53, but this time my global domain name was not propogate. As a result of my research, I learned that my domain was suspended due to lack of email verification. I activated the domain 2 days ago, but I can't seem to register on any name server other than aws. My domain is in the route 53 registered domain list. My website has been out of service for about 1 week. What should I do? Thank you.
Contenuto pertinente
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Ah yes, I got a bit confused so I was changing the NS record on the hosted zone, but really I also needed to update it on the Route 53 Registrar as well. Thanks.