Resource Records
When the zone is set up for monitoring the DNSMonitor configuration engine will take care of the base configuration which includes DNS records that are usually present in the zone apex. This makes the monitoring setup easy and painless for our customers, but they might want to add resource records to make the monitoring of the domain complete.
The configuration of Resource Records as easy as the initial domain configuration. Only the Name and Resource record type is required and the configuration engine manages the rest.
The monitoring service currently supports the following records.
Certificate Authorisation Authority record.
A Host resource Record can be a CNAME record or it can be an A and/or AAAA record(s). The configuration engine will find out and when configuration is completed it will be presented as found.
Name Authority Pointer record. Commonly used Internet telephony applications.
Sender Policy Framework text record. To be used for monitoring of subdomain SPF records and to avoid other generic TXT records.
Service record. Defines the hosts are responsible for certain Internet services of the domain.
TLS Authentication record. In order to trust a TLSA record the zone must be signed with DNSSEC.
Generic text resource record.
All resource records is monitored using the same principle. After the name and type is looked up, its response in then compared to the value that was looked up during configuration, which is stored in the DNSmonitor configuration database.
If the zone is signed, all configured Resource Records have their RRSIG validated (require Premium plan or Basic plan with the DNSSEC package).
Note!
Some DNS servers are geo-location sensitive. This means it will respond with different content depending the source IP address of the query. If you know your DNS servers are configured this way it might be an idea to select the monitoring locations accordingly. During the configuration a resource record is looked up from each of the currently selected monitoring locations, which is reported back to the configuration engine and is stored separately in the configuration database (if needed).