Modifying Host and Network Interface Settings : Configuring domain labels
  
Configuring domain labels
You can configure domain labels for in-path rules in the Domain labels page. You add domain labels to in-path rules to filter connections based upon hostnames (that is, both optimized and pass-through rules).
Domain labels are names given to a group of domains to streamline configuration. You can specify an internet domain with wildcards (*) to define a wider group. For example, you can create a domain label called Office365 and add *.microsoftonline.com, *.office365.com, or *.office.com.
Domain labels provide flexible domain and hostname-based interception through a dynamic IP address to accommodate network environments that are changing from static to dynamic IP addresses.
For details on domain label guidelines and when to use them, see the SteelHead User Guide.
Domain labels are optional.
Use these guidelines when creating domain labels for in-path rules:
• Because hostname-based interception (HNBI) consumes resources, we recommend you use domain label rules that are low in the in-path rule stack.
• Domain label in-path rules that are defined as pass through, discard, or deny should be used with extreme caution as they can pass through or block all traffic.
• If the traffic matches the domain rule and HNBI fails, the system moves to the next rule that matches. If the traffic matches a fixed-target rule and HNBI fails, and the subsequent search matches an autodiscovery rule, then the traffic is bypassed.
To configure domain labels
1. Choose Administration > Networking: Domain labels.
2. To add a domain label, complete the configuration as described in this table.
Control
Description
Add a New Domain Label
Displays the controls to add a new domain label.
Name
Specify the label name: for example, YouTube. These rules apply:
• Domain label names are case sensitive and can be any string consisting of letters, numbers, underscore ( _ ), or hyphen ( - ). There can’t be spaces in domain labels.
• Riverbed suggests starting the name with a letter or underscore,
• To avoid confusion, don’t use a number for a domain label.
• You can’t delete domain labels that an in-path rule is using.
Domain
Specify a comma-separated list of domains. Keep in mind that the URL might use other domains. For example, www.box.com might also use srv1.box.net and other domains. Determine all of the domains whose traffic you want to optimize, and make an entry in the domain label for each one. Domain labels are most useful when they specify a narrow destination IP range, so use the smallest destination IP range you can. Using a host label can help to narrow the destination IP range.
These rules apply to domain label entries:
• Matching is not case sensitive.
• You must include a top-level domain: for example, .com. You cannot include a wildcard in a top-level domain.
• You must specify second-level domains: for example, *.outlook.com, but not *.com.
• You can also separate domains with spaces or new lines.
• A domain name can be up to 64 characters long.
• Characters must be alphanumeric (0-9, a-z, A-Z), periods, underscores, wildcards, and hyphens.
• Do not use consecutive periods.
• Do not use consecutive wildcards.
• Do not use IP addresses.
A domain can appear in multiple domain labels. You can create up to 63 unique domain labels.
Remove Selected
Select the check box next to the name and click Remove Selected. You can’t delete domain labels that an in-path rule is using.
Add New Domain Label
Adds the domain label. The page updates the domain label table with the new domain label.