Infrastructure records
Plan a DNS Change Around Its TTL
A change window that accounts for caching, rollback, and resolver behavior, with the checks that prove the new record is actually being served.
Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.
Delegation playbook
On this pageJump to section
A DNS edit takes seconds. The change takes as long as the old record lives in caches. Teams that treat the edit as the change window end up debugging a rollout that is still partly on the old address.
The procedure below is deliberately conservative. It is written for a small team where the same person prepares the change, watches it, and answers the phone if something breaks.
Treat TTL as part of the window
Look up the current TTL for every record you plan to touch. The realistic propagation window is at least that long, and often longer because some resolvers ignore low TTLs.
If the current TTL is 24 hours, a Friday afternoon cutover is not a one-hour event. Either lower the TTL well in advance or accept a multi-day window with both values live.
Write the window in the change ticket in plain language: when the edit happens, when most clients should see the new value, and when you will consider the change complete.
Lower the TTL before the cutover
Reduce the TTL to a small value at least one old-TTL period before the change. If the record currently has a one-day TTL, lower it on Monday for a Wednesday cutover.
Confirm the lower TTL is actually being served before you rely on it. A record edited in the wrong zone or hidden by a provider proxy will not behave as expected.
Keep a note of the original TTL so you can restore it afterwards.
Prepare the record pair and the rollback
Write the exact old and new values, including trailing dots where the zone file requires them. A missing dot has caused more outages than most other DNS mistakes.
Prepare the rollback edit before the change, and make sure the person on call can perform it without hunting for credentials.
If the record is proxied by a CDN, record whether the proxy is on or off. Changing the origin while the proxy setting stays on produces a different failure than changing the address itself.
Verify from more than one place
Check the authoritative name servers first, then a public resolver, then the office network. Each layer can cache differently.
Use a query that shows the answering server and the TTL. A cached answer with a long remaining TTL tells you the change has not reached that resolver yet, which is different from a wrong record.
Test the service, not just the record. A correct A record pointing at a host with the wrong certificate still fails for users.
Watch the window and restore the TTL
Keep the ticket open through the propagation period. Monitor the service, the error rate, and the support queue. Note the time each resolver switched.
When the window closes, restore the original TTL. Leaving a one-minute TTL in place is a common cause of resolver load and unexpected query costs.
Attach the query output, the timestamps, and the rollback decision to the ticket. The next change will start from that evidence.
Operating brief
What this guide should help you decide
Routine intake, status updates, records, screenshots, and documentation upkeep.
Approvals, risky system changes, security decisions, and final technical judgment.
How to use this guide
Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.
Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.
Workflow
Recommended operating workflow
Define the request
Write what plan a dns change around its ttl means in your company, where requests enter, and what finished work looks like.
Limit the access
Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.
Run a pilot
Use a two-week sample period so the manager can review accuracy before expanding the workflow.
Review patterns
Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.
Decision rules
| Question | VA fit signal | Escalate when |
|---|---|---|
| Is the work repeatable? | The same request appears weekly and can be described in steps. | The request changes business policy or system design. |
| Can quality be reviewed? | The manager can inspect the output without redoing the work. | Only a senior technical person can judge correctness. |
| Is access contained? | The assistant can work with read-only or role-limited access. | Admin rights, customer data, or security settings are involved. |
Delegation checklist
- Write the intake source, expected output, and manager review cadence.
- Confirm the assistant has only the permissions needed for the workflow.
- List the events that require escalation before work continues.
- Track examples for two weeks before changing the workflow.
- Save examples of good and bad outputs so the assistant has concrete references.
- Review the workflow monthly and remove permissions that are no longer needed.
Example first-week agenda
Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.
What to review before delegating
Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.
What should an IT virtual assistant handle first?
Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.
Get free IT support review