Private Hosted Zone DNS
Table of Contents
Expand all | Collapse all
-
- About Cloud NGFW for AWS
- Getting Started from the AWS Marketplace
- Cloud NGFW for AWS Pricing
- Cloud NGFW for AWS Free Trial
- Cloud NGFW for AWS Limits and Quotas
- Subscribe to Cloud NGFW for AWS
- Locate Your Cloud NGFW for AWS Serial Number
- Cross-Account Role CFT Permissions for Cloud NGFW
- Invite Users to Cloud NGFW for AWS
- Manage Cloud NGFW for AWS Users
- Deploy Cloud NGFW for AWS with the AWS Firewall Manager
- Enable Programmatic Access
- Terraform Support for Cloud NGFW AWS
- Provision Cloud NGFW Resources to your AWS CFT
- Usage Explorer
- Create a Support Case
-
-
- Prepare for Panorama Integration
- Link the Cloud NGFW to Palo Alto Networks Management
- Unlink the Cloud NGFW from Palo Alto Networks Management
- Associate a Linked Panorama to the Cloud NGFW Resource
- Use Panorama for Cloud NGFW Policy Management
- View Cloud NGFW Logs and Activity in Panorama
- View Cloud NGFW Logs in Cortex Data Lake
- Tag Based Policies
-
Private Hosted Zone DNS
Learn how to direct DNS queries from a Private Hosted Zone DNS to Cloud
NGFW.
To create a Private Hosted zone in AWS, see
Creating a private hosted zone
.To allow your Cloud NGFW resource to query Route 53 Resolver for any DNS zones (e.g.,
Private Zones) hosted on Route 53, you create a Route 53 Inbound Endpoint as
discussed earlier. The Inbound Endpoint is a bridge for other services to query
Route 53 for domain name resolution. When you create an Inbound Endpoint, AWS
creates an elastic network interface (ENI) in each availability zone (AZ) that you
specify will receive inbound DNS queries.
- Open the Amazon VPC console.
- Create an inbound endpoint.
- Select.ServicesRoute 53ResolverInbound Endpoints
- ClickCreate inbound endpoint.
- Enter a descriptiveName.
- Select the VPC for the endpoint.
- Attach a security group for this endpoint.
- Set theEndpoint Typeto IPv4.
- Select the availability zone.
- Select the subnet you created above.If you have more than one availability zone, you must specify the availability zone and subnet for each.
- ClickCreate inbound endpoint.
- Note the IP address associated with each subnet attached to your inbound endpoint. Use these IP addresses when configuring yourDHCP option setsin the following steps.
- Select.VPCDHCP option sets
- You can create a new DHCP option set and add the IP address for each availability zone. If you have more than one availability zone, enter each IP address as a comma-separated list.
- SelectVPCand choose the VPC to secure.
- From theActionsdrop-down, selectEdit VPC settings.
- UnderDHCP settings, choose the DHCP option set with you created above from theDHCP option setdrop-down.
- ClickSave changes.
- Edit your subnet route table.
- Select.VPCRoute Tables
- Select the route table for the subnet you want to secure.
- Add a route and set the destination to the IP address of your DNS server and set the target to the Cloud NGFW endpoint.
- ClickSave changes.Any DNS traffic from the protected subnet is routed through the Cloud NGFW endpoint and on to the Cloud NGFW for inspection and enforcement.