3 ms·

> Thehe crux of the issue is that the root domain "myname.com" does NOT point to my website, and will simply time out without a response. There is nothing I can

> Thehe crux of the issue is that the root domain "myname.com" does NOT point to my website, and will simply time out without a response. There is nothing I can do to fix this. My domain host does not allow ALIAS records on the root domain, only A records. Conversely, my server host (Heroku) does not allow A records for routing, only ALIAS. As such, I'm stuck with the www solution. I have to admit I don't have much sympathy for this. Do better at hosting your own authoritative dns properly so you can actually control the zone file for your domain. You can do it on a $1 per month virtual machine. It's that low in resource needs.

lrx 5y ago
Chrome shouldn't make big changes to requests. Changing the host is unacceptable. And no, asking someone to run a $1 server to get around it is not sufficient either. Why would you think a PaaS app would need a dedicated DNS server? Defeats the purpose.
- walrus01 5y ago
  if you own your own domain name and run your own httpd, being able to properly format an authoritative DNS answer so that when people type "burrito.com" into the address bar, it goes to your webserver at www.burrit.com, is a bare minimum level of doing things normally on the internet these days. I don't agree at all with chrome mangling stuff in the address bar, but if you're not running your authoritative dns properly and don't have actual control over your zonefile, it's not a good sign.
i_cannot_hack 5y ago
I would have hoped it was clear from the P.P.S. that I was working on a fix for the hosting situation. Of course the routing to my website was broken, and needed a fix. But if the routing to my website is broken, Chrome clearly should not choose present the broken URL to the user as the location of my website. You cannot ensure every domain on the internet remains working at all times. But you can ensure your browser will not trick you into sharing a broken domain with others, by falsely presenting it as working to you.
BenjiWiebe 5y ago
There's free good DNS hosting out there. Dns.he.net for example.

lrx 5y ago

Chrome shouldn't make big changes to requests. Changing the host is unacceptable. And no, asking someone to run a $1 server to get around it is not sufficient either. Why would you think a PaaS app would need a dedicated DNS server? Defeats the purpose.

walrus01 5y ago
if you own your own domain name and run your own httpd, being able to properly format an authoritative DNS answer so that when people type "burrito.com" into the address bar, it goes to your webserver at www.burrit.com, is a bare minimum level of doing things normally on the internet these days. I don't agree at all with chrome mangling stuff in the address bar, but if you're not running your authoritative dns properly and don't have actual control over your zonefile, it's not a good sign.

i_cannot_hack 5y ago

I would have hoped it was clear from the P.P.S. that I was working on a fix for the hosting situation. Of course the routing to my website was broken, and needed a fix. But if the routing to my website is broken, Chrome clearly should not choose present the broken URL to the user as the location of my website. You cannot ensure every domain on the internet remains working at all times. But you can ensure your browser will not trick you into sharing a broken domain with others, by falsely presenting it as working to you.

BenjiWiebe 5y ago

There's free good DNS hosting out there. Dns.he.net for example.