[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

4.1 The soa table

The soa table contains one row for each zone for which the server is authoritative.

The default values for the various timer fields are from RFC 1537.

`id INT UNSIGNED NOT NULL'
A unique number identifying this zone. (Auto increment / Primary key)

`origin CHAR(78) NOT NULL'
The name of this zone. (Unique key)
ex: example.com.

`ns CHAR(255) NOT NULL'
The name of the name server that was the original or primary source of data for this zone. (meaningless to MyDNS)
ex: primary.example.com.

`mbox CHAR(255) NOT NULL'
A name which specifies the mailbox of the person responsible for this zone. This should be specified in the wacky mailbox-as-domain-name format where the `@' character is replaced with a dot. (meaningless to MyDNS)
ex: postmaster.example.com.

`serial INT UNSIGNED NOT NULL default '1''
A "version number" for this zone. DNS servers that rely on AXFR for zone transfers use this to determine when updates have occurred. Popular values to use are the Unix timestamp or a date in the form YYYYMMDD. (see section 5.4 Zone transfers).
ex: 20020529

`refresh INT UNSIGNED NOT NULL default '28800''
The SOA record of the primary server is checked every refresh seconds by the secondary servers; if it has changed, a zone transfer is done. (meaningless to MyDNS)
ex: 10800

`retry INT UNSIGNED NOT NULL default '7200''
If a secondary server cannot reach the primary server, it tries it again every retry seconds. (meaningless to MyDNS)
ex: 3600

`expire INT UNSIGNED NOT NULL default '604800''
If for expire seconds the primary server cannot be reached, all information about the zone is invalidated on the secondary servers (i.e., they are no longer authoritative for that zone). (meaningless to MyDNS)
ex: 60400

`minimum INT UNSIGNED NOT NULL default '86400''
The minimum TTL field that should be exported with any RR from this zone.
ex: 86400

`ttl INT UNSIGNED NOT NULL default '86400''
The time interval that this resource record may be cached before the source of the information should again be consulted. Zero values are interpreted to mean that the RR can only be used for the transaction in progress, and should not be cached.
ex: 86400