Grok BotGuide

Network

Grok Bot DNS error

A Grok Bot DNS error means your resolver cannot look up the computer hostname under cursorvm.com. The apex name can answer while every subdomain returns Query refused.

Retry, Recover, and Reset do not teach that resolver a name. A rebuilt computer is another hostname in the same zone.

Full can't-reach order, after this resolver check

Why the native method fails

The native method is to rebuild the computer because the sentence says it cannot be reached. Staff have answered threads where the cloud computer was healthy the whole time. The Mac never finished reconnecting because traffic to cursorvm.com was dropped, or because the subdomain lookup was refused. Reset allocates a new name your resolver still cannot resolve. You then spend the evening on Cleaning up for a network fault.

The same on-screen sentence is also a known display bug when a trial or plan has ended. If Retry and Recover fail because the account no longer includes Grok Bot, DNS changes will not help. The pricing page is that check. Do not burn an evening on a public resolver for a billing problem.

Steps

  1. Fully quit Grok Bot and reopen it. On a Mac that is menu-bar Quit, not closing the window. On Windows, quit from the tray. Then choose Retry if it is offered. Do this before you edit DNS, so a stuck process is not what you are measuring.
  2. Join a phone hotspot on another carrier and open Grok Bot from the computer. If the hotspot works, the home or office path is the fault. Stop resetting the computer. If the hotspot fails and the phone app on cellular also fails, treat it as server-side and slow down. Desktop and iOS both stuck, with the phone off your Wi-Fi, is the case staff often tell people not to Reset, Recover, Update, or sign out of.
  3. Look up a hostname under cursorvm.com, not the apex. The app connects to a per-computer subdomain. Staff have used names of the shape test123 under a region host such as us8 or us10. Read the Server line in the lookup so you see which resolver actually answered. Apex success plus Query refused on the subdomain is this bug.
  4. Staff point at 1.1.1.1 and 8.8.8.8 for IPv4. On IPv6, a router advertisement can keep handing out the ISP resolver after you change only IPv4, so the new IPv4 servers never get the query. The thread that cleared a multi-day failure set IPv6 DNS as well, using 2606:4700:4700::1111, then fully quit and reopened the app.
  5. On Windows the app ignores the system HTTP proxy and connects directly. Browser checks that travel through a proxy can pass while Grok Bot fails. Staff's probe, after a TUN-mode tunnel is on, is a direct request that skips the proxy to a test hostname under cursorvm.com. A fast 404 whose server banner is awselb/2.0 means the direct path works. The hostname is only a probe. A hang means the app will fail too. Region in that report was us10, not us8. Do not install that tunnel inside the Agent Computer.

Limits

Never change DNS, or install a VPN or proxy, inside the Agent Computer. A bot that installs a VPN can cut the always-on path so every bot on the account fails until Recover restores routing. That is a different outage from the one on your laptop resolver, and Recover is the routing restore, not a casual Reset.

Antivirus products that scan HTTPS, Cloudflare WARP, and a Zscaler-style tunnel can blank the screen while DNS is fine. WARP can intercept the computer even on a hotspot. Zscaler can keep tunneling on a hotspot; staff have told people to quit Grok Bot, pause Zscaler, and ask IT to allowlist both *.cursorvm.com and **.cursorvm.com. Those are path blocks. Use them when the lookup itself succeeds. The can't-reach page is the full order, including the button sequence before any resolver edit.

Days of Can't reach after you have already recovered, reset, and reinstalled usually mean a stuck hosted box that only staff can restore. Email hi@cursor.com. Another public DNS server will not shorten that queue.

FAQ

The website cursorvm.com opens. Why does Grok Bot still fail?

The app does not use the apex. It uses a per-computer subdomain. The apex can resolve while the subdomain returns Query refused.

I set 1.1.1.1 and nothing changed. What did staff add?

IPv6. Router advertisements can keep the ISP resolver. Set IPv6 DNS as well, then fully quit and reopen. One fixed thread used 2606:4700:4700::1111.

Will Reset give me a computer on a DNS name that works?

No. The replacement is in the same zone. If staff have said the computer is healthy, do not Reset or Recover. Fix the resolver or move to a hotspot.

My phone on cellular works and the desktop does not. Is that DNS?

It is your desktop path, which includes DNS. The bots were not deleted. Do not Reset. Prefer a hotspot test, then Recover or Update only if the computer is actually unreachable after the network is fixed.

Should I change DNS inside the Agent Computer?

No. Staff warn that a VPN or DNS change inside the computer can knock every bot offline until Recover restores routing.

Related

Sources

  • Official troubleshooting
  • Query refused on the subdomain
  • IPv6 DNS
  • VPN drops cursorvm
  • Windows ignores the system proxy
  • Zscaler