DNS record entry for the WWW version of websites

Is a DNS record entry for the WWW version of a website necessary, if on the origin server there is a redirection for the www domain’s URLs to the non-www version of the site?

I think it’s not necessary.
Naked domain works fine without it.

But, I would rather add it to the DNS tab just to make sure my visitors come to the right place.

Furthermore, if Cloudflare manages your DNS records, the visitors would end up in some “black hole” as if the Cloudflare could not find the www record as it’s not existing one and you are not using any Page Rule to redirect/match www to non-www (again, not having a www hostname would create issue), meaning they could encounter the error.

Could be I am wrong about this, from my understanding.

From my experience I’ve seen websites working only on naked domain, without www or having a redirect from www to non-www.

Nevertheless, my practice is inverse, to have non-www to www, while keeping both @ and www records at the DNS :slight_smile:

I’m getting this error: “The number of lookups on your SPF record exceed the allowed limit of 10. This will result in emails failing SPF authentication.”

Someone suggests that keeping records number bellow 11 solves the problem.

I have to look what else I can delete, if anything, in order to try the proposed solution.

1 Like

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