Configuring a forward lookup zone in Unix

Content Platform S Series Node Help

Version
4.0.0
Audience
anonymous
Part Number
MK-HCPS027-02

With BIND in Unix, zones are defined in the /etc/named.conf file on the DNS servers. In this file, the statement that defines the forward lookup zone to be used for an S Series Node must include:

  • A domain name:
    • If the zone is specifically for an S Series Node, the domain name looks something like s-node-1.example.com.
    • If you're using an existing domain, the domain name looks something like example.com.
  • The zone type (master).
  • The name of the file containing the A records for the zone. The A records specify the host entries for the zone.

    Each A record for an S Series Node associates an S Series Node interface or the wildcard (*) with the IP address of one of the S Series Node server modules on one of the S Series Node networks.

    Each fully qualified domain name that can be used for access to an S Series Node is the concatenation of the hostname in an A record with the specified domain name. For example:

    • If the domain name is s-node-1.example.com, the hostname for the Management Console is admin by itself.
    • If the domain name is example.com, the hostname for the Management Console is admin.s-node-1.
  • A specification not to allow dynamic updates of the A records.

Here's a sample zone statement that defines a forward lookup zone specifically for the S Series Node with domain name s-node-1.example.com:

zone "s-node-1.example.com" {
    type master;
    file "/var/named/data/s-node-1.example.com";
    allow-update {none;};
};

Here are sample contents for the file named in the zone statement above:

$TTL 900
@    IN SOA dnsserver.example.com. dns-admin.example.com. (
      1412260762   ; serial
      10800        ; refresh  (3 hours)
      15           ; retry    (15 seconds)
      304800       ; expire   (1 week)
      10800        ; minttl   (3 hours)
     )
; Name Servers
@     IN           NS          dnsserver.example.com.
;Zone Data

admin              IN     A    10.0.0.3
admin              IN     A    10.0.0.4
mapi               IN     A    10.0.0.3
mapi               IN     A    10.0.0.4
hs3                IN     A    10.0.0.3
hs3                IN     A    10.0.0.4

In the sample file above, the admin, mapi, and hs3 hosts are all associated with the virtual IP addresses of the server modules on the access network.

If the forward lookup zone is not specifically for the S Series Node, the A records in the file look something like this:

admin.s-node-1     IN     A    10.0.0.3
admin.s-node-1     IN     A    10.0.0.4
mapi.s-node-1      IN     A    10.0.0.3
mapi.s-node-1      IN     A    10.0.0.4
hs3.s-node-1       IN     A    10.0.0.3
hs3.s-node-1       IN     A    10.0.0.4