The most reliable situation would be to setup a CNAME
for a subdomain of (host on) your domain pointing to the domain you are updating with DynDNS. I'll assume your domain is example.com
below.
There are a variety of services that will support dynamically updating domains. Using a CNAME
for your domain is not a supported configuration. If you want it for access to your home system you could setup home.domain.com
as a CNAME
pointing the name updated by DynDNS.
You may be able to find a redirection server which can redirect web requests for your domain to your web subdomain. Requests for example.com
would be redirected to www.example.com
. If you want a reliable web server, you likely need to find a hosting provider. If you have a hosting provider, you may be able to configure your domain's A
record to the same IP address as you use for your web service. Another alternative is not to publish any addresses for your domain, and just have addresses for your subdomains. Browsers may try for a www
subdomain in this case.
DynDNS no longer offers free services. When it did, I had a CNAME in my domain's DNS like home.example.com
which pointed to my DynDNS entry (mydomain.dyndns.org
). I've had a fixed IP address for years, so I haven't worked with the paid service. My www
and mail
subdomains were hosted elsewhere and I provided A
records for those servers. My web provider supported my domain as well as the www
subdomain, so I provided an A
record for my domain with the same address as the www
subdomain.
If you want email services, you will have problems using dynamic IP address. Many domains will refuse to accept mail from you, and you risk loosing incoming mail.