NS1 Automated Weekly DNS Scorecard
Every Monday, WebRun opens the NS1 portal, reads query volume and uptime for every managed zone, saves the scorecard as a dated file in Google Drive for a running history, and posts the same summary to Slack flagging any zone with an unusual pattern.
How do I track NS1 DNS query volume and uptime every week?
WebRun reviews every NS1 managed zone each Monday, reading query volume and uptime for the week. It saves the scorecard as a dated file in Google Drive for a running history and posts the same summary to Slack, flagging any zone with an unusual pattern, so a DNS performance problem gets noticed before it affects traffic.
- Every managed zone gets a weekly query volume and uptime review
- Unusual patterns get flagged before they affect traffic
- A running performance history builds up in Drive automatically
Built for DevOps teams · platform engineers · enterprise IT teams · site reliability engineers
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
ns1.comin a real browser with your saved login - no setup, no API keys. -
1
NS1 - review query volume and uptime
- Open the NS1 portal and review every managed zone
- Read query volume and uptime for the week
- Note any zone with an unusual pattern
Done when Every zone has a week's query volume and uptime reading.
-
2
Google Drive - save the scorecard
drive.google.com
WebRun opens Google Drive to save the scorecard. - Save the scorecard as a dated file in your shared Drive folder
- Keep prior weeks' scorecards for a running history
Done when This week's scorecard is saved to Drive.
-
3
Slack - post the scorecard
slack.com
WebRun opens Slack to post the scorecard. - Post the scorecard to your infrastructure channel
- List every zone with its query volume and uptime
- Flag any zone with an unusual pattern
Done when The team has this week's DNS scorecard 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
Will it change a DNS record or traffic steering rule on its own?
No. WebRun only reads query volume and uptime data and reports it. Changing a DNS record or a traffic steering rule always stays a manual step in NS1.
What counts as an unusual pattern?
A clear jump or drop in query volume, or any dip in uptime, compared to that zone's normal week. It's flagged for a look, not acted on automatically.
Does the scorecard cover every managed zone?
Yes. It reviews every zone under the account each week, not just your primary domain.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.