Adding DNS/DHCP Servers to Address Manager - BlueCat Address Manager - 9.2.0

Address Manager Administration Guide

Locale
English (United States)
Product name
BlueCat Address Manager
Version
9.2.0

Place a configured DNS/DHCP Server under Address Manager control, or edit properties of a BDDS already under BAM control.

Prerequisites
Before attempting to add a DNS/DHCP Server to Address Manager, you must complete the following:
  • Assign an IPv4 address to the Service interface (eth0)
  • Set the default gateway
  • If using Dedicated Management (multi-interface DNS/DHCP Server appliances only), an IPv4 address must be assigned to the Management interface (eth2) and Dedicated Management must be enabled
For details, refer to Getting started with DNS/DHCP Servers.

Add a DNS/DHCP Server to Address Manager to control services, deployment, and server operations from the BAM user interface. From the Add Server page you can set name of the hostname, upgrade the server, configure the xHA Backbone, configure an optional IPv6 address, and set validation options.

Certain fields and options of the Add Server page will only be available depending on the number of network interfaces of your DNS/DHCP Server.

If editing a DNS/DHCP Server, you can only change the server name, Management interface address (if the server is disabled), host name, and deployment validation options. The Edit Server page is the same for 2, 3, or 4-port DNS/DHCP Servers. Certain server properties are only available when the server is disabled or not under BAM control.

Note: BlueCat VM customers should refer to the VM Installation Guide for complete information on supported VM hypervisors including VM setup and configuration for your particular VM environment.
Attention: If you require NIC bonding/network redundancy in your network environment, you will need a 4-port DNS/DHCP Server appliance. Network redundancy through port bonding is only supported on physical DNS/DHCP Server appliances, not on virtual interfaces from DNS/DHCP Server VMs.
Note: If you require VLAN interfaces in your network environment, you should refer to VLAN tagging for complete information on requirements and configuration.

