NAME

DESCRIPTION

METHODS

->new($confighashref);

"confighashref" is a reference to a hash holding configuration keys. They will be blindly used to create a DNSCheck::Config object, unless one key is "with_config_object". If there is such a key, its value will be used as the DNSCheck::Config object. No check to see if it actually is such an object will be done, so anything that responds to the right methods can be used.

Providing a pre-created config object can be useful when creating and discarding a large number of DNSCheck objects, since config object creation normally stands for the majority of the time it takes to create such an object. Creating the config object once and then providing it to every DNSCheck may save considerable time in the long run. An example if this use can be found in the "dnscheck-dispatcher" application.

->flush()

Flush the internal DNS cache.

->logger()

Return the logger object. It is of type DNSCheck::Logger.

->dns()

Return the DNS lookup object. It is of type DNSCeck::Lookup::DNS.

->asn()

Return the ASN lookup object. It is of type DNSCheck::Lookup::ASN.

->config()

Return the config object. It will be of type DNSCheck::Config unless something different was given to "new" as described above.

->dbh()

Return a live database connection (DBI) object, if database access is configured. If not, returns "undef". If a database connection is configured, it should point at a database with the dnscheck schema loaded, or the first sub-module here to try and use the database will throw an exception and cause the script to die.

This method uses DBI::ping() to determine if a connection is alive or not, so make sure to use a DBI adapter where that isn't a null operation (as it used to be in older versions of DBD::mysql). Also, since the included database schema assumes that the database is MySQL, this method will try to connect to the server five times before it gives up and dies.

->add_fake_glue($zone, $nsname, [$nsip])

Add an item of "fake" glue data. For the given zone, the provided information will be used instead of what can be found live in DNS (if any). If an IP address is provided, it will be used. If not, an attempt to look up addresses for the name will be made. If that attempt fails, the name will be ignored.

->undelegated_test()

This method returns true of any "fake" glue information has been provided.

->zone()

->host()

->address()

->soa()

->connectivity()

->consistency()

->delegation()

->nameserver()

->dnssec()

->mail()

->smtp()

These eleven methods all return properly configured objects of the respective test classes. For more details on how to use the objects, see the documentation on the modules in question. Generally, though, they have a main entry method called "test" that runs all available tests with the arguments given.

The objects returned are created on first request and cached for future use. Use the "flush()" method to discard the existing objects, so that new ones will be created on next request.

EXAMPLES

   use DNSCheck;
   
   my $dc = DNSCheck->new;
   $dc->zone->test("iis.se");
   $dc->logger->dump;

SEE ALSO