DNS resolution¶
DNS resolution not working¶
-
Obtain your Enclave local IP address using the
enclave get-ipcommand.That's the IP address which the local DNS stub resolver will bind to (
udp\53).C:\> enclave get-ip 100.117.177.98 -
Use
nslookupto send a test query to the Enclave nameserver identified in step 1 by attempting to resolve the special DNS name_my.id.enclave. It should resolve to your own local Enclave IP address, the same IP as the nameserver you're querying.C:\> nslookup _my.id.enclave 100.117.177.98 Server: UnKnown Address: 100.117.177.98 Name: _my.id.enclave Address: 100.117.177.98 -
If the DNS query fails, check there isn't other software bound to your Enclave
Local addresson portudp/53 -
If you're running Enclave on a Linux operating system or inside a container, check that DNS queries from the operating system are reaching the local Enclave DNS stub resolver. See DNS for details on how Enclave's split-tunnel DNS works.
-
Some ISPs hijack DNS queries to serve ads. Check that your primary recursive nameserver correctly returns a
SERVFAILresponse when queried with a hostname it should be unable to resolve. Some ISPs run nameservers which return IP addresses for ad servers instead of aSERVFAILfor non-existent domains. The ping request shown below to the non-existing hostnamenull.enclave.ioshould fail. If it does not, your ISPs nameservers may be hijacking your DNS requests to serve ads, in which case we recommend contacting your ISP to disable this function or switching to another primary resolver.C:\> ping null.enclave.io Ping request could not find host null.enclave.io. Please check the name and try again.
DNS queries slow to complete¶
- On Windows, check that the Enclave network interface doesn't list more than one DNS nameserver. If it does, please remove the DNS server that does not match the Enclave
Local addressshown by theenclave get-ipcommand.
If you're still experiencing DNS issues after working through this checklist, see collecting logs and contact support.