To add or edit a DNS/DHCP Server to Address Manager:

  1. From the configuration drop-down menu, select a configuration.
  2. Select the Servers tab. Tabs remember the page you last worked on, so select the tab again to ensure you're on the Configuration information page.
  3. Under Servers, click New.
    If editing a server, click the server name. From the Details page, click the server name menu then select Edit.
  4. Under Server, complete the following:
    • Profile—select the model number of your DNS/DHCP Server appliance from the drop-down menu.
      Note: If you want to use the monitoring service, you must first enable SNMP on each DNS/DHCP Server you intend to monitor. For details, refer to Enabling monitoring services for DNS/DHCP Server.
    • Name—enter the name for the server. This name is used only in the Address Manager user interface and isn't associated with deployed DNS data.
    • Management Interface—enter the IPv4 address configured on the eth0 interface in the BDDS Administration Console. If Dedicated Management is enabled, enter the IPv4 address configured on the eth2 interface.
      Note: IPv6 addresses can't be used to connect to an DNS/DHCP Server appliance.
      Note: If editing a server, the Management Interface field is only available after you have first disabled the managed DNS/DHCP Server. If you want to change the IPv4 address of the Management interface (eth2), you must first re-configure the IPv4 address of the Management interface using the DNS/DHCP Server Administration Console, disable the server in Address Manager, then edit the server with the new IPv4 address.
    • Hostname—The host name used for the server on the network. For example, myhost.example.com
    • Connect to server—by default, this option is selected. It allows Address Manager to connect to the server once it's added. Deselect this check box if you don't want to connect to the server at this time.
      Note: The Connect to server check box must be selected in order to click the Detect Server Settings button which is required to add the server to Address Manager.
    • Upgrade to latest version—by default, this option is deselected. This provides a safe environment to add a DNS/DHCP Server in Address Manager without applying an unintentional software update. Select the check box only if you want to apply the latest version of DNS/DHCP Server software once the appliance is under Address Manager control.
      Note: BlueCat recommends upgrading the DNS/DHCP Server software only after first adding the server to Address Manager. Add the server without selecting the Upgrade to latest version check box. After the server has been added to Address Manager, upgrade the server software. For details, refer to Upgrading DNS/DHCP Server software.
    • Password—enter the server password. You must enter a password in order to click the Detect Server Settings button. For more information on the default server password, refer to BlueCat default login credentials (you must be authenticated to view this topic).
    • Location(Optional) select a location from the drop-down menu on which the server object that you are adding or editing will be based. The most often used location objects will be shown at the top of the list followed by all other lists in alphabetical order.
  5. Click Detect Server Settings. Address Manager will check the DNS/DHCP Server software version, interface count, state of Dedicated Management, IP address, and redundancy scenario (4-port appliances only).
  6. OPTIONAL: complete the following (available fields depend on the number of interfaces of your DNS/DHCP Server):
    • Service interface—set an IPv4 address and netmask that will be used only for services traffic such as DNS, DHCP, DHCPv6 and TFTP (3 and 4-port appliances only). If Dedicated Management has been previously enabled, you will see the IPv4 address you configured on eth2 in the DNS/DHCP Server Administration Console.
      • IPv6 Address and Subnet—configure an IPv6 address and subnet to the Service interface (eth2). If you assigned an IPv6 address from the DNS/DHCP Server Administration Console during initial set-up of the DNS/DHCP Server, the fields will be automatically populated. For example:
        • IPv6 address: 2001:db8::AC10:FE02
        • Subnet: 64
          Note: The configured IPv6 address is automatically set as the Primary IPv6 address. You must set the Primary IPv6 address BEFORE placing the server under Address Manager control.
          Note: You can't set the IPv6 gateway from the Address Manager user interface. You must configure an IPv6 gateway from the DNS/DHCP Server Administration Console to ensure correct operation of IPv6 functionality.
    • xHA Backbone—select the check box if you want to configure the xHA interface and specify the IPv4 address and netmask to be used.
    • Enable Redundancy—select the check box to enable networking redundancy (4-port appliances only) or deselect to disable network redundancy. From the Scenario drop-down menu, select either Active/Backup or Active/Active (802.3ad).
      Note: You can't enable network redundancy from the Add Server page if any VLAN interfaces are present on the Service interface (eth0). If necessary, remove any configured VLAN interfaces using the DNS/DHCP Server Administration Console, then add the server to Address Manager and enable network redundancy. Once the server is under Address Manager control you can configure VLAN interfaces from the Address Manager user interface (Servers > Service Configuration > Interfaces).

      If you require VLAN Tagging with port bonding, you must first enable bonding then immediately configure VLAN interfaces.

  7. OPTIONAL: Under Monitoring Settings, select the following (only available if the DNS/DHCP Server Monitoring Service is enabled):
    • Using default monitoring setting [Enabled]—selected by default. Leave selected to use the DNS/DHCP Server monitoring settings configured for the configuration.
    • Override global monitoring setting—select to set custom monitoring settings for the server, then select Monitor this Server and configure the following SNMP Parameter settings:
      • Version—select the SNMP version for the monitored servers.
      • Port Number—indicates the SNMP port BAM uses to communicate with the monitored servers. The default port is 161. You can't change the port.
      • Community String—type the SNMP Community String used for authentication and click Add. The Community String appears in the list. You can add up to 100 Community Strings to the list. Strings are used in the order presented in the list. To remove a string, select it from the list and click Remove. To change the order of items in the list, select an item in the list and click Move up or Move down.
  8. Under Validation Options, set the following options to override DHCP and DNS services configuration or DNS zones validation settings configured at the configuration level:
    • Override configuration level DHCP validation settings—select the check box to set DHCP deployment validation options that are specific to the server. If selected, the Enable DHCP configuration validation check box appears.
      • Enable DHCP configuration validation—select the check box to check the syntax of the dhcpd.conf file and validate data prior to deployment from Address Manager.
    • Override configuration level DNS validation settings—select the check box to set deployment validation options that are specific to the server. If selected, the Enable DNS configuration validation and Enable DNS zones validation check boxes appear:
      • Enable DNS configuration validation—select the check box to check the syntax of the named.conf file and validate data prior to deployment from Address Manager.
      • Enable DNS zones validation—select the check box to check the syntax of each DNS zone file and validated data prior to deployment from Address Manager. This is equivalent to setting the -i switch for the named-checkzone tool. If selected, the DNS Zones Deployment Validation Setting section opens on the page.
  9. Under DNS Zones Validation Settings, complete the following:
    • Post-load zone integrity validation—performs syntax checks based on the mode you select for this option. Select one of the following modes:
      • Full—checks for the following conditions:
        • If MX records refer to A or AAAA records, for both in-zone and out-of-zone hostnames.
        • If SRV records refer to A or AAAA records, for both in-zone and out-of-zone hostnames.
        • If Delegation NS records refer to A or AAAA records, for both in-zone and out-of-zone hostnames
        • If glue address records in the zone match those specified by the child.
      • Local—checks for the following conditions:
        • If MX records refer to A or AAAA records, for in-zone hostnames.
        • If SRV records refer to A or AAAA records, for in-zone hostnames.
        • If Delegation NS records refer to an A or AAAA record, for in-zone hostnames.
        • If glue address records in the zone match those specified by the child.
      • Full-sibling—performs the same checks as in Full mode but doesn't check the glue records.
      • Local-sibling—performs the same checks as in Local mode but doesn't check the glue records.
    • None—disables all post-load zone integrity checks.
    • Check names—Checks names. Select Ignore, Warn, or Fail to determine how Address Manager handles conditions found by this check.
    • Check if MX records are IP addresses—checks if MX records point to an IP address rather than an A or AAAA record. This is equivalent to setting the -M switch for the named-checkzone tool. Select Ignore, Warn, or Fail to determine how Address Manager handles conditions found by this check.
    • Check if MX records point to CNAME records—checks if MX records point to a CNAME record rather than an A or AAAA record. This is equivalent to setting the -M switch for the named-checkzone tool. Select Ignore, Warn, or Fail to determine how Address Manager handles conditions found by this check.
    • Check if NS records are IP addresses—checks if NS record point to an IP address rather than an A or AAAA record. This is equivalent to setting the -n switch for the named-checkzone tool. Select Ignore, Warn, or Fail to determine how Address Manager handles conditions found by this check.
    • Check if SRV records point to CNAME records—checks is SRV record point to a CNAME record rather than A or AAAA record. This is equivalent to setting the -S switch for the named-checkzone tool. Select Ignore, Warn, or Fail to determine how Address Manager handles conditions found by this check.
    • Check for non-terminal wildcards—checks for wildcards in zone names that don't appear as the last segment of a zone name: for example, mail.*.example.com. Non-terminal wildcards are permissible, but you may want to be alerted to their presence. This is equivalent to setting the -W switch for the named-checkzone tool. Select Ignore or Warn to determine how Address Manager handles conditions found by this check.
    For the preceding options, Ignore, Warn, or Fail have the following effects:
    • Ignore—Ignores the condition, so it isn't logged in the Zone Validation server log. Deployment proceeds with the zone data containing the condition.
    • Warn—Logs the condition in the Zone Validation server log. Deployment proceeds with the zone data containing the condition.
    • Fail—Logs the condition in the Zone Validation server log. Deployment fails. The existing DNS data is left in place and the new data isn't deployed.
  10. Under Kerberos Service Principal, set the DNS and DHCP service principals:
    • Enable DNS Service Principal—select to specify the security credential for the DNS service to use to authenticate keys requested by the GSS-TSIG protocol. When you select this check box, Realm and Principal fields appear. Select a Kerberos realm and service principal from the Realm and Principal drop-down menus.
    • Enable DHCP Service Principal—select this check box to specify the security credential for the DHCP service to use to authenticate keys requested by the GSS-TSIG protocol. When you select this check box, Realm and Principal fields appear. Select a Kerberos realm and service principal from the Realm and Principal drop-down list.
  11. OPTIONAL: Under HSM Support, complete the following:
    Note: In order to enable HSM support on managed DNS/DHCP Servers, you must have previously created an HSM configuration in Address Manager. For complete information on configuring HSM, refer to Configuring HSM.
    • Select the check box, Enable HSM Support. The Add Server page refreshes to show your HSM configuration and a drop-down menu of HSM servers.
    • From the HSM Servers drop-down menu, select an HSM server and click Add. Repeat this step to add multiple HSM servers.
    • To re-order the hierarchy of the HSM servers in the list, select an HSM server and click Move Up or Move Down. The HSM server at the top of the order will be the Primary; HSM servers below the Primary will be the Secondary, Tertiary. Click Remove to delete an HSM server from the list.

    In the General section of the Details tab, you will see Enable HSM Support: Yes — this confirms that HSM has been enabled on the managed BlueCat DNS Server. Also, the HSM Servers section lists the HSM server(s) linked to your managed DNS Server.

  12. Under Change Control, add comments, if required.
  13. Click Add or click Add Next to add another server.
Next steps:
  • After you have configured and added a DNS/DHCP Server to Address Manager, you need to deploy the configuration to the DNS/DHCP Server. For details, refer to Managing deployment.
  • After adding or replacing an DNS/DHCP Server, BlueCat strongly recommends backing up the Address Manager database. For details, refer to Address Manager database.