Notifications
Last updated
Last updated
DNSControl's "notifications" feature will log push
changes to other services in real time. Typically this is used to automatically announce DNS changes in a team chatroom. The functionality is implemented using the open source library, which knows how to communicate to many different systems. Some additional services are provided natively, see the .
Notifications are configured in the creds.json
file, since they often contain API keys or other secrets. The notifications
key lists the notification service and options.
If you want to send a notification, add the --notify
flag to the dnscontrol preview
or dnscontrol push
commands.
Below is an example where we add foo
and display the notification output.
In case of dnscontrol preview
:
The notification output
In case of dnscontrol push
:
The notification output
DNSControl supports various notification methods via Shoutrrr, including email (SMTP), Discord, Pushover, and many others. For detailed setup instructions, click on the desired service:
Configure shoutrrr_url
with the Shoutrrr URL to be notified.
Configure slack_url
to this webhook. Mattermost works as well, as they share the same api,
Configure teams_url
to this webhook.
Configure telegram_bot_token
and telegram_chat_id
to these values.
This is Stack Overflow's built in chat system. This is probably not useful for most people.
Configure bonfire_url
to be the full url including room and api key.
The above list is accurate as of 2024-Dec. The compete list and all configuration details are in the .
To use the Slack integration, you need to create a webhook in Slack. Please see the or the
To use the Teams integration, you need to create a webhook in Teams. Please see the
To use the integration, you need to create a Telegram bot and obtain a Bot Token, as well as a Chat ID. Get a Bot Token by contacting , and a Chat ID by contacting .