Home / Ongoing Work / Integrations & Automation / Registrar-level DNS & nameserver changes

We make DNS and nameserver changes directly at your domain registrar — adding, correcting, or removing records — through access you grant at the registrar level, since we manage the configuration, not your registrar account itself or your ownership of the domain.

SAS-012

Registrar-level DNS & nameserver changes

Specific DNS or nameserver changes made carefully, with the prior setup documented first.

$109.32 delivered in 48 hours
Needs DNS access and Sub-account invite. Create a limited sub-account — we never ask for your own password.
  • 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 domain registrar’s DNS management, or the registrar’s own delegated-access method if available
  • 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 specific DNS records or nameservers changed at your registrar This fix covers it
You want DNS migrated to Cloudflare specifically, not just changed at your current registrar Cloudflare DNS migration from registrar
You want Google Workspace mail routing configured, which involves specific DNS records Google Workspace mail routing for domain, the more specific, guided version of this for that purpose
You’re not sure what DNS changes you actually need, just that something needs fixing Worth describing the underlying goal, so we can determine the correct records needed

What we do

  1. Confirm the exact DNS or nameserver changes needed
  2. Document current records before making any change, as a safety reference
  3. Implement the changes at your registrar
  4. Verify the changes propagate and resolve correctly
  5. Test that dependent services (website, email) continue working correctly
  6. Provide a written summary of what was changed

What is included

  • DNS or nameserver changes implemented accurately at your registrar
  • A documented record of the prior configuration for reference
  • Verified propagation and correct resolution
  • A written summary of what was changed

Not included

  • Cloudflare-specific DNS migration, a separate, related fix if that’s what you actually need
  • Broader mail routing setup, a separate, related fix if that’s the underlying goal
  • Resolving an issue with the registrar’s own account access or billing
  • Ongoing DNS management as a standing service

Questions about this fix

Is this risky? Could it break my website or email?

DNS changes done carelessly can genuinely disrupt your site or email, which is exactly why we document the existing configuration first and verify each change resolves correctly before considering it complete.

How long do DNS changes typically take to take effect?

Propagation can take anywhere from a few minutes to about 48 hours depending on various technical factors, which is why we'd plan around lower-traffic timing where the change is significant.

Do you need my registrar account password?

We ask for whatever access is genuinely needed — many registrars support adding a collaborator or delegate rather than requiring your full account password, which we'd use where available.

Can I undo a DNS change if something goes wrong?

Yes, we document the prior configuration specifically so a rollback is straightforward if genuinely needed, though careful verification aims to make that unnecessary.

Is this different from migrating my DNS to Cloudflare?

Yes — this makes changes within your current DNS setup wherever it's hosted, while a Cloudflare migration moves DNS management to Cloudflare entirely, a larger, more involved change.

Registrar-level DNS & nameserver changes
$109.32 · delivered in 48 hours · needs DNS access, Sub-account invite

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.

See care plans

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.