Docs → Guides & how-tos
Requesting hosting & DNS changes
How to ask us for a hosting or DNS change, what to include so it happens right the first time, and what happens after you hit send.
Last updated: August 2026
At a glance
- Send requests via the HelpDesk portal or support@betaboxts.com
- Include: domain, exact record, the change, and why
- Something down right now? Call (931) 355-7256
- Third-party requests always get verified with you first
What counts as a hosting or DNS change
DNS records
A, CNAME, MX, TXT — new records or edits to existing ones.
Subdomains
New subdomains for apps, campaigns, or vendor tools.
SSL certificates
New certs, renewals, and fixing certificate warnings.
Redirects
Old URLs to new ones — one page or a whole domain.
Server configuration
PHP versions, resource limits, cron jobs, server settings.
Environment moves
Staging to production, host-to-host migrations.
If your request does not fit a box above, send it anyway — sorting it is our job, not yours. The one thing we ask: one request per change where possible, so nothing gets lost inside a bundle.
What to include
The domain and record — “the MX records for betabox-client.com” beats “our email thing”.
The exact change — Old value → new value where you have it. Screenshots welcome.
The reason — If the “why” does not match the “what”, we ask — that catches typos and fraud alike.
The deadline — “Before the campaign launches Thursday” changes how we schedule it.
What happens next
1
A human confirms
We acknowledge the request and flag anything risky before touching production. Odd-looking requests get a phone call, not blind execution.
2
Change gets made
Scheduled around your deadline. Anything that could take a site offline gets an agreed window with you first.
3
You get the outcome
What changed, when, and what to expect — DNS propagation runs on its own schedule, and we tell you what that means for your change.
Security note: We never action DNS changes requested by an unknown third party without confirming with you directly. If someone pressures you to “just forward this to your IT company”, that is a red flag — send it to us and we will verify it. And if something is down right now: call (931) 355-7256 and say it is urgent.
Common questions
How long do DNS changes take to show up?+
Propagation timing depends on the record’s TTL and the resolvers between you and it — we tell you what to expect for your specific change when we make it.
Can you deal directly with our registrar or old host?+
Yes, with your authorization — that is usually faster than relaying instructions through you.
Who on our team is allowed to request changes?+
Your authorized contacts. If someone new should have that ability, an existing authorized contact tells us — that keeps social engineering out of your DNS.
Related docs
Incident response →
What happens when something is genuinely wrong.
Support escalation →
How to raise the temperature on a stuck request.
Maintenance windows →
How planned work reaches you before it happens.
Not sure how to phrase it?
Send it messy — sorting requests is our job, not yours.