Domain DNS Configuration

We start by identifying who controls the domain: the registrar, the current nameservers, and the DNS provider if separate, such as Cloudflare or the hosting company. We confirm that you have access, and, if not, we help with recovery. We then export or screenshot every existing record and list what each is for: website, email, subdomains, verification and third-party services such as CRM, ticketing, marketing tools and payment gateways. Many problems come from records nobody remembers. Next, we define the target setup. For the website, we decide the root domain and www versions, the redirect between them, and whether a CDN or proxy is used. For email, we confirm the provider, such as Google Workspace, Microsoft 365 or hosting mail, and gather its MX values and recommended settings; see business email configuration and domain authentication with SPF, DKIM and DMARC. For services, we collect required verification TXT or CNAME values. When moving a site, we plan the sequence to reduce downtime. We lower the TTL, which is the time records are cached, a day or two beforehand; then change the A record when the new server is ready and tested; and restore a normal TTL after things are stable. If nameservers are being changed, we recreate every needed record at the new provider before switching, because missing records at the moment of change cause outages. We apply changes in small steps and test after each: loading the site with and without www, checking the secure connection, sending and receiving test emails, and verifying services such as Search Console and Google Business Profile; see SSL certificate installation. We use DNS lookup tools to confirm that records are visible from different locations, remembering that changes can take from minutes to a couple of days to spread. We watch for common errors: a CNAME at the root, duplicate SPF records, MX records pointing to old providers, conflicting A records, missing www, and expired verification records. We then record the final setup in a DNS sheet with each record, its purpose, value, and who set it, plus a change log. We recommend turning on registrar lock and two-step login, and setting renewal reminders; see website uptime monitoring to notice problems early. We cannot control the time DNS takes to spread, and we cannot fix issues with a provider that refuses access, but a planned change prevents most disruption. If you are also changing hosting, see cloud hosting setup.