Deployment Guide

Configuring DNS on a Linux Server
This section describes the procedure to configure Linux DNS server for Extreme Campus Controller IP
addresses discovery.
1. Configure the Linux DHCP server to include DNS information. In the /etc/dhcp.conf file, add
domain-name-servers and domain-name DHCP options.
subnet 10.2.221.0 netmask 255.255.255.0 {
range 10.2.221.30 10.2.221.130;
option slp-directory-agent true 10.2.221.2;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.6.2;
option domain-name "Availability-221.com";
option routers 10.2.221.1;
default-lease-time 40000;
}
2. Configure the Linux DNS server to include Extreme Campus Controller IP addresses.
Create a file for the domain name configured in dhcp.conf (in this example, "Availability-221.com") as
follows at /var/named/chroot/var/named.
The name of the file should be the following: /var/named/chroot/var/named/
named.Availability-221.com
/var/named/chroot/var/named/named.Availability-221.com
$TTL 86400
@ IN SOA ns1.availability-221.com. hostmaster.availability-221.com. (
2 ; serial #
28800 ; refresh
14400 ; retry
3600000 ; expire
86400 ; ttl
)
IN NS ns1.availability-221.com.
Controller IN A 10.2.221.2
3. Add the domain name to the DNS configuration file (/var/named/chroot/etc/named.conf).
$//
// a caching only nameserver config
//
options {
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
version "Bind";
recursion no;
directory "/var/named";
};
zone "Availability-221.com" {
type master;
file "named.Availability-221.com";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "named.local";
allow-update { none; };
Configuring
DNS on a Linux Server Configuring DHCP, NPS, and DNS Services
50 Extreme Campus Controller Deployment Guide for version 5.46.03