domain-label
Configures domain label settings.
Syntax
[no] domain-label <name> domain <domain-name>
Parameters
<name> | Name of the domain label. • Domain labels are case sensitive and can be any string consisting of letters, numbers, the underscore (_), or the hyphen ( -). Don’t use spaces in domain labels. • A domain label can be up to 64 characters long. • Domain label changes (that is, adding and removing domain names inside a label) are applied immediately by the rules that use the domain labels that you have modified. • You can create up to 63 unique domain labels. • Domain labels aren’t compatible with IPv6. |
<domain-name> | Domain name. The domain names can be hostnames (for example, www.hostname.com) or wildcard hostnames (for example, *.riverbed.com). • Domain names can appear in multiple domain labels. • Domain names must include a top-level domain, for example, .com or .org. No wildcard is allowed in the top-level domain, for example, microsoft.* • A maximum 64 characters per domain name is allowed. • Domain names must have some characters in the second-level domain names, for example *.outlook.com, *.sharepoint*.com, but not *.com • A domain name can be up to 64 characters long. • Matching on the domain name is case in-sensitive. • Do not use consecutive periods or consecutive wildcards. • Do not use IP addresses. |
Usage
A domain label is a group of Internet domains with optional wildcards to define a wider group. For example a domain called Office365 can match:
n *.microsoft.com
n *.office365.com
n *office.com
You use these domain labels in your in-path rules to simplify in-path rule management. Domain labels are compatible with auto-discover, passthrough, and fixed-target in-path rules. Domain labels are useful if many services are hosted by the same IP address or are hard to separate into distinct subnets. If you know which domains your traffic is going to, you set up your in-path rule to match those domains based on the domain label.
Domain labels do not replace the destination IP address in an in-path rule. The in-path rule still sets the destination IP/subnet (or uses a host label or port to set the destination). The in-path rule matches the destination IP address or port first, and then matches the domain label as a secondary check. The rule must match both the destination and the domain label.
Domain labels in an in-path rule automatically apply to HTTP and HTTPS (ports 80 and 443 by default) for optimization when the port field is set to "All Ports". If you specify a different port number in your in-path rule, the rule honors that port number.
On a downgrade, all domain label information is lost.
The client-side SteelHeads and server-side SteelHeads must be running RiOS 9.2.
The no command option removes the domain label. You cannot remove a domain label if it is used in an in-path rule. You must first remove all domain-label configurations from the in-path rules.
Example
amnesiac (config) # domain-label Bag domain *company.com
amnesiac (config) # in-path rule auto-discover dst-domain Bag
Product
SteelHead CX, SteelHead EX, SteelHead-v
Related Commands
Host Label Commands
This section describes the host label commands.