Point Subdomain e.g. dyndns.example.de to my IP with DynDNS.
Then create CName wiki.example.de to dyndns.example.de
Then create CName www.example.de to dyndns.example.de
Caddy should be able to handle it like this.
I am going to give it a try like this.
Thanks to all of you.
Sounds fine.
Did you get DNSSEC set up (DS records in the parent zone)? That is mandatory when using deSECâs nameservers.
Yes, I have done this.
Everything is working fine now.
One thing I still donât know how to deal withâŚ
I point a subdomain dyndns.example.com to my home IP with DynDNS and use CNAME records to point to this Domain like mentioned above.
I would like to host something at my apex domain but is this possible? When I point my apex domain to my home IP with DynDNS and use CNAME records to refer to it, that would not be the recommended way as mentioned above.
A workaround would be to use the method of the first paragraph of this comment and use a CNAME www.example.com to refer to dyndns.example. com.
But for a specific project it is necessary to use the apex.
Is it possible to use the apex with DynDNS (and subdomains referring to it) without the problems that can rise up with the conflicts between apex CNAME and e.g. SOA record as mentioned above. Did I overlooked something?
The zone apex cannot have a CNAME record. The DNS standard forbids it. If you want to use the apex domain with dynamic DNS and it has to be an A or AAAA record, then you have to have your dynamic DNS client change the records there. You can have CNAMEs at subdomains point to the zone apex. The subdomains âinheritâ all records of the zone apex that way, so that may not be what you want. The alternative is to have a dynamic DNS client change more than records on just one domain, but you canât do that with a Fritzbox and you need to make sure that you donât trigger the rate limit.