Cursor Agent DNS Resolution Failure

I need help with a Cursor connection issue. Validated that I can’t resolve outside of my network either, with both Claude, ChatGPT, and from my work network.

Request ID: 4bf4fb64-4c67-4687-b2ed-19824fd74552

Error:
[unavailable] getaddrinfo ENOTFOUND agentn.global.api5.cursor.sh

Stack trace:
at P5A (vscode-file://vscode-app/c:/Users/[REDACTED]/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34267:23755)
at B5A (vscode-file://vscode-app/c:/Users/[REDACTED]/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34267:22658)
at $5A (vscode-file://vscode-app/c:/Users/[REDACTED]/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34268:6285)
at Wou.run (vscode-file://vscode-app/c:/Users/[REDACTED]/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34268:10400)
at async $Oa.runAgentLoop (vscode-file://vscode-app/c:/Users/[REDACTED]/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46832:10024)
at async n5u.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/[REDACTED]/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46886:9277)
at async n5u.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/[REDACTED]/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46886:13663)
at async bMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/[REDACTED]/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34329:17597)
at async Object.Ea [as onSubmit] (vscode-file://vscode-app/c:/Users/[REDACTED]/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45811:4826)
at async vscode-file://vscode-app/c:/Users/[REDACTED]/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45785:56633

Found this post from a link in mine: Cursor connection problem with agent.api5.cursor.sh . Swapping to HTTP 1.1 fixed it for me.