2 years ago
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.
25 Replies
2 years 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.
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.
2 years ago
what errors?
[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. (/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)2 years ago
I really don't think you own domain.com
2 years ago
I'm sorry but it's not helping
2 years ago
help me, help you
2 years ago
the error, without unnecessary sanitation
[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. (/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)2 years ago
is that the correct domain?
2 years ago
where is it hosted?
2 years ago
dns lookup works fine -
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.
2 years ago
it's only been a problem since the DNS was changed
please provide more context
All of the DNS records were in a cPanel. We had to move them back to the registrar. That change took place earlier today.
2 years ago
dns lookup from google directly also works fine
2 years ago
this would not be a platform issue