Reset Search



How To Configure an AP to find the IdentiFi Wireless Controller from a DNS server entry.

« Go Back


TitleHow To Configure an AP to find the IdentiFi Wireless Controller from a DNS server entry.
How To Configure an AP to find the IdentiFi Wireless Controller from a DNS server entry.  
  • IdentiFi
  • All Access Points
  • All Firmware
  • Controller.Domain
  • DNS
  • Windows 
  • Linux
Windows - To configure DNS for Wireless APs discovery:
  1. Click Start, point to All Programs, point to Administrative Tools, and then click DNS.
  2. Select the domain.
  3. In the Action menu, select New Domain. The New DNS Domain window is displayed.
  4. In the New DNS Domain window, type the name for the new domain.
  5. Restart the service. The new domain is displayed as the child domain.
  6. Right-click the new domain name, and select New Host A. The New Host window is displayed.
User-added image
  1. In the Name text box, type Controller (IP interface selected on the controller for AP Registration).  The  Fully Qualified Domain Name of the Network the controller is installed on ( FQDN) name should be "", for example: 
  2. In the IP address text box, type the Extreme Wireless Appliance’s Management IP address. ( The IP of the Topology with Management checked. ) 
  3. Select Create associated pointer (PTR) record checkbox.
  4. Click Add Host. The new host is displayed in the right pane of the screen.
  5. Exit out.
  6. Open a command prompt and enter nslookup controller to confirm it's returning back the correct IP of the controller.
  7. NOTE : If there are multiple controllers deployed or being deployed, a DNS entry for each additional controller is needed.  The additional controller entry will be the same as in step 7 but the IP will be the IP of the additional controller. ( step 8 ) 
Linux - To configure DNS for Wireless APs 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 netmask {
option slp-directory-agent true;
option subnet-mask;
option domain-name-servers;
option domain-name "";
option routers;
default-lease-time 40000;
  1. Configure the Linux DNS server to include IdentiFi Wireless Appliance IP addresses. Create a file for the domain name configured in dhcp.conf (in this example, "") as follows at /var/named/chroot/var/named. The name of the file should be the following: /var/named/chroot/var/named/
$TTL 86400
 2 ; serial #
 28800 ; refresh
 14400 ; retry
 3600000 ; expire
 86400 ; ttl
Controller IN A
  1. 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 "" {
 type master;
 file "";
zone "" {
type master;
file "named.local";
allow-update { none; };
  1. Confirm that DNS service is running.
ps -ef | grep named

named 10023 1 0 Feb18 ? 00:00:00 /usr/sbin/named -u named -t /var/named/chroot
root 7687 7531 0 22:14 pts/982 00:00:00 grep namedjavascript:void(0)
  1. Verify that the domain name is configured properly.



Additional notes
Manual Configuring DHCP, DNS, and IAS Services - (requires Extranet log in):

DHCP Informs must still pass between the DHCP server and AP in order for DNS discovery to work, see: Access points failing the IdentiFi Controller discovery process



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255