Versions Compared

Old Version 3

changes.mady.by.user Shwetha S

Saved on

compared with

New Version Current

changes.mady.by.user Shwetha S

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can configure DNS Traffic Control servers, pools, and LBDNs on the NIOS appliance. You can define multiple servers, pools, or LBDNs.

...

  1. From the Data Management tab, select the DNS tab -> Traffic Control tab.
  2. Click the server name  to which you want to add the records. Details of the records added to the server are displayed.
  3. Click the arrow next to the Add icon and select the type of record you want to add. (A Record/AAAA Record/CNAME Record/SRV Record/NAPTR Record/Unknown record).
  4. Enter the following information in the Add <Record_Type> Record wizard:
    • For an A record:
      • IP address: Enter an IPv4 address for the A record on the DTC server.
      • Comment: Optionally, enter additional information about the A record.
      • Disable: Select this checkbox to disable the record. Clear the checkbox to enable it.
    • For an AAAA record:
      • IP address: Enter an IPv6 address for the AAAA record on the DTC server.
      • Comment: Optionally, enter additional information about the AAAA record.
      • Disable: Select this checkbox to disable the record. Clear the checkbox to enable it.
    • For a CNAME record:
      • Canonical name: Enter the complete canonical (or official) name of the host.
      • Comment: Optionally, enter additional information about the CNAME record.
      • Disable: Select this checkbox to disable the record. Clear the checkbox to enable it.
    • For a NAPTR record:
      • Service: Specifies the service and protocol used to reach the domain name that results from applying the regular expression or replacement. You can enter a service or select a service from the list.
      • Flags: The flag indicates whether the resulting domain name is the endpoint URI or if it points to another record. Select one of the following:
        • U: Indicates that the output maps to a URI.
        • S: Indicates that the resulting domain name has at least one SRV record.
        • A: Indicates that the resulting domain name has at least one A or AAAA record.
        • P: Indicates that this record contains information specific to another application.
          Leave this blank to indicate that the DNS client must use the resulting domain name to look up other NAPTR records. You can use the NAPTR records as a series of rules that are used to construct a URI or domain name.
      • Order: Select an Integer from 10 to 100, or enter a value from 0 to 65535. This value indicates the order in which the NAPTR records must be processed. The record with the lowest value is processed first.
      • Preference: Select an Integer from 10 to 100, or enter a value from 0 to 65535. Similar to the Preference field in MX records, this value indicates which NAPTR record should be processed first when the records have the same Order value. The record with the lowest value is processed first.
      • REGEX: The regular expression that is used to rewrite the original string from the client into a domain name. RFC 2915 specifies the syntax of the regular expression. Note that the appliance validates the regular expression syntax between the first and second delimiter against the Python re module, which is not 100% compatible with POSIX Extended Regular Expression as specified in the RFC. For information about the Python re module, refer to http://docs.python.org/release/2.5.1/lib/module-re.html.
      • Replacement: This specifies the domain name for the next lookup. The default is a dot (.), which indicates that the regular expression in the REGEX field provides the replacement value. Alternatively, you can enter the replacement value in FQDN format.
      • Comment: Optionally, enter a descriptive comment for this record.
      • Disable: Clear the checkbox to enable the record. Select the checkbox to disable it.
    • For an SRV Record:
      • Display input as: Select the format in which you want the SRV record to be displayed. When you select RFC 2782 format, the appliance follows the service._protocol.name format as defined in RFC 2782. When you select Free format, enter the entire name in the Domain field.
      • Service: Specify the service that the host provides. You can either select a service from the list or type in a service, if it is not on the list. For example, if you are creating a record for a host that provides FTP service, select _ftp. To distinguish the service name labels from the domain name, the service name is prefixed with an underscore. If the name of the service is defined at http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml, use that name. Otherwise, you can use a locally-defined name.
      • Protocol: Specify the protocol that the host uses. You can either select a protocol from the list or type in a protocol, if it is not on the list. For example, if it uses TCP, select _tcp. To distinguish the protocol name labels from the domain name, the protocol name is prefixed with an underscore.
      • Domain: Specify the name determined by LBDN.
      • Preview: After you have entered all the information, this field displays the FQDN, which is the concatenation of the Service, Protocol, and Domain fields.
      • Priority: Select or enter an integer from 0 to 65535. The priority determines the order in which a client attempts to contact the target host; the domain name host with the lowest number has the highest priority and is queried first. Target hosts with the same priority are attempted in the order defined in the Weight field.
      • Weight: Select or enter an integer from 0 to 65535. The weight allows you to distribute the load between target hosts. The higher the number, the more that host handles the load (compared to other target hosts). Larger weights give a target host a proportionately higher probability of being selected.
      • Port: Specify the appropriate port number for the service running on the target host. You can use standard or nonstandard port numbers, depending on the requirements of your network. You can select a port number from the list or enter an integer from 0 to 65535.
      • Target: Enter the canonical domain name of the host (not an alias); for example, www2.corpxyz.com
        In addition, you need to define an A record mapping the canonical name of the host to its IP address.
      • Comment: Enter a descriptive comment for the record.
      • Disable: Clear the checkbox to enable the record. Select the checkbox to disable it.
    • For an Unknown record:
      • Domain name: Enter the complete canonical (or official) name of the host.
      • Comment: Optionally, enter additional information about the CNAME record.
      • Disable: Select this checkbox to disable the record. Clear the checkbox to enable it.
  5. To schedule the change, click Next or ScheduleforLater. In the ScheduleChange panel, select Now to immediately execute this task. Or select Later to schedule this task, and then specify a date, time, and time zone.
  6. Save the configuration and click Restart if it appears at the top of the screen.

...

  1. From the Data Management tab, select the DNS tab -> Traffic Control tab, click the Action icon next to the DTC server and select Edit from the menu.
  2. The DTC Server editor contains the following tabs from which you can modify data.
    • General: This tab displays the Name, Host, Auto-create DTC records, and Comment that you entered while configuring the server. You can enable or disable the server. For information about how to modify the server data, see Managing DNS Traffic Control Objects.  Additionally, specify the Server Name Indication setting:
      • UseAlternateSNIHostname: If the SNI name is different from what is configured in the address field, select this checkbox and enter the required hostname by which an HTTPS health monitor should connect to the server.

    • Health Monitors: Define health monitors for the DTC server:

      1. Click the Add icon. A new row appears in the table.

      2. In Health Monitor, select the monitor type: icmp, http, https, sip, pdp, or snmp.

      3. In Domain Name or IP Address, type either the FQDN or the IP address to monitor.

      4. If required, add more health monitors for the server as described above. You can add up to ten health monitors per server.
        In Health Monitors from Pools, you can see other health monitors assigned to the pools that the server belongs to. The availability requirement for the pools must be set to either “All” or “Any” for you to be able to add server-specific health monitors. For information, see the following section, Configuring DNS Traffic Control Pools.

      5. Save the configuration.

    • Extensible Attributes: Add and delete extensible attributes that are associated with the server. You can also modify the values of extensible attributes. For information, see Managing Extensible Attributes.
  3. To schedule this task, click the Schedule icon at the top of the wizard. In the Schedule Change panel, select Later and enter a date, time, and time zone. The Schedule icon is green when there is a pending scheduled task. For information, see Scheduling Tasks.
  4. Save the configuration.

...