CNAME Records not working


I am trying to set up a reverse proxy for my server. It wasn’t working so started experimenting with the DNS Records and I set up a few test records to point to other domains. I found out that they always return either a 400 or 404 status code.

Am I doing something wrong?

You will need to switch that record :grey: if you want an actual CNAME.

1 Like

Thanks for the quick reply!

Wouldn’t that kind of defeat the purpose of a reverse proxy?
Also when I switch it to a Grey Cloud I am still having the same problem.

Of course it would, but you cant expect a CNAME with that setup. Also, of course you are getting these return codes or do you have control over Google’s main webserver and managed to configure your domain there?

What would be the correct approach for doing something like this then? Because what I want is having a CNAME point the duckdns with holds the actual IP of my server, so that I can keep that IP hidden from the public.

I now realize that a CNAME to google is not going to work. I kind of thought of it as a redirect to another domain, but apparently that is not the case.

A CNAME is correct, but what is it you actually want to achieve? Whether it is a CNAME or an A record does not matter, as long as it is proxied it wont carry the actual destination but only the proxy records.

Simply point your record to the host in question (either hostname or IP) and proxy it. If that host is properly configured the connection will work.

No, CNAMES do not redirect, they are basically regular A records but dont hold an IP address but a hostname with the eventual address. Think of them as dynamic A records.

Well the reason I was trying to redirect to Google is to check whether I was able to access a site through Cloudflare using my own domain. Which apparently I can, but I wasn’t doing it right.

The issue I am having is, that I would like to be able to access my Plex Container running on Unraid (And other containers in the future) over the internet using a reverse proxy.

So I have set up my portforwarding, duckdns and letsencrypt and I can access the letsencrypt container locally using but the is not working. It just times out and I am not sure what the problem is.

So you want to point the host to a machine on your local network? Make sure that machine is actually accessible from the outside, then you only need the IP address.

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