Domains & DNS
Make DNS changes for customers on their domains.
Overview
DNS turns names into addresses. A records point a name at an IPv4 address; CNAME points one name at another; MX says where mail goes; TXT holds verification text. A wrong record takes a website or email down instantly for everyone. A DNS job is checked by the domain's DNS having changed after you accepted.
Jobs this covers
dom_dns — certificate: Web developer (recommended)
The equipment — what everything does
DNS editor
Add, edit or delete A, AAAA, CNAME, MX and TXT records.
In game: Browser → opsdomains.sa → My domains → the domain → DNS records.
WHOIS
Who owns a domain and when it expires.
In game: opsdomains.sa → WHOIS.
Tools & PPE
Engineer laptop & console cable
Configures routers, NVRs and servers, runs speed tests and opens OPS Hub.
Standalone servers: tools are in your van (OPS Work → My van & tools). Items servers: collect them — and the job’s parts — at an OPS depot.
Step by step
Exactly which record should change.
opsdomains.sa → My domains — the customer's domains appear under your job.
Add or edit the record. A CNAME can't share its name with other records, and the bare domain (@) can't be a CNAME.
Visit the site / send a test email.
Press Check on the job.
Health & safety
Customer data & privacy
Risk: Router settings, passwords and camera footage are private.
Control: Only change what the job needs. Never share Wi-Fi passwords or footage, and log out of customer systems when you finish.
Taking a service down
Risk: A wrong record breaks the customer's website or email.
Control: Write down the old value first and test straight after.
In game you confirm these in a risk assessment before starting. Skipping them on risky work can cause a fall or a shock — and it’s logged as a safety incident.
When it’s not done correctly
Deleting the A record for @
The website stops resolving: ERR_NAME_NOT_RESOLVED.
Changing MX by mistake
Email bounces.
Change made before accepting
The check needs a change after acceptance.