<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Cloudflare Archive - Pixelfriedhof</title>
	<atom:link href="https://pixelfriedhof.com/en/tag/cloudflare-en/feed/" rel="self" type="application/rss+xml" />
	<link>https://pixelfriedhof.com/en/tag/cloudflare-en/</link>
	<description>IT-Blog, Fotoblog, Travelblog, Nerdstuff</description>
	<lastBuildDate>Wed, 13 Jan 2021 08:10:52 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.3</generator>

<image>
	<url>https://pixelfriedhof.com/wp-content/uploads/2022/02/cropped-My-project-3-32x32.png</url>
	<title>Cloudflare Archive - Pixelfriedhof</title>
	<link>https://pixelfriedhof.com/en/tag/cloudflare-en/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Reverse Cloudflare activation and deployment</title>
		<link>https://pixelfriedhof.com/en/reverse-cloudflare-activation-and-deployment/</link>
					<comments>https://pixelfriedhof.com/en/reverse-cloudflare-activation-and-deployment/#respond</comments>
		
		<dc:creator><![CDATA[megaadmin]]></dc:creator>
		<pubDate>Mon, 11 Jan 2021 08:22:00 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Cloudflare]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[Nameserver]]></category>
		<guid isPermaLink="false">https://pixelfriedhof.com/?p=3834</guid>

					<description><![CDATA[<p>If the switch to Cloudflare was not successful, the switch to the CDN provider can be easily undone to return to the original state.</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/reverse-cloudflare-activation-and-deployment/">Reverse Cloudflare activation and deployment</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>If the switch to Cloudflare was not successful, the switch to the CDN provider can be easily undone to return to the original state.</p>



<h2 class="kt-adv-heading_6ca51f-fb wp-block-kadence-advancedheading" data-kb-block="kb-adv-heading_6ca51f-fb">Return to the original state</h2>



<h3 class="wp-block-heading">1. Resetting the DNS configuration of the hosting server</h3>



<p>To enable Cloudflare, we had to change the DNS settings of our domain to Cloudflare&#8217;s name servers. We have to undo this change so that our domain works with the old DNS settings again.<br><br>Now we have to wait. It can take up to 24 hours until the DNS settings are distributed worldwide and all servers access our own server again when calling our domain and no longer look for the data at Cloudflare.</p>



<p>With an <a href="https://mxtoolbox.com/DNSLookup.aspx" target="_blank" rel="noreferrer noopener">online DNS lookup</a> we can check if the Cloudflare nameservers we don&#8217;t want are still stored for our domain, or if our old ones are again.</p>



<h3 class="kt-adv-heading_ba6ec1-67 wp-block-kadence-advancedheading" data-kb-block="kb-adv-heading_ba6ec1-67">2. Deleting the page from Cloudflare</h3>



<p>Actually, the first step should be enough. After changing the DNS records, we can completely delete our site from Cloudflare.</p>
<p>Der Beitrag <a href="https://pixelfriedhof.com/en/reverse-cloudflare-activation-and-deployment/">Reverse Cloudflare activation and deployment</a> erschien zuerst auf <a href="https://pixelfriedhof.com/en">Pixelfriedhof</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://pixelfriedhof.com/en/reverse-cloudflare-activation-and-deployment/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
