Troubleshooting Google Domains hosting with Amazon Route 53 -> Application Load Balancer

By -

I have a domain managed on Google Domains and would like it to point to an Amazon route 53. I've configured the custom name servers on Google to point to the ones for my public hosted zone, and using WHOIS can confirm that these are the name servers being returned when I try to access the domain. The problem is that when I navigate to this domain in my browser it says "Server not found." I have an alias record set up in Route 53, of type A, that points to the Application Load Balancer running my application (and another alias for www.domain.com). When I hit "test record", and select type A it returns an IP address that I can go to and verify that it is running my app.

TLDR: WHOIS shows the Amazon name servers, testing the records in Route 53 returns IPs from an alias'd A record that are indeed hosting my app, but when I navigate to domain.com in my browser nothing happens.

Thanks!

I've tried updating the type of the record in Route 53 to both AAAA and CNAME (changing what they point to respectively) with no luck. I've tried destroying the hosted zone and making it again.

UPDATE: Feel quite stupid, but waiting ~36 hours worked. I guess it just took awhile, I was only expecting it to take up to 24.



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more