|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
> Do you have any literature about it? I've never heard about testing DNS domains :o)
This is something we're trialling - the idea is to make sure that all of our domains are the same as a 'template'. For example, we make sure that certain fields in our Whois, SOA, NS and MX records have the right information in them. To do this, we give Jenkins a list of our domain names, it then runs a job that generates a series of tests for each domain, performs those tests (generating TAP output) and then reports all of that for us (and sends emails if things are wrong, etc).