|
I recently had problems with a MX record changed by an admin (he manages several domains). We have several domains pointed to gsuite email (Google). If MX records are changed, it is unoticed by end users since they keep using the service as usual and send emails, they just dont receive any more. Once an end user finds out, it is because of non received emails, a problem that could be prevented. It would be great to check MX records of a domain to find any change... hope it makes it to an upcoming version of PA :) |
|
Update: the log file monitor is not appropriate as workaround, but File & Directory Change monitor is, unchecking file date and checking MD5 hash value to detect any change and using script: nslookup -querytype=mx mydomain.com >> domainrecords.txt nslookup -querytype=txt mydomain.com >> domainrecords.txt nslookup -querytype=cname mydomain.com >> domainrecords.txt |
|
Workaround while the feature comes up: nslookup -querytype=mx domain.com >> logfile.txt Then run log file monitor over logfile.txt it wont check if there are MX records that shouldnt be, but it can check if a given MX record is found... |