t_sec_fqdn_config

Available Languages

Updated:November 29, 2020

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Mapping FQDN ACLs with Domain Lists

Mapping FQDN ACLs with Domain Lists

ClosedAbout FQDN ACLs

 

When access control lists (ACLs) are configured using a fully qualified domain name (FQDN), ACLs can be applied based on the destination domain name. The destination domain name is then resolved to an IP address, which is provided to the client as a part of the DNS response.

Guest users can log in using web authentication with a parameter map that consists of an FQDN ACL name.

On the Configuration > Security > FQDN page, you can create FQDN ACLs and map them to domain lists.

ClosedDomain Lists
  1. In the Domain Lists tab, click Add.
  2. Enter a name for the domain list.
  3. Click Add.
  4. In the Domain Name field, enter the domain name you want to add to the domain name list.
  5. Click Save & Apply to Device.
ClosedMap an FQDN ACL to a Domain List
  1. In the Parameter Mapping tab, click Add.
  2. In the Create Parameter Mapping window that is displayed, choose an access list.
  3. Choose a domain name list you want to map with the access list.
  4. Check the Global check box to use the parameter map globally.
  5. From the Parameter Map list, choose a parameter map from the available list to the used list.
  6. Click Save & Apply to Device.

 

Related Topics Link IconRelated Topics

 

© 2020 Cisco Systems, Inc. All rights reserved.

 

Was this Document Helpful?

FeedbackFeedback

Contact Cisco