the dashboard networking section takes forever to load, and when it eventually does, the part under "public networking" says "Waiting for DNS update"

i double checked and my DNS is updated exactly as railway expects it to be

i'm also seeing ERR_FAILED 504 (Gateway Timeout) for a request to https://backboard.railway.app/graphql/internal?q=networking in my browser's console sometimes

what is the domain in question?

https://knoword.com

now the dashboard UI is saying "setup complete" under the public networking section, but when i access the URL, it still gives me ERR_SSL_UNRECOGNIZED_NAME_ALERT

who is your domain provider

namecheap

can you show me your setup?

yeah for sure

want me to send a screenshot or hop on a video call?

just a simple screenshot is good

my DNS setup hasn't changed since august, and i've had no problem with it until just now

the reason i'm using an ALIAS instead of a CNAME is because i also need to have a TXT record at the domain root and i can't do that with a root-level CNAME

ALIAS is not going to work correctly given the cname doesnt have a static IP

your domain will break every time we change the IP behind *.up.railway.app

damn that sucks. did you guys just change the IP? I've never seen this happen before

im not sure, this could be a separate issue, just thought id state that fact

go ahead and redeploy

redeploying

ok we're back

that really sucks though. do you have any advice on how i can point my root-level domain at my railway deployment while still allowing me to set root level TXT records? it's my understanding that you can't have TXT and CNAME records for the same subdomain (or @)

for context, i need the root-level TXT records for email authentication (SPF records)

use cloudflare's nameservers with the proxy enabled

oh ok! i'll take a look at that

!s