Neither barcrwlr.com nor www.barcrwlr.com are currently added as custom domains on your service. Your domain list only shows Railway-generated .up.railway.app domains. You'll need to add them as custom domains in your service settings at railway.com under the service's Settings > Networking > Custom Domain section. Additionally, barcrwlr.com (the apex) is currently resolving to 151.101.2.15, which is not a Railway IP. It needs a CNAME or A record pointing to Railway per the instructions shown when you add the custom domain.

what is the IP address I need to use

We don't provide a static IP address for custom domains. When you add a custom domain in your service's Settings > Networking > Custom Domain section, you'll be given a unique CNAME value (in the form xxxxx.up.railway.app) to point your DNS records to. For the apex domain (barcrwlr.com), your DNS provider must support CNAME flattening or ALIAS records, as described in our custom domain docs.

Do I need to add both www.barcrwlr.com and barcrwlr.com as custom domains

Yes, you need both added as separate custom domains, and we can see you've already done that. However, there are two DNS issues to fix. First, barcrwlr.com (the apex) is pointing to 151.101.2.15 instead of the required CNAME target sgeg2qhs.up.railway.app, and since your DNS is on GoDaddy (which doesn't support CNAME flattening), you'll need to switch your nameservers to a provider like Cloudflare to use a CNAME at the root. Second, www.barcrwlr.com is pointing to barcrwlrs.up.railway.app but needs to point to ua0pf85h.up.railway.app, and it's also missing its verification TXT record at _railway-verify.www with the value shown in your domain settings. Certificates won't issue until both the CNAME and TXT records are correct for each domain.