Expected Behaviour
For the P4CR EC2 instance to initialize successfully.
Current Behaviour
It does not initialize successfully, instead I see a Apache2 default page when trying to navigate to the home page for Code Review. route53_private_hosted_zone_name is set to workshop.local
Possible Solution
The P4 Code Review AMI is Ubuntu-based and uses systemd-resolved. By RFC 6762, systemd-resolved treats .local as a Multicast DNS (mDNS) domain and never forwards those queries to the VPC DNS resolver at 169.254.169.253. As a result, the instance cannot resolve the P4 Server hostname during the configure-swarm.sh initialization step.
Add a validation or warning in the route53_private_hosted_zone_name variable rejecting .local TLDs.
Steps to Reproduce
Deploy Perforce module with a .local hosed zone, such as with the CGDT Workshop.
Cloud Game Development Toolkit version
latest
Expected Behaviour
For the P4CR EC2 instance to initialize successfully.
Current Behaviour
It does not initialize successfully, instead I see a Apache2 default page when trying to navigate to the home page for Code Review. route53_private_hosted_zone_name is set to workshop.local
Possible Solution
The P4 Code Review AMI is Ubuntu-based and uses systemd-resolved. By RFC 6762, systemd-resolved treats .local as a Multicast DNS (mDNS) domain and never forwards those queries to the VPC DNS resolver at 169.254.169.253. As a result, the instance cannot resolve the P4 Server hostname during the configure-swarm.sh initialization step.
Add a validation or warning in the route53_private_hosted_zone_name variable rejecting .local TLDs.
Steps to Reproduce
Deploy Perforce module with a .local hosed zone, such as with the CGDT Workshop.
Cloud Game Development Toolkit version
latest