🥳 Celebrate Our Launch With a $200 LIFETIME Discount OFF The Premium Plan Use: BIRTHDAY2024
This offer expires 9/30/2024, at 11:59 PM EST
Troubleshooting Domains
Fix DNS issues, SSL errors, Cloudflare proxy conflicts, CNAME/A record problems, 404 pages, and domain routing issues in BizStackPro.
Fixing Domain Problems Before They Break Your Website or Funnels
Domain problems can quickly make websites inaccessible, trigger SSL warnings, break funnels, or cause visitors to land on 404 pages instead of the correct content.
BizStackPro domains rely on properly configured DNS records, valid SSL verification, correct routing settings, and clean A or CNAME configurations to function correctly.
Without accurate DNS setup and routing configuration, businesses may experience SSL failures, missing pages, Cloudflare conflicts, broken subdomains, or incomplete domain verification.
This guide explains how to troubleshoot DNS records, fix SSL and routing issues, resolve Cloudflare conflicts, and restore stable domain functionality inside BizStackPro.
Before troubleshooting advanced domain behavior, it helps to understand how DNS records, SSL validation, default page routing, and Cloudflare proxy settings work together inside BizStackPro.
Overview
Domain issues usually come down to DNS accuracy (A/CNAME/AAAA records), SSL issuance, or routing (default page and paths). This guide walks you through a structured way to identify the root cause and fix it fast.
Most common causes: duplicate A/CNAME records, incorrect DNS host/provider, Cloudflare proxy enabled, or missing default page settings.
Source Document: Troubleshooting Domains.
1) Check Your DNS Records (DNS Lookup)
Before changing anything, confirm what the internet currently sees for your domain. A DNS lookup tool can show whether your A/CNAME/TXT records exist, whether they match what BizStackPro expects, and whether there are conflicts.
Use MXToolbox
- Open mxtoolbox.com.
- Select the lookup type you need (DNS, A, CNAME, TXT, MX, etc.).
- Enter your domain and run the lookup.
- Look for duplicates (multiple A/CNAME for the same host) or conflicts (wrong target/value).
Propagation note: DNS updates can take time to spread globally. In many cases it’s quick, but allow up to 24–48 hours for full propagation depending on TTL and registrar/provider.
2) Remove a Domain from BizStackPro
If you need to disconnect a domain (for example, to reconnect cleanly or move it to a different site/funnel), remove it from your BizStackPro Domains settings.
- Go to Settings → Domains.
- Click the three dots next to the domain.
- Select Delete and confirm.
Tip: If you’re troubleshooting, removing and re-adding the domain after correcting DNS can force a cleaner verification flow.
3) What Causes SSL Errors?
BizStackPro can only issue SSL once DNS is correct and the domain points cleanly to the expected destination. SSL errors usually mean something is blocking validation.
Common causes
- Multiple A or CNAME records exist for the same host (duplicate/conflicting records).
- Missing DNS records for the domain/subdomain you connected.
- Conflicting records pointing to different targets/IPs.
- The same host is connected in more than one place (multiple funnels/websites/environments).
- AAAA (IPv6) records interfering with expected A/CNAME behavior.
- The domain is flagged for unsafe content (security scanners may report issues).
Fix mindset: Remove conflicts first (duplicates/AAAA), confirm the domain points to only one place, then allow time for validation to complete.
4) Fix “CNAME / A Record Not Found”
This error means BizStackPro can’t detect the required DNS record. That’s typically caused by adding the record in the wrong DNS provider, a typo in the host/value, or the record not fully propagated yet.
How to resolve
- Confirm which provider hosts DNS (registrar vs Cloudflare vs another DNS host).
- Verify the record host/name and value/target match BizStackPro exactly.
- Remove duplicate/incorrect records, then re-add the correct record.
- Re-check in a DNS tool after a few minutes (and again after propagation time if needed).
- Reconnect the domain in Settings → Domains after DNS is correct.
Avoid this: Adding both an A record and a CNAME for the same host (or multiple A records) can cause verification failures.
5) Troubleshoot 404 Errors
Case 1: Root domain shows 404
If yourdomain.com shows a 404, the domain likely has no default page set.
- Go to Settings → Domains.
- Choose Edit Domain.
- Select a Default Page.
- Save. (If it’s already selected, save again to refresh routing.)
Case 2: A specific path shows 404
If yourdomain.com/home shows a 404, confirm that the page/path exists and the domain assignment is correct.
- Confirm your funnel/website actually uses the path (example: /home).
- Reassign the domain:
- Remove the domain from the funnel/website settings and Save.
- Add it back and Save again.
Case 3: Intermittent 404s
Intermittent 404s often come from a mismatch between www and non-www routing.
- Set a redirect between www.yourdomain.com and yourdomain.com.
- Use Cloudflare (or your DNS/WAF provider) for path-based redirects when needed.
6) Cloudflare Proxy Conflicts (Orange Cloud)
If DNS looks correct but SSL fails, images don’t load, or pages behave inconsistently, Cloudflare’s proxy can be interfering with routing and SSL validation.
Fix: set records to DNS Only
- Log in to Cloudflare and select your domain.
- Go to DNS.
- Edit the A or CNAME record pointing to BizStackPro.
- Change Proxy Status from Proxied (orange cloud) to DNS Only (gray cloud).
- Save, wait a few minutes, then test your domain again.
If you see script errors (example: “appendChild not supported”): Disable proxy for the BizStackPro record (DNS Only), clear cache, and retest the page.
Fix domains faster with a clean DNS checklist
Validate DNS records, remove conflicts, set a default page, and disable Cloudflare proxy when needed so your BizStackPro sites load securely and reliably.
Opens in a new tab.
Frequently Asked Questions
How do I check if my DNS records are correct?
Use a DNS lookup tool (like MXToolbox) to confirm your A/CNAME/TXT records match BizStackPro’s required values and that no duplicates or conflicts exist.
Do I need to buy SSL separately?
No. BizStackPro issues and manages SSL automatically once the domain is connected correctly and DNS is verified.
What does “CNAME / A Record Not Found” mean?
It means BizStackPro cannot detect the required DNS record. Confirm you added the record at the correct DNS provider, the values are exact, and wait for propagation.
How do I fix a 404 on the root domain?
Set a Default Page in Settings → Domains → Edit Domain. If one is already selected, save again to refresh routing.
Why doesn’t my domain work with Cloudflare?
Cloudflare proxy (orange cloud) can interfere with SSL and routing. Set the BizStackPro A/CNAME record to DNS Only (gray cloud) and retest after a few minutes.
Keep your sites secure, fast, and reachable
Clean DNS records and correct routing prevent SSL failures and 404 errors. If you use Cloudflare, switch the BizStackPro record to DNS Only during setup so SSL and verification can complete smoothly.
Fewer errors. Better uptime.
Disclaimer: This site is NOT endorsed by Google, Facebook or YouTube in ANY WAY. All trademarks & Logo / branding are the property of their respective owners. Please Note: This site was created in BizStackPro by Ken George II (An Affiliate of BizStackPro) and may contain affiliate links.
Copyrights 2024 | AllAboutBizStackPro.Com | Pricing | About | Features | All Rights Reserved.