Custom Google Domain not directing to Square Weebly store even after 48 hours

[Kvinod77]

Hi,

I setup my custom resource records in Google Domains on 9/19 at around 10am. It has been more than 48 hours and my domain (www.kushalasip.coffee) is still pointing to my old "Blogger" site.

I've reviewed the IP address a dozen times for the @ and www records and they are correct.

My domain is setup for using a custom name server because the email server is hosted with the original host and I don't want to move that.

Any advice on why my site isn't redirecting correctly?

Thanks,

Vinod

[BernadetteA]

Hi Vinod. I used a third party tool (whatsmydns.com) to verify your dns settings, however, the A-records appear to be pointing to an IP address I do not recognize. Can you please verify on Google’s end that the records for the domain and the www subdomain are both pointing to 199.34.228.164

It can take up to 24-48 hours for the dns to fully update on the backend, and you can use the url I mentioned to monitor the progress.

[Kvinod77]

Hi @BernadetteA - Thank you so much for looking into this and responding. I checked www.whatsmydns.com and you are correct in that it is still pointing to my old website location.

The weird thing about this is that my Custom Resource Records are pointing to the right address, and it has been that way for 5 days now. See screenshot below. 

Any ideas what else might be the issue here?

[PreOrder_Apps]

Hi. We're an Official Square Partner company and would be happy to help you with this - no charge or anything. Let us know if you continue to have trouble and we can do a quick screenshare with you to help you problem shoot this. Google Domains can be a little tricky when updating the DNS and like @BernadetteA said it can take sometime - in fact they've been known to take longer than other registrars. 

Thanks!

Thomas

[BernadetteA]

Hmm.. that is odd. Unfortunately, I'm not familiar enough with the Google dashboard to provide you information on what it should or should not look like. The only thing I can think of is to make sure you do not see any records pointing to 68.66.200.214

It also looks like the nameservers may be set to Enom. Is this company familiar to you?