• A list of the VPC domains that the on-premise DNS server must resolve to the AWS DNS
server. For example, if your VPC servers must resolve
server.example.com
and
server.example.net
, then the list of required VPC domains is
example.com
and
example.net
.
• A test FQDN that is configured in the VPC DNS.
Procedure
1. Log on to your local on-premises DNS server.
2. Add a new “Forward Zone” or “Forward Lookup Zone” DNS by following the instructions
provided by your DNS server manufacturer.
3. Add a new forward zone with the following details for each required VPC domain:
a. A zone name: Use the same name as the domain name. For example,
example.com
.
b. The forwarding address: Use the IP address and port of the DNS server in the AWS
VPC. For example,
10.1.2.3@53
.
c. Forward First: Enable Forward First if your DNS server supports this feature. This
feature causes resolution requests for the zone to be forwarded to the VPC DNS
server before attempting to resolve them locally.
4. Enable the DNS server changes by reloading the configuration or restarting the DNS
server.
5. Verify that the DNS resolution completes by performing a lookup of the test FQDN using a
DNS resolution utility, such as
nslookup
or
dig
.
For example, you can run the following
nslookup
command:
> nslookup server.example.com
Server: 192.168.0.1
Address: 192.168.0.1#53
Non-authoritative answer:
Name: server.example.com
Address: 10.1.2.165
Logging in to the EC2 instance
Procedure
Log in to the EC2 instance using the SSH console or PuTTY.
For information about how to use PuTTY, see
https://docs.aws.amazon.com/AWSEC2/latest/
UserGuide/putty.html?icmpid=docs_ec2_console
.
Note:
You must use the key that you specified during stack creation.
Amazon Web Services deployments
October 2018
Deploying the Avaya Aura
®
Web Gateway
61
