Among the most popular ( and critical ) problems in the Webflow forum involve the process of adding a domain to Webflow - particularly if that domain is already on a live website.
Here are some tips to make the process easier.
Sygnal uses Cloudflare's free DNS service almost exclusively for our clients because of its robust capabilities and rapid updates. This is not necessary or relevant to this lesson, but if your DNS provider is giving you problems, check our migration guide here.
In most cases, your DNS will be managed by your domain registrar, for example GoDaddy. You'll login there to make your DNS changes.
To minimize the risk of downtime for the production site, we approach the DNS change in two parts.
You can perform this step anytime, it will not affect your production site.
In Webflow;
In your DNS;
In Webflow;
The purpose of doing the verification first is that some DNS's are slow to propagate, especially with TXT records. Since this is a crucial step and does not affect your production site, we want to resolve it first.
Do this after-hours, when traffic is minimal, like midnight Sunday for your primary market.
In your DNS;
@
A
records@
symbol next to the A record listing. In others, you'll see your bare domain, like mydomain.com
. These indicate the same thing.A
records, prefixed with e.g. something
or something.mydomain.com
. These are used by other services unrelated to your website.www
recordCNAME
record, but it may be an A
record, or it may not exist. @
A
records, and www recordIn Webflow,
www
recordwww
record in Webflow