Automation sandbox cannot resolve DNS while host Terminal can

What version of the Codex App are you using (From “About Codex” dialog)?

26.730.61639

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Darwin 27.0.0 arm64 arm

What issue are you seeing?

Summary

A local Codex automation that had run successfully for about two weeks can no longer resolve DNS names inside its execution sandbox.

The same Mac can resolve the same domains successfully in a normal Terminal. Restarting Codex and manually running the automation did not fix the issue.

Impact

This blocks all network-dependent local automations. My daily QQQ and S&P 500 price-action screener cannot download the current index constituents or market data, so it cannot produce updated reports.

Actual result

Inside the Codex automation sandbox, DNS resolution fails:

socket.gaierror: [Errno 8] nodename nor servname provided, or not known

urllib3.exceptions.NameResolutionError:
HTTPSConnection(host='en.wikipedia.org', port=443):
Failed to resolve 'en.wikipedia.org'

### What steps can reproduce the bug?

1. On macOS, run a local Codex automation that executes a Python script requiring HTTPS access.

2. Run:

TradingAgents/.venv/bin/python price_action_screener.py --universe qqq --max-results 20

3. The command fails while resolving en.wikipedia.org with:

socket.gaierror: [Errno 8] nodename nor servname provided, or not known

urllib3.exceptions.NameResolutionError: HTTPSConnection(host='en.wikipedia.org', port=443): Failed to resolve 'en.wikipedia.org'

4. Run:

TradingAgents/.venv/bin/python price_action_screener.py --universe sp500 --max-results 30

5. It fails with the same DNS resolution error.

6. In the Codex automation sandbox, run:

scutil --dns
curl -I https://developers.openai.com

7. Observed results:
- scutil --dns reports no DNS configuration.
- curl fails with: curl: (6) Could not resolve host: developers.openai.com

8. On the same Mac, normal Terminal DNS resolution works. Restarting Codex and manually running the automation does not resolve the issue.

No session ID, token-limit usage, or context-window usage is applicable to this DNS/network sandbox issue.

### What is the expected behavior?

_No response_

### Additional information

_No response_