Route traffic to CF & Google analytics

Hi,
we want to server our webshop through CF.

sub.xxx.eu -> we have a DNS record pointing the the respective IP:
sub 300 IN A 153.XX.XX.XX

Now, we wanted to move that traffic routed through CF:
Like:
sub 300 IN CNAME sub.xxx.eu.cdn.Cloudflare.net.

Unfortunately that did not work as already we have a TXT entry for that:
sub IN TXT “google-site-verification=XXXX”

What is the correct approach to get this fixed? Fo we need another verification method for GA? Or move it to CF?

Thanks,

Fionn

Hi Sandro,
currently we hav the traffic for our shop url not going through CF. Now we want to let the traffic going through CF to leverage some CF features. Yesterday we wanted to change it but it did not work because of that google analytics TXT entry.
I’m not 100% sure, what would be the right setup… I the end we want to deliver the whole page throught CF, e.g. “https://shop.berner.eu/de-de/”.

Thanks,

Fionn

That is exactly what we wanted to do but the step “set up the DNS records according to your hosts” failed because there was an entry for google analytics.
shop IN TXT “google-site-verification=XXXXX”
And I am not 100% sure if this is needed. How would the new/correct entry look like?

This: [quote=“fionn.ziegler, post:3, topic:44340”]
https://shop.berner.eu/de-de/
[/quote]

How can we do that? with a cname entry right?

No, CNAMEs are not involved at all. You need to change the nameservers at your registrar.

Check out https://support.cloudflare.com/hc/en-us/categories/200275218

We receive an error when we try to add the cname entry to use CF.

it seems https://tools.ietf.org/html/rfc1034 does not allow both CNAME & TXT records at the same time. Is there something we’re missing here?

thanks for you patient sandro & sorry if a miss something here! We did that for berner.eu already:

Now we want to activate shop.berner.eu to go over CF:

We think we have to do it with a cname entry, is that not correct?
New: shop 300 IN CNAME shop.berner.eu.cdn.Cloudflare.net.
Old: shop 300 IN A 153.95.146.199

If we try to save that it does not work with the error above, because there is a txt record already… We use CF with a CNAME setup, probably that is the problem.

that does not work with that TXT entry for google. When we apply that change to our nameserver we get the error above.
So, yep indeed circles :slight_smile:

Yes, the RFCs for DNS do not allow for other entries to exist for a CNAME entry in DNS. SO you would need to remove the TXT record. I don’t think it’s required you retain the TXT record after Google validation is complete.

Hm if we can remove that line simply that would be great. But we need to ensure that this google search console does not stop working after we do that. I could not find a respective comment in their documentation. Do you have an idea how we can find out if we need that or not? Thanks!

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