Update DNS, but resolve old IP

[vohoangtri]

Hi,

I migrate my host from a2hosting to AWS. I updated my domain tapchiamnhac.net but it still resolves to the old a2hosting:

1. From Cpanel of A2Hosting, remove Cloudflare dns.
2. Check site is removed from Cloudflare: OK
3. Create a new site and point to the Elastic IP of EC2 instance: “active”

Type A tapchiamnhac.net points to 54.179.139.61

4. ping still resolves to the old hosting:

PING tapchiamnhac.net (103.227.176.14) 56(84) bytes of data.
64 bytes from sgss4.a2hosting.com (103.227.176.14): icmp_seq=1 ttl=54 time=378 ms

Why?

[cs-cf]

You should flush your local DNS cache. That host resolves to Cloudflare IPs for me.

[vohoangtri]

Hi @cs-cf,

can you ping tapchiamnhac.net?

as you see above, my ping goes to “sgss4.a2hosting.com”

Thanks

[cs-cf]

As I said, it resolves to a Cloudflare IP for me.

ping tapchiamnhac.net
PING tapchiamnhac.net (104.18.52.209): 56 data bytes

AS      | IP               | AS Name

13335 | 104.18.52.209 | CloudflareNET - Cloudflare, Inc., US

[vohoangtri]

@cs-cf thank you!

1. do you know if we can set the nameservers of AWS (AWS Route 53) instead of forwarding IP (Type A).
2. And is it better to do so?

[cs-cf]

@vohoangtri

• do you know if we can set the nameservers of AWS (AWS Route 53) instead of forwarding IP (Type A).

It’s not possible to redelgate your root record NS when Cloudflare is serving as your DNS.

• And is it better to do so?

Generally no. It involves more DNS lookups and there isn’t any additional value to doing it that I see in this scenario.