Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 9 Current »

You create either an Inbound or Outbound cloud forwarder based on the requirement as follows:

  • Outbound to forward DNS queries from one cloud provider to another.

  • Inbound where a NIOS-X Server responds to queries from a private cloud. 

After you have completed the tasks listed in Prerequisites for Cloud Forwarders, complete the following steps to create a cloud forwarder:

  1. Go to Configure > Networking > DNS > Cloud Forwarders.

  2. Click Create and select AWS, Azure or GCP.

  3. Configure the following:

    • Name: Specify a name for the cloud forwarder.

    • Description: Provide a brief description.

    • Inbound/Outbound: Select Inbound/Outbound based on the requirement. Consider the following two scenarios before configuring a cloud forwarder as Inbound or Outbound:

      • Inbound Cloud Forwarder: NIOS-X Server responds to queries from a private cloud (AWS, Azure, or GCP).

      • Outbound Cloud Forwarder: Forward DNS queries from one cloud provider to another. For example, you can forward DNS queries from AWS to Azure and vice-versa. Cloud to cloud forwarding is only supported for AWS and Azure.

    • VPC/VNET: Select the VPC/VNET from the drop-down. Azure and AWS only support a single VPC/VNET. GCP supports multiple VPC/VNETs.

    • Subnet Address: Select the subnet and use the arrow icon (>>) to move it from Available to Selected. Azure only supports a single subnet and the subnet chosen must be used exclusively for the cloud forwarder. AWS supports multiple subnets. No subnet is chosen for GCP as GCP uses a standard network to source forwarded DNS traffic (35.199.192.0/19).

  4. Click Save & Close.

  • No labels