TCP/IP Configuration and Management Manual

Configuration Reference
TCP/IP Configuration and Management Manual—427132-004
A-17
Domain Name Server Files
NS—Name Server
The format of this record is:
[name] [ttl] addr-class NS name-server-name
For example:
IN NS jiffy.kentcomm.com
In the example, note that the name and the ttl fields are empty.
The Name Server record (NS) lists a domain name server responsible for a given
domain.
The first field name lists the domain that is serviced by the listed domain name server.
Each Primary Master server for the domain should have one NS record. Use an NS
RR to specify the name server at the top of the current domain and the servers child
domain. In the latter case, also specify a glue address RR (refer to RFC 1034).
A—Address
The format of this record is:
[name] [ttl] addr-class A address
For example:
eric IN A 128.33.0.14
IN A 11.0.0.87
The Address record (A) lists the address for a given machine.
The name is the machine name and the address is the network address. There
should be one A record for each address of the machine. If the name field is empty, the
name is assumed to be the last name specified in previous lines. When the A RR
refers to a name server, it is also referred to as glue (refer to RFC 1034).
HINFO—Host Information
The format of this record is:
[name] [ttl] addr-class HINFO hardware oper-sys
For example:
sam ANY HINFO TANDEM/VLX GUARDIAN
In the example, note that the ttl field is absent. When you omit the name field, the
name is assumed to be the last name field that was seen. The Host Information
resource record (HINFO) is for host-specific data. This record lists the hardware and
operating system that are running at the listed host. Note that only a single space
separates hardware and oper-sys fields. If you want to include a space in the
machine name, you must enclose the name in quotation marks. Host information is not
specific to any address class, so you can use ANY for the address class. Each host
should have one HINFO record.