Versions Compared

Key

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

...

  • Type: The type of record.
  • Data: The data that the record contains. For a NAPTR record, this field displays the following data: Order, Preference, Flags, Services, REGEX, and Replacement.
  • Comment: Comment that was entered for the record.
  • TTL: The TTL (time-to-live) value of the record.
  • Disabled: Indicates if the record is disabled.

You can do the following:

  • Click the Add icon to add a DTC record.
  • Select a record and click the Edit icon to edit the configuration. You can also click the Action icon  next to the record and select Edit from the menu.
  • Select a record and click the Delete icon to delete it. You can also click the Action icon  next to the record and select Delete from the menu.
  • Create a quick filter to save frequently used filter criteria. For information, see Using Quick Filters.
  • Click the Export icon to export the list of DTC records to a .csv file.
  • Click the Print icon to print the list of DTC records.

...

      • UseAlternateSNIHostname: If the SNI name is different from what is configured in the address field, select this check box 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 Configuring DNS Traffic Control Pools.

      5. Save the configuration.

    • ExtensibleAttributes: Add and delete extensible attributes that are associated with the server. You can also modify the values of extensible attributes. For information, see Using Extensible Attributes.

3. To schedule this task, click the Schedule icon at the top of the wizard. In the ScheduleChange 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.

Anchor
Configuring DNS Traffic Control Pools
Configuring DNS Traffic Control Pools
Anchor
bookmark2125
bookmark2125
Configuring DNS Traffic Control Pools

...

    • Display Name: Enter a display name for the LBDN.
    • Patterns: Click the Add icon to add an LBDN pattern. For more information, see Configuring LBDN Patterns.
      To delete an LBDN pattern, select the check box next to the pattern and click the Delete icon.
    • Load Balancing Method: From the drop-down list, select the method you want to use for load balancing. You can select one of the following: Global Availability, Ratio:Fixed, Round Robin, and Topology. The default is Round Robin. For more information about the load balancing methods, see Load Balancing Methods for DNSTraffic Control.
      • Topology Ruleset: This is displayed only when you select the Topology load balancing method. In the drop-down list, only the topology rulesets with the Pool destination type are displayed. Select a topology ruleset for the Topology load balancing method. For more information, see Defining Topology Rulesets.
    • Persistence: Select this check box and enter a value greater than zero seconds to enable persistence for the LBDN. You can specify a period between one second to 30 minutes. If you specify zero, the appliance does not cache the requests. When you enable persistence for an LBDN, the appliance stores the results for specific LBDN responses in the DNS Traffic Control cache. When a request originates from the respective FQDN or an IP address within the specified period, the DNS server directs the request to the same server.

...