News for hackers. Stuff that matters.

A comment on Should you use www or not in your domain? (2017). Parent comment

Re:Should you use www or not in your domain? (2017) by hacknat on Sunday November 11, 2018 @10:38AM (#18426843)
You can add AWS, Azure, and GCP to this list. Most people don’t want to lay out the money for a static IP, and why should they?
[ Parent | on HN ]
Re:Should you use www or not in your domain? (2017) by yegle on Sunday November 11, 2018 @11:17AM (#18427070)
Not true for App Engine: we have a fixed set of IP addresses to be used in A/AAAA record.

Disclaimer I work on App Engine.

[ Parent | on HN ]
Re:Should you use www or not in your domain? (2017) by hacknat on Sunday November 11, 2018 @11:54AM (#18427251)
This FAQ on App Engine specifically says you guys can’t map a static IP to a site:

https://cloud.google.com/appengine/kb/

[ Parent | on HN ]
Re:Should you use www or not in your domain? (2017) by stickfigure on Sunday November 11, 2018 @12:41PM (#18427512)
That is something different. If you want to run your app on a naked domain, they give you a set of A/AAA records you can use.

Search in that same document for "naked domain".

[ Parent | on HN ]
Re:Should you use www or not in your domain? (2017) by merb on Sunday November 11, 2018 @01:15PM (#18427679)
you should read before you write.

> I'd like to map my app to a naked domain (such as http://example.com).

vs.

> App Engine does not currently provide a way to map static IP addresses to an application

the latter is that you own an IP and want to map it against your appengine.

the former is example.com -> appengine site.

(not related to google)

[ Parent | on HN ]