NgSysV2-4.5: Getting a Custom Domain

A few words of explanation might be helpful here. "A" records are what the web's Domain Name Servers use to translate a URL such as ngatesystems.com into an IPv4 (32-bit) address like 216.239.32.21 that targets a physical machine. Except, in this case, you know this can't be quite right because when you chose the location of your App Engine machine, you selected it from a list of dozens. This address is actually the address of Google's "Global Load Balancer". I guess that you're given four addresses for this in order to provide redundancy. Additionally, you're given four "AAAA" records mapping to IPv6 (128-bit) addresses. This new standard enables the web to support many more physical targets than the original IPv4 scheme. Anyway, to sum up, a DNS record like @ A 216.239.32.21 says "map a request for ngatesystems.com (the @ symbol is a shortcut for the root address of your site) to a machine at 216.239.32.21

Finally, the CNAME record, which stands for 'Canonical Name', directs traffic for ngatesystems.com's subdomain at www.ngatesystems.com to the Google traffic handler at ghs.googlehosted.com. It's called a 'Canonical' Name because it provides a unique reference for resolving the domain to its correct destination, simplifying DNS management and ensuring consistent routing.

4.4 Set Up SSL (Enable use of HTTPS addresses):

• Google Cloud automatically provisions SSL certificates for your custom domain. If you visit the Custom Domains section after mapping your domain, you'll see the SSL status as "Provisioning." It usually takes a few minutes to complete.


• Once complete, your app will be accessible over HTTPS.

4.5 Wait for DNS Propagation:

• DNS changes can take some time to propagate, so your custom domain might not work immediately. This process can take a few minutes to several hours, depending on your registrar.