Changed A-Record but it points somewhere else

Website, Application, Performance DNS & Network
1

I am working on brilliantlightpower-dot-com. It is properly setup with nameservers going to Cloudflare. I added multiple subdomain records that worked, but when I changed A Record to 72.52.220.81 (from 72.52.220.112). The DNS Checker shows 104.26.1.27!

I changed it back to the old IP and it resolves correctly.

Thank you in advance for any suggestions.

Paul

4

Welcome to the Cloudflare Community. :logodrop:

Of course it does. That is a Cloudflare proxy IP. When your names are set to :orange: proxied DNS will always return Cloudflare proxy IPs.

Take a look at the life of a request in this brief guide. It should demonstrate why you can change your IP and have it stay the same. Your visitors connect to Cloudflare which then connects to your origin server on their behalf.

3 Likes
5

So the answer is to turn off proxied DNS?

6

Certainly you can do that @website27, but understand in doing so you would disable Cloudflare services.

2 Likes
7

The answer is that you will not see the IP change when you perform a public lookup. You will see the change in your Cloudflare dashboard DNS app.

2 Likes
8

First of all… Thank you all for responding.

I am trying to make a staging site on 72.52.220.81 live. But the site wasn’t resolving. For some time this company’s site was dead, so I changed it back to the old server 72.52.220.112. It was fine under proxied for the old, but not for the new.

How do you maintain the proxy - and still have it go to the changed IP address?

9

As soon as you change the IP address in Cloudflare, Cloudflare starts sending requests to the new IP.

What response do you see when you switch to the new IP?

1 Like
10

After changing the IP for the A Record, the site has too many redirects and fails to load.

I am not on the server end. Could there be something on the server end that is preventing the connection through Cloudflare?

11

:point_up_2: Click that link for a longer explanation.

The short version is two steps:

  1. Make sure that Cloudflare SSL/TLS encryption mode is Full (strict)
  2. Use either a valid public certificate or a Cloudflare Origin CA certificate on your origin server
2 Likes
12

Thank you.

2 Likes
13

This has been nerve-racking. I sent the private and public keys to the server administrator. And I have the SSL/TLS set to Full (strict). It was set to Flexible.

I assume he will know what to do with them on the server side.

Thank you again.

2 Likes
14

I changed to DNS only. I added a pem file to the public_html folder with the Origin Certificate text. But the server admin asked me to delete it.

Not sure what needs to be done on the server, but I’ll resolve it later.

Thanks again.
Paul

15

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.