We will migrate DNS Check’s infrastructure to more powerful hardware on Saturday, July 24. The maintenance window will begin at 12 am UTC and end at 1 am UTC.

We anticipate that this migration will cause 10-15 minutes of downtime for our website and API endpoints. Monitoring of some DNS records will also be delayed by up to 15 minutes.

The upgrade will make DNS Check's website snappier and increase the number of DNS records we can monitor. We've grown steadily since our last major hardware upgrade in 2018. We still have spare capacity from the 2018 upgrade but are upgrading now to ensure that we stay well ahead of the growth curve.

Happy New Year! We want to kick off 2021 by announcing some improvements to DNS Check.

1. Extended the Notification History

When troubleshooting an intermittent problem or flapping record, it's useful to see what failures occurred in the past and look for patterns. DNS Check maintains a log of the notifications sent for each monitored DNS record to support that type of troubleshooting. Each record's log can be viewed by clicking its History button.

We're going to replace some of the hardware that runs DNS Check's website on Friday, May 8th, between 4:15 am and 12:15 pm UTC.

A few minutes of degraded performance is expected towards the beginning of this window.

Website downtime is possible, but not expected. If downtime does occur, then it's expected to last approximately 5 minutes.

We're going to perform software updates to DNS Check's website on Sunday, December 30th between 11:00 pm and 11:30 pm UTC. We anticipate that the updates will cause 5-10 minutes of downtime for our website.

If you're using our API for DNS record monitoring, then we recommend scheduling a maintenance window within your monitoring system which covers this window.

Back in 2016, we added support for monitoring wildcard DNS records. Wildcard DNS records are used to serve requests for otherwise non-existent domain names. For example, if you created a wildcard record for *.example.com, but not a foo.example.com record, queries for foo.example.com would receive the IP addresses specified for *.example.com in response.

Today we're pleased to announce that we've extended our support for using wildcards in DNS records monitoring. DNS Check now allows you to specify a wildcard (*) in place of some DNS record values, such as an A record's IP address to indicate that any value is acceptable, but the record must exist.

Wildcard values are supported in the following areas:

• A and AAAA records may have an IP address of * specified.
• CNAME records may have a value of * specified to indicate that they may point to any domain.
• MX records may have an exchange of * specified to indicate that any exchange is acceptable.
• NS records may have a value of * specified to indicate that any name server is acceptable.
• PTR records may have a value of * specified to indicate that any value is acceptable.

We've moved the Sunday, February 25th maintenance window that was announced in the previous post to take place on Monday, February 26th between 16:00 and 17:00 UTC.

The maintenance window was rescheduled so that mitigations for the Spectre and Meltdown vulnerabilities can be put in place at the same time as the hardware upgrade.

We anticipate that this maintenance will cause 5-15 minutes of downtime for our website.

We're going to migrate DNS Check's website to new and more powerful hardware on Sunday, February 25th starting at 1:00 am UTC. We anticipate that this migration will cause 5-10 minutes of downtime for our website.

If you're using our API for DNS record monitoring, then we recommend scheduling a maintenance window within your monitoring system which covers this window.

We just finished refactoring the code that we use for integrating DNS Check with services like Slack and PagerDuty. It felt good to take some of the bespoke code that had accumulated over the past couple years as integrations got added in and generalize it.

These updates will allow us to more easily add and update integrations in the future.

You shouldn't notice any difference in how existing DNS Check integrations work.

We're going to migrate DNS Check's website to new hardware on Thursday, October 13th starting at 12:00 am UTC. We anticipate that this migration will cause 5-10 minutes of downtime for our website.

If you're using our API for DNS record monitoring, then we recommend scheduling a maintenance window within your monitoring system which covers this window.

Wildcard DNS records are used to serve requests for otherwise non-existent domain names.

For example, the following DNS zone file excerpt contains two non-wildcard A records along with a wildcard record:

; Name            Record Type     IP Address
example.com.      A               1.2.3.4
www.example.com.  A               1.2.3.4
*.example.com.    A               5.6.7.8

If you look up the www.example.com A record in the above recordset, you'll receive a response of 1.2.3.4, since explicit records take precedence over wildcard records. If you look up the foo.example.com DNS record, you'll receive a response of 5.6.7.8, since there is only a wildcard record for foo.example.com.

Wildcard DNS records are handy, but how do you monitor them? Two options come to mind: