Agent functions for DNS agent

Online

Updates one or more name servers with the resource records.

The agent updates the name servers defined in the StealthMasters attribute. If you have not configured this attribute then the agent obtains the name of the master server by sending an Start of Authority (SOA) query. This query retrieves the SOA record of the zone defined in the agent's Domain attribute. This SOA record contains the name of the master server.

The agent creates PTR records for each RR of type A or AAAA if the value of the CreatePTR attribute is true. A prerequisite for this feature is that the same master or stealth server serves the forward (A or AAAA) and reverse zones.

Finally the agent generates an Online lock file to indicate that the resource is online on the current system.

Note:

The DNS agent does not send any update for a resource record if it is already present on the name server.

Offline

Removes the Online lock file.

If attribute OffDelRR is true, offline removes all records that the ResRecord keys define.

Monitor

Returns the ONLINE state if at least one name server reports all mappings that ResRecord defines. The name servers are the master or StealthMaster servers and all the servers for which an NS record for the zone exists.

The monitor entry point also sends periodic refresh requests to DNS server if the RefreshInterval attribute is set.

Clean

Removes the Online lock file, if it exists. If attribute OffDelRR is true, clean removes all records that the ResRecord keys define.

Open

Removes the Online lock file if the resource is reported online on another node inside the cluster to prevent concurrency violation. If the lock file exists, at least one name server has to report all the records that the ResRecord attribute defines. If all the name servers fail to report all the records, the agent function removes the Online lock file.

Action

Different action agent functions follow:

  • keyfile.vfd

    This action entry point checks if the key file as specified in the TSIGKeyFile attribute exists either locally or on shared storage.

  • dig.vfd

    This action entry point checks if dig and nsupdate binaries exist and are executable.

  • master.vfd

    This action entry point checks if stealth masters are able to reply to SOA query for the configured domain.