Dnschecker

My student organization had an old website with the domain crazymonkeyscomedy.com that had very simple html and css hosted by bluehost, but I have learned a lot about web development lately and made a ruby on rails application for our new website on heroku at crazymonkeyscomedy.herokuapp.com . I think I pointed our domain to the heroku site correctly after following a few online tutorials, and when I check the dns propagation on sites like dnschecker.org, they all become resolved, but when I try to navigate to crazymonkeyscomedy.com, the IP can not be reached.

Could this be an issue with my computer caching the DNS for that domain and trying to resolve the old bluehost hosting? Its been a little over 24 hours and I know that propagation can take up to 48 hours but I just find it odd that dnschecker.org says several locations could resolve it.

Dnschecker

Download File 🔥 https://urloso.com/2y3i4U 🔥

when we check on dns propagation website on dnschecker.org and www.dnscheck.id, we can see on dnschecker from 25 regional servers there are 7 servers can't resolved and on dnscheck.id from 15 servers there are 10 servers can't resolved.

Hi, Not sure if this is still being reviewed. but I have a similar issue. I went to our site today and I'm getting a dns error like this, but my ip addresses and the name are all correct in my registrar (register.com). So I'm not sure what the issue is? according to dnschecker.org, it's seeing the A records with no problem, but it is not seeing the CNAME at all? And according to register.com, there is no error there either? ff782bc1db