top of page
Geometric Ceiling

Project no.2

Demonstrate the integration of the DNS platforms of AWS and a Linux-based, simulated on-premises environment using Route53 inbound and outbound endpoints.

​

Education source credit: https://github.com/acantril/learn-cantrill-io-labs

HYBRID DNS.jpeg

Architecture Diagram

AWS CANNOT RESOLVE ANY DSN FROM ON PREMISE ENVIRONMENT.png

Checking and confirming that AWS cannot resolve any DNS from On-Premise environment in simulatation.

proving that there is no networking connectivity between the AWS and ON-PREMISES Environme

Confirming that there are no networking connectivity between On-premise and AWS

3...png

Connecting VPC peer between the environments. This verifies that the AWS environment can ping a resource in the on-premises environment

3. This verifies that the AWS environment can ping a resource in the on-premises environme
4. creating inbound endpoints.png

Creating inbound endpoints

5. Architecturally ... you have just queried the local DNS server on this instance, which

Queried the local DNS server on this instance, which is configured to use the route53 inbound endpoints

6. you have just queried the local DNS server on this instance, which is configured to use

Queried the local DNS server on this instance, which is configured to use the route53 inbound endpoints

7. By using R53 inbound endpoints, you have configured this one-way integration.png

By using R53 inbound endpoints, configured theone-way integration

8. Architecturally this is using DNSA or DNSB as a resolver ... both of which are configur

Using DNSA or DNSB as a resolver. Both of which are configured to forward those queries to the R53 inbound endpoints

9. CREATING OUTBOUND ENDPOINTS.png

Creating Outbound endpoints to allow AWS environment to resolve on-premises

© 2021 by Logan

bottom of page