Purpose of this guide
This guide shows you how to connect a domain, subdomain, and professional email in Builderall without breaking your website, email, or any other service already connected to your domain.
Use this guide when you need to:
Connect your own domain to a website created in Builderall.
Connect a subdomain to a website created in Builderall.
Choose between connecting with Name Servers or connecting by IP.
Keep existing professional email services working.
Create or configure Builderall professional email.
Set up professional email in Outlook, Gmail, Apple Mail, Thunderbird, or another email app.
Validate your domain and sender to send emails through MailingBoss.
Fix DNS, SSL, propagation, cache, or domain already connected errors.
1. Understand the main terms
Domain
This is the main address of your website.
Example:
yourdomain.com
Subdomain
This is a section of the main domain.
Examples:
blog.yourdomain.com
course.yourdomain.com
lp.yourdomain.com
DNS
DNS is the configuration that tells the internet where your domain should point.
Think of DNS as the routing map for your domain.
Name Servers
Name Servers are the servers that control the entire DNS zone of your domain.
When you change the Name Servers, you change who controls all DNS records for that domain.
This can affect your website, email, subdomains, and other services.
A Record
An A record is a DNS record that points a domain or subdomain to an IP address.
Example:
yourdomain.com points to 64.251.1.115
CNAME
A CNAME is a DNS record that points one name to another name.
Example:
webmail.yourdomain.com points to mailXX.l4email.com
MX
An MX record defines which server receives emails for your domain.
Without the correct MX record, your domain may stop receiving emails.
TXT
A TXT record is used for validations and authentication.
Common examples:
SPF
DKIM
DMARC
Domain verifications
SSL
SSL is the security certificate that allows your website to open with HTTPS and a padlock.
Example:
DNS propagation
DNS propagation is the time it takes for the internet to recognize a DNS change.
During propagation, your site may work in one place and not work in another.
Cache
Cache is temporary memory stored by your browser, network, or internet provider.
Even after the setup is correct, cache may still show an old version or an old error for a while.
2. The most important rule before changing any DNS
Before changing anything in your domain provider, connect the domain or subdomain inside Builderall first.
The correct order is:
- Open the website or tool inside Builderall.
- Enter the domain or subdomain you want to connect.
- Click to connect it.
- Only after that, open your domain provider and configure DNS if needed.
Do not start with Registro.br, GoDaddy, Hostinger, Namecheap, Cloudflare, or any other provider.
Start inside Builderall.
This helps prevent errors like domain not recognized, domain not prepared, or incomplete configuration.
3. Choose the right connection method
The best method depends on what already exists on the domain.
Scenario 1
The domain was purchased inside Builderall.
Use this path:
Do not change DNS manually.
Do not change Name Servers.
Do not create records manually.
Just activate or confirm the domain through the email you received.
Scenario 2
The domain was purchased outside Builderall and does not have professional email, subdomains, or other active services.
Use this path:
You can connect it using Name Servers.
Builderall will control the entire DNS zone of the domain.
Scenario 3
The domain was purchased outside Builderall and already has professional email, Google Workspace, Microsoft 365, Zoho, subdomains, or other active services.
Use this path:
Do not change the Name Servers.
Use IP connection with A records.
This is the safest method to preserve existing services.
Scenario 4
You only want to connect a subdomain.
Use this path:
Connect the subdomain inside Builderall first.
Then configure the corresponding DNS record in the current domain provider.
Scenario 5
You want to use Builderall professional email, but the domain DNS is managed outside Builderall.
Use this path:
Configure the required MX, CNAME, and TXT records in the current domain provider.
Scenario 6
You want to send email campaigns through MailingBoss.
Use this path:
Validate the domain and sender inside MailingBoss.
MailingBoss does not create the email inbox. The email address must already exist.
4. When to use Builderall Name Servers
Use Name Servers when you want Builderall to control the entire DNS of the domain.
This method is recommended when the domain does not already have important services configured.
Use Name Servers when
The domain is new.
The domain does not have active professional email.
The domain does not use Google Workspace.
The domain does not use Microsoft 365.
The domain does not use Zoho Mail.
The domain does not have active subdomains.
The domain does not have important external integrations.
You want to manage everything through Builderall.
Do not use Name Servers without checking first when
The domain already has professional email working.
The domain already uses Google Workspace.
The domain already uses Microsoft 365.
The domain already uses Zoho Mail.
The domain already has subdomains in use.
The domain already points to other systems.
The domain already has a store, portal, members area, or external application.
Changing Name Servers changes full DNS control.
If old records are not recreated correctly, the website may work, but the email may stop working.
5. How to connect a domain using Name Servers
Step 1
Open Builderall Website Builder.
Step 2
Open the website that will receive the domain.
Step 3
Go to the website domain area.
Step 4
Enter the domain you want to connect.
Example:
yourdomain.com
Step 5
Click to connect.
Step 6
Builderall will show the Name Servers that must be used.
Copy the exact Name Servers shown on your screen.
Do not use Name Servers from another domain.
Do not use Name Servers from another tutorial.
Do not change letters, numbers, or dots.
Step 7
Open the provider where the domain was purchased.
Examples:
Registro.br
GoDaddy
Hostinger
Namecheap
HostGator
Cloudflare
Step 8
Look for a section called:
Name Servers
DNS Servers
Domain DNS
Step 9
Replace the current Name Servers with the Name Servers shown by Builderall.
Step 10
Save the change.
Step 11
Wait for propagation.
Propagation may take a few hours and, in some cases, up to 48 hours.
6. Special note for Registro.br
If the domain is registered with Registro.br, wait around 2 hours after connecting the domain inside Builderall before continuing the configuration.
This wait helps prevent configuration failures and temporary DNS errors.
7. When to use IP connection
Use IP connection when you do not want to change the domain’s Name Servers.
This is the recommended method when the domain already has other active services.
Use IP connection when
The domain already has professional email.
The domain already uses Google Workspace.
The domain already uses Microsoft 365.
The domain already uses Zoho Mail.
The domain already has active subdomains.
The domain uses Cloudflare.
The domain already has other connected services.
You want to connect only the website without changing the rest of the DNS.
What will be configured
You will create A records in the current DNS provider.
The Name Servers will stay the same.
Email and other existing services will not be removed, as long as you do not delete old records that are still required.
8. Official IPs by region
Choose only one IP based on your server region.
United States
64.251.1.115
Europe
141.147.2.163
Brazil
137.131.215.227
Singapore, Asia, and Oceania
161.118.202.243
Use only the IP that matches your server region.
Do not use two IPs at the same time.
Do not mix IPs from different regions.
9. How to connect the main domain by IP
Use this setup when you want to connect the main domain.
Example domain:
yourdomain.com
You must create two A records.
Record 1
Type: A
Host: @
Value: IP of the selected region
Record 2
Type: A
Host: www
Value: same IP of the selected region
Both records are required.
One record connects the domain without www.
The other connects the domain with www.
If one is missing, one version may not work.
10. How to fill in the Host field correctly
Each provider may use a different name for the same field.
The field may appear as:
Host
Name
Entry
Subdomain
For the domain without www, use:
@
If the provider does not accept @, use:
yourdomain.com
If the provider says to leave the field blank for the root domain, leave it blank.
For the www version, use:
www
Do not enter https://
Do not enter http://
Do not add a slash.
Do not add a page path.
Wrong:
Wrong:
yourdomain.com/page
Correct:
yourdomain.com
Correct:
www
11. What to do if an A record already exists
If an A record already exists for the root domain and points to another IP, edit that record and replace it with the correct Builderall IP.
If an A record already exists for www and points to another IP, edit that record and replace it with the same correct Builderall IP.
Do not leave two conflicting A records for the same host.
Example conflict:
A @ 123.123.123.123
A @ 64.251.1.115
In this case, keep only the correct record.
12. Do I need to create a CNAME for IP connection?
No.
To connect the main domain by IP, create only A records.
Do not create a CNAME for this method.
13. How to connect a subdomain by IP
Use this setup when you want to connect only a subdomain.
Example subdomain:
lp.yourdomain.com
Create this record:
Type: A
Host: lp
Value: IP of the selected region
Example using the United States server:
Type: A
Host: lp
Value: 64.251.1.115
After that, the connected address will be:
lp.yourdomain.com
14. Subdomain with www
In most cases, you do not need to use www before a subdomain.
Usually, the correct address to share is:
lp.yourdomain.com
Not:
If you really need www.lp.yourdomain.com to work too, create a second record.
Type: A
Host: www.lp
Value: same IP of the selected region
Use this setup only if that format is required.
15. When Builderall shows specific records for the subdomain
Some tools may show specific connection records.
When Builderall shows its own records on the connection screen, copy exactly what appears.
Do not adapt them.
Do not change the type.
Do not turn CNAME into A.
Do not turn A into CNAME.
Do not change the destination.
Do not remove dots, text, or codes.
The rule is simple:
Whatever appears on the Builderall connection screen must be copied exactly into your DNS provider.
16. Domain purchased inside Builderall
If the domain was purchased inside Builderall, do not configure DNS manually.
You do not need to:
Change A records.
Change CNAME records.
Change MX records.
Change Name Servers.
Create TXT records.
Create records manually.
The required step is to activate or confirm the domain through the email you received.
Where to look for the activation email
Inbox.
Spam.
Junk.
Promotions.
Updates.
Common symptom
The domain appears in the account.
The payment was approved.
The website does not publish.
In this case, the likely cause is that the domain has not been activated through the email yet.
17. SSL and HTTPS
SSL is the security certificate that makes the website open with HTTPS and a padlock.
Example:
After the domain is pointing correctly, SSL may take up to around 2 hours to be generated.
During this time, the website may open without a padlock or show a security warning.
That can be normal at first.
When to contact support about SSL
Contact support if all the conditions below are true:
The domain is already pointing correctly.
The website already opens.
More than 2 hours have passed.
The website still does not have HTTPS.
You already checked that Cloudflare proxy is not interfering.
18. Setup with Cloudflare
If the domain uses Cloudflare, pay attention to the proxy.
For SSL to be generated correctly, the website records should temporarily be set to DNS Only.
How to configure this in Cloudflare
- Open Cloudflare.
- Open the domain.
- Go to DNS.
- Find the A records used for the website.
- Disable the proxy.
- The status should be DNS Only.
- Wait for SSL to be generated.
- Test the website with HTTPS.
- After HTTPS is working, the proxy can be enabled again.
Important
Email records should not have proxy enabled in Cloudflare.
Records like mail, webmail, smtp, imap, pop, and other email related records should stay as DNS Only.
19. Builderall professional email
Professional email is an email inbox using your own domain.
Example:
Professional email is not the same as MailingBoss.
Difference between professional email and MailingBoss
Professional email is the inbox used to send and receive messages.
Example:
MailingBoss is the tool used for campaigns, automations, and email marketing.
MailingBoss does not create the email inbox.
Before validating a sender in MailingBoss, the email address must exist.
20. How to configure professional email in an external app
Use this section to configure professional email in apps like:
Outlook.
Gmail.
Apple Mail.
Thunderbird.
Mailbird.
Phone email app.
Any other email client.
21. How to find the professional email pool
Builderall professional email uses this server format:
mailXX.l4email.com
XX must be replaced with the real pool number for your domain.
Examples:
mail07.l4email.com
mail12.l4email.com
Do not use mailXX.l4email.com literally.
XX is only a placeholder. It must be replaced with the real pool number.
Option 1: check inside Builderall
When the domain is connected in Builderall, the pool can be found inside the platform.
Open the DNS Manager or the area where the domain was connected.
Check the DNS records shown for the domain.
Look for the MX record.
The MX record will point to the domain’s email server.
Example:
mail07.l4email.com
In this example, the pool is:
07
So, to configure email in external apps, use:
mail07.l4email.com
The same server should be used for incoming and outgoing email.
Option 2: check the MX using an external tool
If you cannot see the MX record inside Builderall, you can also check the domain using an external DNS lookup tool.
Use a DNS checker and search for this record type:
MX
Then check which server appears as the MX destination.
Example:
mail12.l4email.com
In this case, the pool is:
12
And the correct server will be:
mail12.l4email.com
Option 3: ask support
If the domain does not show an MX record yet, if the professional email has not been prepared yet, or if the domain uses external DNS and the pool is not visible, ask support to confirm the Pool Entry.
After support provides the pool, replace XX with the correct number in all email records and settings.
22. Incoming email setup with IMAP
IMAP is recommended for most users.
Use IMAP when you want to access the same email account from more than one device.
Example:
Computer.
Phone.
Tablet.
Webmail.
External app.
IMAP settings
Account type: IMAP
Incoming server: mailXX.l4email.com
Port: 993
Security: SSL/TLS
Username: full email address
Password: email password
Example:
Account type: IMAP
Incoming server: mail07.l4email.com
Port: 993
Security: SSL/TLS
Username: contact@yourdomain.com
Password: email password
23. Incoming email setup with POP
POP should only be used when the user understands this type of setup.
POP may download messages to the device.
Depending on the app settings, messages may be removed from the server and stay available only on the device where they were downloaded.
To avoid losing access from other devices, use IMAP.
POP settings
Account type: POP
Incoming server: mailXX.l4email.com
Port: 995
Security: SSL/TLS
Username: full email address
Password: email password
24. Outgoing email setup with SMTP
SMTP is used to send emails.
SMTP settings
Outgoing server: mailXX.l4email.com
Port: 465 or 587
Security: SSL/TLS
Authentication: Yes
Username: full email address
Password: email password
Example:
Outgoing server: mail07.l4email.com
Port: 465
Security: SSL/TLS
Authentication: Yes
Username: contact@yourdomain.com
Password: email password
If port 465 does not work, try port 587.
25. Builderall professional email with external DNS
Use this section when:
The domain is outside Builderall.
DNS is managed by another provider.
You want to use Builderall professional email.
You do not want to change the domain’s Name Servers.
In this case, you will need to configure DNS records in the current provider.
26. Pool Entry for professional email with external DNS
To use Builderall professional email with external DNS, the domain needs a Pool Entry.
First, check if the domain is already connected in Builderall and open the records shown in DNS Manager.
Look for the MX record.
The destination of the MX record shows the required pool.
Example:
Type: MX
Destination: mail07.l4email.com
In this case, the pool is 07.
If DNS Manager does not show the MX record, if the domain email has not been prepared yet, or if you are not sure which pool is correct, ask support to create or confirm the Pool Entry.
After that, use the server provided in the records and email settings.
Example:
mail07.l4email.com
27. MX record for Builderall professional email
The MX record defines who receives emails for the domain.
Configure it like this:
Type: MX
Host: @
Destination: mailXX.l4email.com
Priority: 10
Example with pool 07:
Type: MX
Host: @
Destination: mail07.l4email.com
Priority: 10
If the provider does not accept @, use the full domain.
Example:
Type: MX
Host: yourdomain.com
Destination: mail07.l4email.com
Priority: 10
Do not add https://
Do not add http://
Do not add a slash.
28. CNAME records for Builderall professional email
Create the CNAME records below in the domain DNS.
Replace XX with the pool number.
Type: CNAME
Host: mx
Destination: mailXX.l4email.com
Type: CNAME
Host: mail
Destination: mailXX.l4email.com
Type: CNAME
Host: webmail
Destination: mailXX.l4email.com
Type: CNAME
Host: smtp
Destination: mailXX.l4email.com
Type: CNAME
Host: pop
Destination: mailXX.l4email.com
Type: CNAME
Host: pop3
Destination: mailXX.l4email.com
Type: CNAME
Host: imap
Destination: mailXX.l4email.com
Type: CNAME
Host: imap4
Destination: mailXX.l4email.com
Example with pool 07:
Type: CNAME
Host: mail
Destination: mail07.l4email.com
In Cloudflare, these records must be set to DNS Only.
Do not leave proxy enabled on email records.
29. SPF for Builderall professional email
SPF is a TXT record that authorizes servers to send emails using your domain.
Use this setup when the domain does not already have an SPF record:
Type: TXT
Host: @
Value: v=spf1 a mx ip4:65.111.191.0/24 include:mailingboss.net include:mailXX.l4email.com ~all
Example with pool 07:
Type: TXT
Host: @
Value: v=spf1 a mx ip4:65.111.191.0/24 include:mailingboss.net include:mail07.l4email.com ~all
If the provider does not accept @, use the full domain in the Host field.
30. Critical SPF rule
A domain should not have two separate SPF records.
If there is already a TXT record that starts with:
v=spf1
Do not create another one.
Edit the existing SPF and include the required authorizations before the ending.
Example of existing SPF:
v=spf1 include:_spf.google.com ~all
Example adjusted to include Builderall:
v=spf1 include:_spf.google.com a mx ip4:65.111.191.0/24 include:mailingboss.net include:mail07.l4email.com ~all
Important:
Keep only one SPF record.
Everything must stay on the same line.
The SPF must start with v=spf1.
The SPF must end with ~all or -all.
31. MailingBoss and domain validation
Use this section when you want to send campaigns or automations through MailingBoss.
Before you start, the sender email must exist.
Example:
Do not try to validate an email that has not been created yet.
32. How to add a domain in MailingBoss
Enter only the clean domain.
Correct:
yourdomain.com
Wrong:
Wrong:
Wrong:
yourdomain.com/page
After adding the domain, MailingBoss will show DNS records for validation.
Copy the records exactly as they appear.
33. Records MailingBoss may generate
MailingBoss may generate records such as:
DKIM.
SPF.
DMARC.
CNAME.
These records must be created in the provider that controls the domain DNS.
If the domain uses Builderall Name Servers, configure them in Builderall.
If the domain uses Cloudflare, configure them in Cloudflare.
If the domain uses Registro.br, GoDaddy, Hostinger, Namecheap, or another provider, configure them in that provider’s panel.
34. MailingBoss DKIM
DKIM is an authentication method that helps prove the email was sent by an authorized server.
Configure it exactly as MailingBoss shows it.
Template:
Type: TXT
Host: copy the host shown in MailingBoss
Value: copy the value shown in MailingBoss
Do not edit the value.
Do not remove characters.
Do not split the text into parts.
Do not add extra spaces.
35. MailingBoss SPF
If the domain does not have SPF, create the SPF shown by MailingBoss.
If the domain already has SPF, edit the existing SPF.
Do not create two SPF records.
The MailingBoss include must be added before ~all or -all.
36. MailingBoss DMARC
DMARC usually uses this host:
_dmarc
Template:
Type: TXT
Host: _dmarc
Value: value shown by MailingBoss
If the value shows a generic email, replace it with a real email from the domain.
Example:
Or:
37. MailingBoss CNAME
Configure it exactly as MailingBoss shows it.
Template:
Type: CNAME
Host: copy the host shown in MailingBoss
Destination: copy the destination shown in MailingBoss
Do not add https://
Do not add http://
Do not add a slash at the end.
38. Sender validation in MailingBoss
After validating the domain, validate the sender too.
Step by step
- Open the sender area in MailingBoss.
- Enter the professional email address.
- Request the validation code.
- Open the email inbox.
- Also check spam and junk.
- Copy the code you received.
- Paste the code into MailingBoss.
- Complete the validation.
Without sender validation, sending will not be enabled.
39. How to keep existing email working when connecting a website
If the domain already has working email, do not change Name Servers before reviewing all existing records.
To keep existing email working, use IP connection.
This way, the website points to Builderall, but the email stays where it already is.
Before changing anything, check if there are records for:
MX.
SPF.
DKIM.
DMARC.
Mail CNAME.
Webmail CNAME.
SMTP CNAME.
IMAP CNAME.
POP CNAME.
Verification TXT records.
Records used by Google Workspace.
Records used by Microsoft 365.
Records used by Zoho.
Records used by another hosting provider.
40. DNS propagation
After saving DNS changes, it may take some time to work.
During propagation, you may see things like:
The website does not open right away.
The website opens on your phone, but not on your computer.
The website opens on one network, but not on another.
The website works intermittently.
SSL does not appear yet.
Email takes some time to normalize.
The old version of the website still appears.
This does not necessarily mean something is wrong.
41. Expected time
DNS by IP
It can take up to 48 hours.
In many cases, it works within a few minutes.
SSL
It can take up to around 2 hours after the domain is already pointing correctly.
Registro.br
After connecting the domain inside Builderall, wait around 2 hours before continuing.
Email records may take a few hours to propagate.
42. Cache and website updates
Use this section when you published changes to the website but still see the old version.
First tests
Open an incognito window.
Try another browser.
Test on your phone using mobile data.
Ask someone else to test from another network.
If it works somewhere else, the issue is probably local cache.
43. Sync the website version
Use this path directly after the domain:
https://yourdomain.com/cheetah/version
Example:
https://lojadaclau.com.br/cheetah/version
Do not use it inside an internal page.
Correct:
https://yourdomain.com/cheetah/version
Wrong:
https://yourdomain.com/page/contact/cheetah/version
44. Clear the website cache
Use this path directly after the domain:
https://yourdomain.com/cheetah/remove
Example:
https://lojadaclau.com.br/cheetah/remove
Do not use it inside an internal page.
Correct:
https://yourdomain.com/cheetah/remove
Wrong:
https://yourdomain.com/page/contact/cheetah/remove
45. Recommended cache order
- Publish the website.
- Test in a regular tab.
- Test in an incognito window.
- Use /cheetah/version.
- Test again.
- Use /cheetah/remove.
- Test again in incognito.
- Test from another network if needed.
46. Domain already connected error
This error may appear with messages like:
Domain already exists in website
Or:
This domain is already connected to another website
This means the domain is already linked to another website or another account.
Builderall prevents duplicate connections to avoid conflicts.
How to fix it if you have access to the old website
- Open the old website.
- Go to the domain settings.
- Disconnect the domain.
- Go back to the new website.
- Connect the domain again.
How to fix it if you do not have access to the old website
Ask support to release the domain.
How to avoid this problem
Before deleting any website, disconnect the domain.
Deleting the website without disconnecting the domain may leave the domain stuck.
47. Builderall temporary link stopped working
Before connecting a custom domain, the website may use a temporary Builderall link.
After the custom domain is connected, the temporary link may stop working.
This is expected.
After connecting the custom domain, always use the main domain.
Example:
Before:
mysite.site.builderallsite.com
After:
yourdomain.com
Use the custom domain.
48. Changing the subdomain breaks old links
If you change the subdomain, the address changes.
Example:
Before:
old.yourdomain.com
After:
new.yourdomain.com
All old links will stop working.
Manually update every place where the old link was used.
Check:
Ads.
WhatsApp.
Emails.
Website buttons.
Social media.
QR codes.
Printed materials.
Automations.
Thank you page.
PDFs.
External integrations.
49. Checklist before changing DNS
Before saving any change, answer these questions:
Does the domain already have professional email working?
Does the domain use Google Workspace?
Does the domain use Microsoft 365?
Does the domain use Zoho?
Does the domain have active subdomains?
Does the domain have a store, portal, or external application?
Does the domain use Cloudflare?
Is the goal to connect the entire website?
Is the goal to connect only a subdomain?
Is the goal to create professional email?
Is the goal to validate sending in MailingBoss?
If the domain already has active services, do not change the Name Servers without mapping and recreating the required records.
When in doubt, use IP connection for the website.
50. Troubleshooting
The domain does not open
Check:
The domain was typed correctly.
The domain was connected inside Builderall.
The website is published.
The DNS records were created in the correct provider.
The IP is correct.
The record without www exists.
The record with www exists.
There are no conflicting A records.
You waited for propagation.
Cache was cleared.
The test was done from another network.
The site works with www, but not without www
The root domain record is missing.
Create:
Type: A
Host: @
Value: IP of the selected region
The site works without www, but not with www
The www record is missing.
Create:
Type: A
Host: www
Value: same IP of the selected region
The old website appears
Possible causes:
Cache.
Incomplete propagation.
Old A record still active.
Local DNS is outdated.
Record configured in the wrong provider.
What to do:
Test in incognito.
Clear cache.
Test from another network.
Check for old records.
Confirm where DNS is managed.
Wait for propagation.
SSL does not appear
Check:
The domain already opens.
DNS points correctly.
Up to 2 hours have passed.
Cloudflare is temporarily set to DNS Only.
No proxy is blocking SSL generation.
If everything is correct and SSL still does not appear after the expected time, contact support.
Email stopped working after connecting the domain
Likely cause:
Name Servers were changed and the old email records were not recreated.
Check:
MX.
SPF.
DKIM.
DMARC.
Email CNAMEs.
Verification TXT records.
Records from the previous provider.
If the email must stay with another provider, restore that provider’s records.
Email does not configure in Outlook, Gmail, Apple Mail, or Thunderbird
Check:
The server uses the correct pool.
The server is in this format: mailXX.l4email.com.
XX was replaced with the correct number.
The IMAP port is 993.
The POP port is 995.
The SMTP port is 465 or 587.
SSL/TLS is enabled.
The username is the full email address.
The password is correct.
SMTP authentication is enabled.
MailingBoss does not validate the domain
Check:
The domain was entered without www.
The domain was entered without https://
The domain was entered without a page path.
DKIM was created correctly.
SPF was created or edited correctly.
There are not two SPF records.
DMARC uses the host _dmarc.
The CNAME was copied exactly.
You waited for propagation.
The sender validation code did not arrive
Check:
The email address really exists.
The address was typed correctly.
Inbox.
Spam.
Junk.
Promotions.
Whether the domain is receiving emails normally.
Then request the code again.
51. FAQ
Can I change the Name Servers?
Yes, but this changes full DNS control.
If the domain already has email, subdomains, or active services, use IP connection.
Which method is safer?
For an external domain with email or other active services, the safest method is IP connection.
Do I need to create a CNAME to connect the website by IP?
No.
For IP connection, use A records.
Do I need to configure both with www and without www?
Yes.
For the main domain by IP, both records are required.
One for the domain without www.
One for the domain with www.
Can I use more than one IP?
No.
Use only the IP for your server region.
How long does it take to work?
It may take up to 48 hours, depending on the provider and DNS propagation.
Does SSL take time?
Yes.
After the domain is already pointing correctly, SSL may take up to around 2 hours.
The website opens on my phone, but not on my computer. Is something wrong?
Not necessarily.
It may be cache, local DNS, or propagation.
Test from another network, in incognito, and with mobile data.
Is professional email the same as MailingBoss?
No.
Professional email is the email inbox.
MailingBoss is the tool used to send campaigns and automations.
Does MailingBoss create my email address?
No.
The email address must exist before it can be validated in MailingBoss.
Can I have two SPF records?
No.
Keep only one SPF record per domain.
If SPF already exists, edit the existing one.
What does domain already connected mean?
It means the domain is already linked to another website or account.
Disconnect it from the old website or ask support to release it.
52. Final summary for beginners
If you purchased the domain inside Builderall, do not change DNS. Just activate the domain through the email you received.
If you purchased the domain outside Builderall and it does not have email or other services, you can use the Name Servers shown by Builderall.
If you purchased the domain outside Builderall and already use professional email, do not change the Name Servers. Use IP connection.
For IP connection, create two A records: one for the domain without www and one for the domain with www.
If you use Cloudflare, temporarily turn off the proxy until SSL is generated.
To configure professional email in an external app, use IMAP with port 993 and SMTP with port 465 or 587.
To use Builderall professional email with external DNS, configure MX, CNAMEs, and SPF using the correct pool.
To send campaigns through MailingBoss, first create the professional email. Then validate the domain and the sender inside MailingBoss.
When in doubt, do not change the Name Servers of a domain that already has professional email or other active services. Use IP connection.