Railway•7mo ago

Is there a cache?

We have an API that is deployed with Railway. The API includes a WP instance for content. The name servers for this WP instance's subdomain were updated. While propagation typically can take up to 3 days, ours run super fast. For nearly 12 hours now, our API does not register that the DNS updates were made, and continue to crash saying the subdomain can't be found. In localhost, everything is working as expected, but when deployed it doesn't work. So, the only thing that makes sense is that there is a cache somewhere.

22 Replies

Percy•7mo ago

Project ID: N/A

Brody•7mo ago

a cache in what sense? http requests? build? what? I'm sorry but you weren't very clear in explaining what exactly the issue is.

jared.leddyOP•7mo ago

The issue is that this 1 subdomain is throwing errors in the logs, and no where else. And subsequently, our services using the API have crashed.

Brody•7mo ago

what errors?

jared.leddyOP•7mo ago

[Nest] 25  - 05/07/2024, 2:15:05 AM   ERROR [ExceptionsHandler] getaddrinfo ENOTFOUND content.domain.com
Error: getaddrinfo ENOTFOUND content.domain.com
at Function.AxiosError.from (/app/node_modules/axios/dist/node/axios.cjs:836:14)
at RedirectableRequest.handleRequestError (/app/node_modules/axios/dist/node/axios.cjs:3010:25)
at RedirectableRequest.emit (node:events:513:28)
at ClientRequest.eventHandlers.<computed> (/app/node_modules/follow-redirects/index.js:14:24)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:494:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

[Nest] 25  - 05/07/2024, 2:15:05 AM   ERROR [ExceptionsHandler] getaddrinfo ENOTFOUND content.domain.com
Error: getaddrinfo ENOTFOUND content.domain.com
at Function.AxiosError.from (/app/node_modules/axios/dist/node/axios.cjs:836:14)
at RedirectableRequest.handleRequestError (/app/node_modules/axios/dist/node/axios.cjs:3010:25)
at RedirectableRequest.emit (node:events:513:28)
at ClientRequest.eventHandlers.<computed> (/app/node_modules/follow-redirects/index.js:14:24)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:494:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

Brody•7mo ago

I really don't think you own domain.com

jared.leddyOP•7mo ago

LoL! No. That was sanitized.

Brody•7mo ago

I'm sorry but it's not helping help me, help you

jared.leddyOP•7mo ago

What do you need?

Brody•7mo ago

the error, without unnecessary sanitation

jared.leddyOP•7mo ago

[Nest] 25  - 05/07/2024, 2:15:05 AM   ERROR [ExceptionsHandler] getaddrinfo ENOTFOUND content.veterandb.com
Error: getaddrinfo ENOTFOUND content.veterandb.com
at Function.AxiosError.from (/app/node_modules/axios/dist/node/axios.cjs:836:14)
at RedirectableRequest.handleRequestError (/app/node_modules/axios/dist/node/axios.cjs:3010:25)
at RedirectableRequest.emit (node:events:513:28)
at ClientRequest.eventHandlers.<computed> (/app/node_modules/follow-redirects/index.js:14:24)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:494:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

[Nest] 25  - 05/07/2024, 2:15:05 AM   ERROR [ExceptionsHandler] getaddrinfo ENOTFOUND content.veterandb.com
Error: getaddrinfo ENOTFOUND content.veterandb.com
at Function.AxiosError.from (/app/node_modules/axios/dist/node/axios.cjs:836:14)
at RedirectableRequest.handleRequestError (/app/node_modules/axios/dist/node/axios.cjs:3010:25)
at RedirectableRequest.emit (node:events:513:28)
at ClientRequest.eventHandlers.<computed> (/app/node_modules/follow-redirects/index.js:14:24)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:494:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

Brody•7mo ago

is that the correct domain?

jared.leddyOP•7mo ago

Yes

Brody•7mo ago

where is it hosted?

jared.leddyOP•7mo ago

That subdomain is hosted with Flywheel.

Brody•7mo ago

dns lookup works fine - https://utilities.up.railway.app/dns-lookup?value=content.veterandb.com&type=ip

jared.leddyOP•7mo ago

I know. DNS looks good. API works fine locally. All the other apps that rely on this API work fine locally too. Only this railway instance has a problem with it. And it's only been a problem since the DNS was changed. We redeployed the API about an hour and a half ago as well. Didn't make a difference.

Brody•7mo ago

it's only been a problem since the DNS was changed

please provide more context

jared.leddyOP•7mo ago

All of the DNS records were in a cPanel. We had to move them back to the registrar. That change took place earlier today.

Brody•7mo ago

dns lookup from google directly also works fine

Brody•7mo ago

this would not be a platform issue

jared.leddyOP•7mo ago

Ok. Of course it just started working again. 🤦‍♂️

Gaming

Programming

Is there a cache?