Automated Njalla DNS Change Handoff
Every morning, WebRun opens Njalla, reads the current DNS and nameserver records for each domain, compares them against what a new site or service actually needs, writes up the exact change required in a Google Drive doc, and hands it to a teammate in Slack to make.
How do I hand off a Njalla DNS change to my team without guesswork?
WebRun reads the current DNS and nameserver records for your Njalla domains every morning, compares them against what a new site or service actually needs, and writes up the exact change required in a Google Drive doc. It hands that doc to a teammate in Slack to execute, so DNS changes stay specific and reviewed instead of guessed under pressure.
- DNS changes get a written, specific request instead of a guess
- A teammate always makes the actual edit, never WebRun
- Every change request is documented in Drive before it's made
Built for Privacy focused site owners · small dev teams · system administrators · agencies managing client domains
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
njal.lain a real browser with your saved login - no setup, no API keys. -
1
Njalla - read current DNS and nameserver records
njal.la
WebRun reads current DNS and nameserver records in Njalla. - Open the Njalla panel and read current DNS and nameserver records for each domain
- Compare them against what the new site or service requires
- Note exactly which records are missing or wrong
Done when Every domain's current records are checked against what's needed.
-
2
Google Drive - write up the exact change needed
drive.google.com
WebRun writes up the exact DNS change needed in Google Drive. - Write up the exact records to add, remove, or change in a change request doc
- Include the domain, the record type, and the correct value
- Leave the doc ready for a teammate to execute
Done when A clear, specific change request doc exists for any domain that needs an update.
-
3
Slack - hand it to a teammate to make
slack.com
WebRun hands the change request to a teammate in Slack. - Post the change request doc to the team channel
- Tag the teammate who manages DNS changes
- Never edit the DNS records directly. WebRun only prepares the request
Done when A teammate has a clear, actionable DNS change request in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun change the DNS records itself?
No. WebRun only reads current records and writes up exactly what needs to change. Making the actual edit in Njalla stays a manual step a teammate takes.
Why not just edit the record directly, since it reads the account anyway?
DNS changes can take a site offline if done wrong. Writing a clear, specific request and handing it to a person keeps a human in control of anything that touches live DNS.
What does the handoff actually include?
The domain, the exact record type, and the correct value needed, written up in a doc so the teammate making the change has everything in one place.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.