We manage DNS zone records directly through your hosting control panel — adding, correcting, or removing A, CNAME, MX, TXT, and other record types — for hosts where DNS is managed within the same control panel rather than at a separate registrar or DNS provider.
DNS zone record management at host
DNS records corrected right inside your control panel, with the prior zone documented first.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to your hosting control panel’s DNS zone management
- A clear list of the specific DNS changes needed
- Confirmation of your preferred timing, given DNS changes can take time to propagate
This or something else?
| You need DNS records changed within your hosting control panel’s own DNS management | This fix covers it |
| Your DNS is managed at your registrar or a separate provider, not within your hosting control panel | Registrar-level DNS & nameserver changes, in the Integrations & Automation bucket, the equivalent for that setup |
| You want DNS migrated to Cloudflare specifically | Cloudflare DNS migration from registrar |
| You’re not sure where your DNS is actually managed | Worth confirming this first — we can help identify it before proceeding with the correct approach |
What we do
- Confirm the exact DNS changes needed
- Document current records before making any change, as a safety reference
- Implement the changes within your control panel’s DNS zone editor
- Verify the changes propagate and resolve correctly
- Test that dependent services (website, email) continue working correctly
- Provide a written summary of what was changed
What is included
- DNS zone changes implemented accurately within your control panel
- A documented record of the prior configuration for reference
- Verified propagation and correct resolution
- A written summary of what was changed
Not included
- Registrar-level nameserver changes, a separate, related fix if that’s where your DNS actually lives
- Cloudflare-specific DNS migration, a separate, related fix
- Resolving an issue with the control panel’s own access or your hosting account
- Ongoing DNS management as a standing service
Questions about this fix
How do I know if my DNS is managed here or at my registrar?
If your hosting control panel has a DNS zone editor showing your records, that's likely where DNS is actually managed — if you're unsure, we can help confirm this before proceeding with whichever is the correct approach.
What's the actual risk of doing this within my own control panel?
A DNS mistake made carelessly here can disrupt your site or email just as easily as one made at a registrar, which is why we document the existing zone before touching anything and verify each change resolves correctly before calling it done.
Does propagation work any differently for zone changes made inside a control panel?
Not meaningfully — the same general propagation window applies regardless of where the record actually lives, so we'd still plan around lower-traffic timing for anything significant.
What's my fallback if a change made here causes a problem?
The prior zone configuration is documented specifically so it can be restored quickly if genuinely needed, though careful verification during the change is meant to make that a rare, backup option rather than routine.
What if my control panel's DNS editor is more limited than what I actually need?
Some control panels offer a genuinely limited DNS editor compared to a dedicated DNS provider — if that's the case, migrating DNS management to a more capable provider like Cloudflare might be worth considering as a separate, related step.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.