Changed A-record but still points to the old server

#1

I’m struggling. I just added one my client’s website on Cloudflare and a simple NS check shows that it has worked. I changed the A-record to put the new server we’re migrating to.

Unfortunately, the website still points to the previous server IP.

The TTL should be of 5 minutes max if i’m not mistaken, but it has been 2 hours and no change.

To test, I put the status to “DNS only” on the A record, and it actually did work (but I can’t choose that possibility cause I need the Cloudflare SSL certificate). So something wrong is happening on Cloudflare’s side.

It seems the old server IP is still there as a ghost and Cloudflare hasn’t deleted it.

Please help :slight_smile:

#2

How exactly without a domain?

#3

Ha indeed. Domain’s « chezcameil.com ». I just tested it and it shows the good server on Pingdom and Gtmetrix, so could it be just slow propagation? I thought A record propagation was fast.

#4

Considering that it is proxied there is not even propagation involved, so a record change should be almost instantaneous.

#5

So how is it possible majority of tests show the new server, but some show the old?

#6

Both, your naked domain and your www record, are proxied. How do you determine that it “shows” different servers?

#7

Because when I browse on it, even with all Dns and cache flushed, I see the old website, while some tools show me the new one. Any ideas?

#8

Is it the main page of your domain or a particular host?

#9

Main page. It has to be cache since I see it correctly on some other computers and phones…

Envoyé de mon iPhone

#10

Main page looks like this

image
image.jpg1270x613 266 KB

You do have a mixed content issue on HTTPS though.

#11

It sometimes looks like this (new website) for me too, but sometimes I see the old site, as if it was load balancing between the old and the new server. This is so weird…

#12

That does seem like a cachine issue, whether that is local or somewhere inbetween is difficult to tell. Do you have the issue with different browsers?

#13

Yes we do. And also same browser, balancing between the two websites.

#14

It it still happening, some users tell me they see the old server and some tell me they see the new one…