Cloudflare produces wrong A record and is pointing to a wrong IP address

dash-dns
dash-crypto
#1

Hi, I am maintaining www.freischem.eu and it worked beautifully with Cloudflare until yesterday. I want the A record to point to 81.173.194.3. And I have entered this into the DNS settings in the Cloudflare control panel. However, Cloudflare now decided to point the A record to 104.27.141.175
(with a ttl 300). This other IP address is NOT entered into the DNS panel. Now the website is not reachable and the original hosting company is displaying a “coming soon” default webpage. What can I do?

Rolf Claessen

#2
1 Like
#4

Cloudflare sits in front of your Site.
The error you mention could be relate the way your server handles SSL connections.
Have you solved your issue?

1 Like
#5

This answer did not help

#6

The answer explains how it works. They point your server to a CF-owned IP address so CF can work it’s magic.

https://community.cloudflare.com/search?q=Future%20home%20of%20something

#7

I see the site fine BUT, the domain has not fully propagated which can take up to 24 hours (rarely the case… :wink: )

clark.ns.cloudflare.com
cortney.ns.cloudflare.com
dns14.netcologne.de
dns11.netcologne.de
dns13.netcologne.de
dns12.netcologne.de

and

clark.ns.cloudflare.com
cortney.ns.cloudflare.com

and

dns11.netcologne.de
dns13.netcologne.de
dns12.netcologne.de
cortney.ns.cloudflare.com
clark.ns.cloudflare.com
dns14.netcologne.de

The number one thing to avoid is switching nameservers back and forth as the rest of the internet needs to catch up or things may never work.

#8

In which way did it not help? Did you read the article at all? You need to understand what Cloudflare is and how it works, after which you’ll be able to answer your question yourself.

#9

Hi,
I 'm just makeing baby steps in creating my own page.
I encountered this same problem and just wated to make sure if i understand correctly that cloudflare just needs some time for the DNS records i changed to take effect.(i changed tham about 12 hours ago to point to my new host).

#10

It is not a propagation issue. Please refer to the articles posted in this thread.

#11

Ok, i 've read this article. I understand ± how it works, but still it doesn 't answer this problem, what should i do - somhow flush the cloudflare cache? The nameservers point to cloudflare at my domain provider, than i changed the DNS records at cloudflare to my hosts provided A racord.
I can 't find the 104.27.x.x IP adress nowhere at any record either at my domain provider nor at cloudflare. It won 't give me anything to understand how it works - i need to know how to resolve it.

EDIT:
Judge - kinda thanks - i found an answer to my problem by your link
BUT!
It would REALLY help if someone just answered:
“It probably is a problem with your host not recognizeing protocols - try turning SSL to flexible or off, installing plugins and than turning it on again” or something like that… sheesh…

#12

No offence, but then you wouldnt continue asking that question.

As I said, that is not a propagation issue, so you can flush caches all day long and it wont change anything.

As long as you proxy you will always have that IP address. Again, please read the linked article and support.cloudflare.com in general, as well as the tutorial section here on the forum.

1 Like
#13

No offence, but reading the article wouldn’t produce me an answer all day. i needed help with an issue which i coulden 't get a straight forward answer to, so telling me to “read how it works” didn 't give me squat. i’m not a programmer nor a web designer or such but as i said i’m takeing baby steps. Judges post pointed me in the right direction - not a straight answer but still a million times more accurate than your vague suggestion. How the hell would i get an answer from this articule…

#14

From that very link

Before Cloudflare, that address would have been 198.51.100.1. With Cloudflare as the authoritative nameserver, the new address is 203.0.113.1. Cloudflare’s data center at 203.0.113.1 will serve as much of your website as it can from its local storage, and ask your web server at 198.51.100.1 for any part of your website it doesn’t already have stored locally. The Cloudflare data center at 203.0.113.1 will then provide your complete website to the visitor, so the visitor never talks directly to your web server at 198.51.100.1.

I understand that you might not be a programmer or a web designer, but that does not mean that you should not familiarise yourself with these topics and learn more about them, which typically starts by reading the documentation.

Cloudflare provides quite a good and extensive documentation at support.cloudflare.com and in this case you were even pointed to the right article straight away. Snarky remarks are hardly in order in this case.

#15

And as “experianced” as I am it leads me to belive i should somehow be able to flush the cache on the data center becouse i provided the “your web server at x.x.x.x IP” and maybe the problem is that the “stored localy data” is somehow in confict with the actual data on my new host OR there is a kind of a firewall in the way - i eliminated these two options and proceed to ask a question, and for ones ONES i would like a simple answer like i found in here: Community Tip - Best Practices For Dealing With "Future Home of Something".
I didn’t get this message i got something else and the problem was decribed perfectly in this topic right here, but this article didn 't give me a streight answer nor even a close one. Frankly i understand every problem is different but telling me to familiarize with all of cloudflares extended documentation is dicouriging. I would hope that if this is a support forum someone should be willing to work to at least get to the root of the problem not just writing “go look for the answer in the docs” it’s just like writeing “go google it and f off”.
Sorry for the rant but i’m kinda ticked off because every step of the way everything is sooooo easy on paper and whan I actually do it it generates problems like this.

#16

Well, the support community obviously is there to provide community support, however it cannot be in the interest of the community to have to rehash the same basic questions over and over again, and I am afraid the question “why a different IP than your server’s shows” falls into that very category.

For this very purpose companies create knowledge bases and support articles. Also, the forum does provide a search which is unfortunately way underutilised anyhow. I understand that things can be confusing and overwhelming and IT administration is not the most straightforward topic but I am afraid this is the exact point where documentation and articles come in.

I should also point out “Part 3” of Setting up your website with Cloudflare - Full tutorial

1 Like
closed #17

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