DNS resolution fails for a newly created Databricks workspace

Users should wait for 10 minutes before re-creating a workspace with the same name.

Written by kunal.jadhav

Last published at: October 16th, 2024

Problem

You are attempting to access a newly created workspace that shares the same name as a recently deleted one, but you get an error saying that the site cannot be reached. This only happens when you are trying to access a newly created workspace with the same deployment name as a recently deleted workspace.

Image showing a browser screen error message "This site can't be reached". DNS_PROBE_FINISHED_NXDOMAIN

Cause

The root cause is a DNS resolution failure for the new workspace. Global DNS changes are not instant and can take time to update. If your local DNS server still has the old record (pointing to the recently deleted workspace) when you attempt to access the newly created workspace, the name resolves to the recently deleted workspace and your browser returns an error message saying that the site cannot be reached.

Solution

  1. Delete the old workspace (AWS | Azure | GCP). Ensure the deletion is successful by verifying that the workspace no longer appears as running in the Account Console.
  2. After you have verified that the previous workspace is fully deleted, wait 10 minutes. During this time, the deletion propagates through global DNS.
  3. Create your new workspace with the same deployment name.
  4. Wait 10 minutes for the new record to propagate through global DNS.

You should now be able to access your new workspace via the DNS name.