The most nervous I have been while setting up Built on Zero had nothing to do with writing content or choosing a niche. It was the moment I opened the DNS area for builtonzero.com and saw a collection of records that looked important enough that touching the wrong one might make something disappear. Systeme.io had given me records to add. I knew what DNS was in a general sense, but “general sense” and “I am comfortable changing a live domain” are not the same thing.
This is the part most “connect your domain in five minutes” tutorials skip. The clicking may take five minutes. Understanding what you are clicking can take longer, particularly if your domain already has email or other services attached to it. I did not want Built on Zero’s experiment in saving money to become an experiment in how quickly I could break a domain, so I stopped and asked Afrihost for help.
The first thing I had to understand was that connecting the website domain and authenticating the domain for email are separate jobs. Systeme.io’s current documentation treats them separately too. The custom-domain connection tells the internet where the web traffic should go. Email authentication is about proving that Systeme.io is authorised to send email using your domain. That is why you can see different CNAME records and, for email authentication, records involving things such as domain keys and DMARC.
Once I understood that, the list of records felt less random. A CNAME is essentially pointing one name toward another destination. Email-authentication records help receiving mail systems verify that messages claiming to come from your domain are legitimate. You do not need to become a DNS engineer to set up a small business, but knowing the purpose of the records makes it easier to follow instructions without treating the whole process like magic.
My strongest advice is not to copy DNS values from somebody else’s tutorial. Systeme.io generates account-specific records. The exact values in my account are not the values you should paste into yours. Open the domain settings inside your own Systeme.io account and use the records it gives you. If the interface or documentation changes after this article is published, follow the current instructions rather than a screenshot frozen in 2026.
The same goes for your domain provider. Afrihost’s control panel may not look like GoDaddy, Namecheap, Cloudflare or another provider. The labels can differ slightly, and some systems automatically append the domain name to the host field. That means blindly following a tutorial created for another provider can produce duplicated domain names or incorrect records. If you are uncertain, this is a perfect moment to use support.
I emailed Afrihost because I did not want to break anything. There is no prize for personally editing every technical setting in your business. Sometimes the competent decision is knowing what you do not want to guess. Systeme.io also currently documents a free DNS setup support option, which I wish I had noticed earlier. If the platform and your domain provider can help, use them.
OPEN SYSTEME.IO FREE AND GET YOUR ACCOUNT-SPECIFIC DOMAIN RECORDS — CLICK HERE
That is my affiliate link. If you later purchase an eligible Systeme.io plan, I may earn a commission. Systeme.io’s current free plan includes one custom domain, so you do not need to upgrade simply to connect your own domain.
Before changing anything, I would take a screenshot or export of the existing DNS zone if your provider allows it. This is basic caution. You want a record of what was there before you started. Do not delete existing MX records or other entries because they look unfamiliar. MX records, for example, can control where your email is delivered. Removing them casually can create a much larger problem than the one you were trying to solve.
Then add only the records required for the specific job. If you are connecting the domain, follow the custom-domain instructions. If you are authenticating email, follow the email-authentication instructions. Do not assume one automatically completes the other. Systeme.io’s current email-authentication help explains that authentication is required when sending from a custom domain through the platform and provides the records generated for that domain.
After adding records, expect DNS changes to take time. This is another place where beginners can panic. You make the change, refresh Systeme.io thirty seconds later, see that verification has not completed and assume something is wrong. DNS propagation is not always immediate. Give the records time, then check again. If verification continues to fail, compare the host and value carefully and ask support before making random additional changes.
Email authentication is worth doing properly because deliverability matters. You can write the best welcome email in the world and achieve nothing if it repeatedly lands in spam. Authentication does not guarantee inbox placement, because sender reputation and content matter too, but it establishes the technical legitimacy of the sending domain. For Built on Zero, that matters because email is supposed to become an owned channel rather than a decorative feature.
I would also use a real sender address on the domain once everything is ready rather than building the entire brand around a free personal mailbox. A domain-based sender looks more coherent and gives you better control over the brand. That does not mean the email itself should sound corporate. I want Built on Zero emails to sound like a person wrote them. Technical professionalism and human writing are perfectly compatible.
There is a broader lesson in this setup that I think applies to starting online generally. “Easy” software does not eliminate every technical task. It removes some of them. You still own a domain on the public internet. DNS still exists. Email standards still exist. Payment processors, analytics and other services will eventually introduce their own technical language. The goal is not to find a platform where you never have to learn anything. The goal is to keep the number of systems manageable enough that learning does not become the whole business.
If you are scared of breaking your domain, do not let that fear stop the project. Build the pages first using the temporary platform address if necessary. Get comfortable with the funnel. Then connect the domain carefully. There is no rule saying every technical step has to be completed on day one. Sequence the work so that one confusing setting does not block everything else.
I would also avoid changing DNS late at night before a launch or important email. Give yourself time to verify that the website, existing email and new records all behave correctly. Test the domain from more than one device. Send a test email to different providers if possible. Check links. The five extra minutes of testing are much cheaper than discovering a problem after traffic arrives.
For Built on Zero, asking Afrihost for assistance did not make the experiment less legitimate. It made it more realistic. Small business owners use support. We ask accountants tax questions and hosting companies hosting questions. “Doing it yourself” should mean taking responsibility for the outcome, not refusing expertise when it is available.
Once the records are verified, the payoff is simple: the funnel lives on a domain that belongs to the brand, and the email system can send from that domain with the appropriate authentication in place. The reader never sees the DNS work. That is how infrastructure should feel when it is finished. It disappears behind the experience.
If you are at this step now, open your Systeme.io domain settings, copy the exact records generated for your account and compare them with the current help documentation. Then open your domain provider in another tab. If the fields make sense, add them carefully. If they do not, send the records to support and ask them to assist. Do not turn uncertainty into improvisation. A custom domain is supposed to make the business look more credible; there is no need to prove your credibility by gambling with the settings behind it.
There is one more reason I am glad I slowed down at the DNS step: email and website problems can look unrelated after the fact. If you change several records at once and something stops working, troubleshooting becomes much harder. I prefer changing only what the instructions require, waiting for verification and testing before moving on. It is less exciting and much easier to reverse.
I also keep the support email and the records supplied by Systeme.io together in my project notes. Six months from now, I do not want to rely on memory to explain why a strange-looking CNAME exists. Documentation is not only for large companies. A one-person business becomes easier to manage when past-you leaves future-you a note.
One last practical habit has already helped me: I keep the domain work separate from the creative work. If I am waiting for DNS verification, I do not sit refreshing the screen for two hours. I go back to the landing page, write the next article or prepare the email sequence. Propagation time does not have to become lost time. This sounds obvious, but technical waiting can easily derail an entire work session when you are already nervous about the setup.
A quick note before you go: Software pricing, features, free-plan limits and terms can change, sometimes without much notice. Everything in this article was accurate to the best of my knowledge when it was written or last updated, but please check the provider’s official website for the latest pricing, features and terms before making a decision or signing up. Built on Zero does its best to keep our guides current, but we can’t guarantee that every price or feature will remain unchanged after publication.
