DNS instructions doesn't work on Hostinger
dp_app
PROOP

15 days ago

I followed your instructions to use a custom name and a custom domain, but when I do this on Hostinger, the CNAME type cannot have an name @ and it is automatically replaced by www (see picture).

Attachments

$20 Bounty

6 Replies

dp_app
PROOP

15 days ago

I found this video that use a trick of specifying the domain with www, but when I do that since I did it before without the www it reuse the CNAME of the previous domain (without www) at the root level. Should I just wait and try again ? If yes how long?


dp_app
PROOP

15 days ago


dp_app
PROOP

15 days ago

I switched to Cloudflare at the end, but still got a warning for the cname:



dp_app
PROOP

15 days ago

It works actually thanks


dp_app
PROOP

15 days ago

It no longer works I'm totally confused


Railway
BOT

15 days ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway 15 days ago


11 days ago

Hi,

DNS propagation can take up to 72 hours to be effective. In most case it will never be longer than a few hours but it all depends on the DNS servers used. For example, if you edit your DNS zone on Cloudflare, someone using Cloudflare DNS will probably see the changes almost immediately but someone using Google DNS may have to wait a few hours.

Furthermore, Cloudflare is proxying all your A, AAAA or CNAME records by default (There is the little orange cloud next to your record saying "Proxied"). In that case, Railway detects the proxy by checking on Cloudflare IPs but leaves a warning (You can see on your screenshot "Cloudflare Proxy Detected"). It just means that they detected your subdomain was proxied so they are unable to check it's routed to your domain but it would still works very well slightly_smiling_face emoji

If you really wan't to get rid of this warning and let Railway manage TLS certificates for you instead of Cloudflare, you can simply uncheck the "Proxy" box by editing your CNAME record. Keep in mind that your traffic will no longer go through Cloudflare infrastructure and you will not benefit from many of their features (WAF, Caching, Content optimization, etc...). It will become a simple CNAME record.

Hope that helps !


Loading...