Databricks (GCP) Cluster not resolving Hostname into IP address

[Sadam97]

we have #mongodb hosts that must be resolved to private internal loadbalancer ips ( of another cluster ), and that we are unable to add host aliases in the Databricks GKE cluster in order for the spark to be able to connect to a mongodb and resolve the mongodb hostname into ip address. Databricks workspace is in VPC as mongodb cluster and has subnet access as we are able to telnet the mongodb node ip from databricks noteboo

Getting error, Timed out after 30000 ms while waiting for a server that matches .

[Kaniz_Fatma]

Hi @Sadam97, 

• First, verify if your DNS server is responding. You can do this by running a ping command from a notebook in Databricks to reach your secondary DNS server.
• Launch a Web Terminal from the cluster workspace.
• Edit the /etc/resolv.conf file on the cluster and update the nameserver value with a working DNS server.
• Save the changes and restart systemd-resolved.
• The error you’re encountering (“Timed out after 30000 ms while waiting for a server that matches”) could be related to DNS settings.
• Ensure that your primary DNS is not down or unresponsive.
• Artifacts (such as MongoDB hosts) might not be resolving due to DNS issues.
• If you have a host record listing the artifact public IP as static, check if it has changed.
• Identify a working DNS server and update the DNS entry on the cluster.

Feel free to try these steps, and let me know if you need further assistance! 😊🚀