created-at

Initial creation time of this resource. (readonly)

data

The required format of data depends on host-type; see below. (required; read/write)

fqdn

Fully qualified domain name (hostname + domain). (readonly)

host-type

DNS host record type; see below. (required; read/write)

hostname

Any part of a domain in front of the domain itself (aka a subdomain). For example, for a fully qualified domain name of ‘www.example.com’, where the zone domain is ‘example.com’, the hostname would be ‘www’. If there isn’t any hostname in front of the domain name, this should be set as nil or left out. Wildcard hostnames are supported (eg: ‘*’ or ‘*.subdomain’). (optional; read/write)

id

Unique ID for this host. (readonly)

notes

Notes about the host. (optional; read/write)

priority

Indicates the relative priority of two or more of certain host-types, such as MX or SRV. For example, this may be set to 10 for a primary mail server and 20 for a backup server.

ttl

TTL (time-to-live), in seconds. If nil, the record uses the default-ttl value from the zone. (optional; read/write)

updated-at

Last update time of this resource. (readonly)

zone-id

ID of the zone to which this record is attached. (readonly)

Host-type and Data

Zerigo supports a number of different host-types. Valid values are A, AAAA, CNAME, GEO, MX, NS, SPF, SRV, TXT, and URL. For reverse domains, the only valid values are PTR, CNAME, and NS.

host-type should be ‘A’ to set an Address record. This points a full hostname (www.example.com) to a specific IPv4 address (172.16.16.1) which should be in the data field.

host-type should be ‘AAAA’ to set an IPv6 Address record.

host-type should be ‘MX’ to set a Mail eXchange record. This indicates where email for a full hostname (www.example.com) should be delivered — by using a hostname in the data field (mail.example.com). Also see the priority field.

host-type should be ‘CNAME’ to create a Canonical Name record. This points one hostname as an alias to another which should be entered as a hostname in the data field (othername.example.com). The CNAME hostname in the data field should not point to another CNAME record. DNS specifications prohibit having a CNAME on the base domain. Wildcard CNAMEs aren’t blocked, but in certain circumstances can exhibit unexpected behavior; contact support to discuss your use-case.

Use a host-type of ‘GEO’ for GeoDNS records. This would be the root/base domain of a GeoDNS configuration. Additional records will be other various record types. The data field of a GEO record can be left out as it will be automatically managed.

A host-type of ‘NS’ is used to delegate DNS for subdomains. Non-subdomain NS records cannot be set this way. The data field for NS records should be a fully qualified domain name of the target nameserver.

host-type should be ‘PTR’ when the zone is a reverse domain. Reverse domains for both IPv4 and IPv6 are supported and are auto-detected based on the zone’s domain name. The data field for PTR records should be a fully qualified domain name.

A host-type of ‘SRV’ will configure a SeRVice record. The data field should contain the weight, port number, and full domain name, for example: 10 389 ldap.example.com. The priority field is also required.

host-type should be ‘TXT’ to configure a text record. The text itself should be entered in the data field. A common use of this is setting an SPF record for a domain, but see the next paragraph.

Also supported is a host-type of ‘SPF’. Records with SPF content can be entered using either an SPF or TXT record type according to the SPF specifications. SPF is now preferred, but TXT was originally used. Zerigo supports both. For maximum compatibility with email servers across the globe, you may want to consider using both.

Redirects use the special host-type ‘URL’. The data field should be a valid URI.