Hi, thanks for the troubleshooting checklist.

I tried the items above, but I’m still blocked and wanted to share the exact current state + ask what I should check next.

What I’ve done / verified:

• Workspace is on AWS, region us-west-2.

• Using Serverless notebook (CPU).

• I attached the “ncc_public_internet” Network Connectivity Configuration to the workspace (I can see it on the workspace details page).

• Serverless egress control shows the default policy with Access = Full.

• After waiting and starting a fresh session, DNS still fails:

  • socket.gethostbyname for a public domain returns “gaierror: Name or service not known”

  • urllib request returns “Temporary failure in name resolution”

• SQL Warehouse queries work, but any outbound HTTP call from the notebook fails because DNS can’t resolve.

Two extra clues:

• When I open “Private access settings” in the account console, the page returns a 403 error (not sure if permissions-related or relevant).

• In the account workspace overview, the credential name shows “Serverless only” (maybe this means classic clusters aren’t enabled?).

Question:
Given NCC is attached and egress policy is “Full”, what else can still block public DNS for Serverless notebooks? Is there a separate account-level setting/entitlement that must be enabled for serverless internet egress, or is “serverless-only” a known limitation where external downloads aren’t allowed?

Thanks again!