• Main
• Solutions
  • Converged
  • Wireless
  • Wireline
• Products

  • Provisioning

  • Broadband Command Center
  • Broadband Command Center (Cable Edition)
  • Broadband Command Center (SIP Deployment Solution)
  • Broadband Command Center (Appliance)
  • FastFlow Broadband Provisioning Manager

  • Service Activation

  • Service Activation Center

  • IP Address Management/DNS

  • Address Commander
  • Name Commander
• Downloads
  • Overview
  • Demo Request
  • Add Product License Key
  • Download Products
  • Previous Releases
• Support
  • Overview
  • Knowledgebase
  • Support Request
  • Self-Service Portal
• Training
  • Overview
  • Course Information
  • Course Schedules
  • Location
  • Training Site Attractions
• Corporate

  • Corporate Info

  • About Us
  • The Team
  • Careers
  • Customer Reference

  • Media Center

  • Press Release
  • Events
  • Articles
• Partners
  • Overview
  • Partner Program
  • Become a Partner
  • Partner Portal
• Contact Us

How Name Commander Works

Name Commander centrally manages a large number of BIND or Incognito DNS Commander Controlled Name Servers (CNS) based on operator-defined policies. They are the lookup engines for resolving DNS queries. Through a Synchronization Service and a Puppet that resides within the DNS management architecture, Name Commander directly manipulates the data in the CNSs, with all of the domain and zone changes occurring in real time.

The process for domain management is as follows:

1. Authentication:
   Administrator logs in to the Web Management Console and password authenticates through the End User Management Service (EUMS)
2. Entering domain / zone updates:
   User edits domain or zones from the GUI interface. The updates are communicated to Name Commander via Java API.
3. Database synchronization:
   Name Commander relays the updates into the Central Database that stores all system information including domain, IP address and user management data.
4. Database retrieval: Name Commander Synchronization Service (NCSS) polls the database for changes
5. Controlled Name Server (CNS) updates:
   The CNS is updated with the new information from the database following the procedure below:
   1. Secure Socket Layer (SSL) connection between NCSS and Puppet:
      Name Commander communicates to the CNS' Puppet through a Secure Socket Layer (SSL) pipe. The puppet is provided by Incognito Software and resides within each of the controlled name server environment (or built in, as is the case for Incognito DNS Commander)
   2. Command Issuance for file transfers over SSL:
      Name Commander Synchronization Service (NCSS) issues commands and transfers files (over SSL).
   3. Domain/zone file transfers on DNS servers:
      New data that travels through the SSL pipe is captured and reflected on the name servers

Domain updates can also be done dynamically through the Dynamic DNS (DDNS) protocol when integrated with Incognito Address Commander IP Address Management (IPAM) system and the Broadband Command Center provisioning software's DCHP service (through Address Commander).