Current DNS Resolver none available?

ronaldrichard123 · ‎04-26-2017

My DNSCrypt stopped working today. Yes, it's an outdated version. But up until yesterday, it works normally. It says that current DNS resolver is none available.

support.opendns.com_hc_user_images_zaNBvsD2HYSE3ly-molY7Q.png

What could cause this to happen? Is it because my ISP managed to block it, or is it because the server down? And is there a way to fix this? Thx.

rotblitz · ‎04-26-2017

Copy & paste the complete plain text outputs of the following diagnostic commands to here:

nslookup -type=txt debug.opendns.com.
nslookup whoami.akamai.net.
nslookup -vc -port=443 -type=txt debug.opendns.com. 208.67.220.220
netsh interface ip show config

ronaldrichard123 · ‎04-27-2017

support.opendns.com_hc_user_images_tMpZYUCi6Q3eY_6aWQbk9w.png

ronaldrichard123 · ‎04-27-2017

If i unchecked the enable DNSCrypt, the DNS resolver shows up.

support.opendns.com_hc_user_images_91sICyftBUa4aCHGd3yW9A.png

But when i checked it, it says none available, and there's no connection at all to the internet.

rotblitz · ‎04-27-2017

These are not plain text outputs, but screen shots. :(

"Is it because my ISP managed to block it, or is it because the server down?"

None of those! It's just you.

As can be easily seen, you send your DNS traffic to 2001:4860:4860::8888 (Google public DNSv6), not to 127.0.0.1 where DNSCrypt is listening to for forwarding to 208.67.220.220. Also, this Google DNSv6 resolver is sub-optimal for you, because they respond too slowly anyway, and your queries allmost time out. :(

Visit https://github.com/jedisct1/dnscrypt-proxy/blob/master/README-WINDOWS.markdown, look for IPv6, and follow the instructions there to rectify this.

Beside the IPv6 issue, you have another problem that your IP address 103.213.130.164 is not registered with your network at https://dashboard.opendns.com/settings/ so that OpenDNS cannot associate your DNS queries with your account, and your dashboard settings cannot take effect. Update your IP address information there, and run an Updater going further.

The following command should show if there is success for both of your problems:

nslookup -type=txt debug.opendns.com.

ronaldrichard123 · ‎04-27-2017

Sorry about that screenshots. I don't know how to copy paste the words in cmd, so i decided to printscreen instead.

I don't quite understand about that IPv6 problem thing. I tried going to network sharing center > change adapter service > select my hotspot connection > properties > IPv6 > and tried to enter use the following dns, but it says it's invalid.

support.opendns.com_hc_user_images_5oQIcHdknfoSTCMS9jhhBg.png

Did i make a mistake or something? I'm not quite knowledgeable about computer programming, so sorry if i'm bothering you with this trivial things. Thx.

rotblitz · ‎04-27-2017

"I don't know how to copy paste the words in cmd"

But the internet knows. A simple search will reveal it.

"I don't quite understand about that IPv6 problem thing."

What is it that you don't understand? What would be your questions related to this which cannot be answered by an internet search?

"Did i make a mistake or something?"

Yes, you did. You must thoroughly read and exactly do as instructed. You should not enter the IPv4 address 127.0.0.1, but its IPv6 representation with a value of ::ffff:127.0.0.1. Copying for your convenience:

In the preferences pane for a given network connection, Windows has IPv6-specific settings under "Internet Protocol Version 6 (TCP/IPv6)".

The DNS server addresses have to be IPv6 addresses, so enter the IPv6 representation of 127.0.0.1:

::FFFF:127.0.0.1

"I'm not quite knowledgeable about computer programming"

Absolutely no programming is needed here. Don't even attempt it!

ronaldrichard123 · ‎04-27-2017

Please forgive me for my lack of knowledge. Not only i know nothing about programming, it seems that i also lack of knowledge about computer terms and language. I don't quite catch what the guide mean by IP representation, since this is the first time i heard about that term. I thought it was some command prompt code, so i tried typing that code (::ffff:127.0.0.1) in cmd, which obviously did nothing at all. Also, i'm also not that fluent in english, which make me misunderstood the meaning of that guide. Please forgive me for my stupidity.

I did everything you told me to. I changed the IPv6 setting and use the ::ffff:127.0.0.1. I also register my IP at OpenDNS dashboard. But, the DNSCrypt still shows that the current resolver is none.

support.opendns.com_hc_user_images_xvY1rwSb8pHN-E2sSxryNw.png

The OpenDNS Updater says that there's no internet connectivity. But if i close the DNSCrypt 0.0.6 program, or simply unchecked the enable DNSCrypt, the internet works fine.

rotblitz · ‎04-27-2017

I need to see the output of the following commands, ideally as plain text:

netsh interface ip show config
netsh interface ipv6 show dns
nslookup -type=txt debug.opendns.com.
nslookup whoami.akamai.net.

ronaldrichard123 · ‎04-27-2017

C:\Users\Asus>netsh interface ip show config

Configuration for interface "Wireless Network Connection 4"
DHCP enabled: Yes
InterfaceMetric: 5
DNS servers configured through DHCP: None
Register with which suffix: Primary only
WINS servers configured through DHCP: None

Configuration for interface "Wireless Network Connection"
DHCP enabled: Yes
IP Address: 192.168.100.3
Subnet Prefix: 192.168.100.0/24 (mask 255.255.255.0)
Default Gateway: 192.168.100.1
Gateway Metric: 0
InterfaceMetric: 25
Statically Configured DNS Servers: 127.0.0.1
Register with which suffix: Primary only
WINS servers configured through DHCP: None

Configuration for interface "Local Area Connection"
DHCP enabled: Yes
InterfaceMetric: 5
DNS servers configured through DHCP: None
Register with which suffix: Primary only
WINS servers configured through DHCP: None

Configuration for interface "Loopback Pseudo-Interface 1"
DHCP enabled: No
IP Address: 127.0.0.1
Subnet Prefix: 127.0.0.0/8 (mask 255.0.0.0)
InterfaceMetric: 50
Statically Configured DNS Servers: None
Register with which suffix: Primary only
Statically Configured WINS Servers: None

C:\Users\Asus>netsh interface ipv6 show dns

Configuration for interface "Wireless Network Connection 4"
DNS servers configured through DHCP: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Register with which suffix: Primary only

Configuration for interface "Wireless Network Connection"
DNS servers configured through DHCP: ::ffff:127.0.0.1
Register with which suffix: Primary only

Configuration for interface "Local Area Connection"
DNS servers configured through DHCP: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Register with which suffix: Primary only

Configuration for interface "Loopback Pseudo-Interface 1"
Statically Configured DNS Servers: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Register with which suffix: Primary only

Configuration for interface "isatap.{20CADD30-C941-47FB-A7DF-522C1672C9FB}"
Statically Configured DNS Servers: None
Register with which suffix: None

Configuration for interface "Local Area Connection* 17"
Statically Configured DNS Servers: None
Register with which suffix: None

Configuration for interface "Local Area Connection* 26"
Statically Configured DNS Servers: None
Register with which suffix: None

Configuration for interface "Local Area Connection* 27"
Statically Configured DNS Servers: None
Register with which suffix: None

C:\Users\Asus>nslookup -type=txt debug.opendns.com.
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 127.0.0.1

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Users\Asus>nslookup whoami.akamai.net.
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 127.0.0.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Users\Asus>

rotblitz · ‎04-28-2017

It looks like you didn't have DNSCrypt running and enabled at this time, because all DNS queries timed out. Enable it and post the outputs of the following commands again:

nslookup -timeout=8 -type=txt debug.opendns.com.
nslookup -timeout=8 whoami.akamai.net.

If the queries still time out, reboot the PC, ensure DNSCrypt is running and try the commands again.

ronaldrichard123 · ‎04-28-2017

I tried to unchecked and checked the enable DNSCrypt again, but the status still says unprotected, even though the enable DNSCrypt is checked.

support.opendns.com_hc_user_images_DwM0xSzNTFZrljXToZ7_Qg.png

The command prompt still shows DNS request time out.

C:\Users\Asus>nslookup -timeout=8 -type=txt debug.opendns.com.
DNS request timed out.
timeout was 8 seconds.
Server: UnKnown
Address: 127.0.0.1

DNS request timed out.
timeout was 8 seconds.
*** Request to UnKnown timed-out

C:\Users\Asus>nslookup -timeout=8 whoami.akamai.net.
DNS request timed out.
timeout was 8 seconds.
Server: UnKnown
Address: 127.0.0.1

DNS request timed out.
timeout was 8 seconds.
DNS request timed out.
timeout was 8 seconds.
*** Request to UnKnown timed-out

I have tried reboot the laptop, but still, the DNSCrypt 0.0.6 shows that there's no connection.

There's something strange happened though. Everytime i first open the DNSCrypt program, the icon did become green. But only for a second. Soon after it became green, it turns back red again.

support.opendns.com_hc_user_images_fcGyIUFjrwXtSxKm12RA4g.png

That's what shows when i first starts the program. But it only last for about 1 second.

rotblitz · ‎04-28-2017

I need to see the following plain text command output with DNSCrypt started and reaching the red status:

netstat -na | find ":53 "

(Could be that there is not really an output...)

ronaldrichard123 · ‎04-28-2017

C:\Users\Asus>netstat -na | find ":53"
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING
TCP [::]:5357 [::]:0 LISTENING
UDP 0.0.0.0:5355 *:*
UDP 192.168.100.3:5353 *:*
UDP [::]:5355 *:*

The result of when it's green at the start and when it already turn red is the same.

rotblitz · ‎04-28-2017

(You forgot the space after :53 so I see also what's with other ports - no problem though.)

What I can see is that nothing listens on port 53 (the DNS port), so your DNSCrypt is no longer functioning, generally not, no matter if it shows green for a short while or not. This is also the reason why your DNS queries timed out - there is nothing which could respond to them.

I have no idea how to fix this with this very old version. Because this version was still issued by OpenDNS (today's versions are not), you may open a support ticket with OpenDNS, in case they are still willing to provide support for this old version.

If you still have the installer for this version 0.0.6, you may try with uninstalling and reinstalling it to see if this helps.

Another option would be to uninstall this old version and to install and use a current version from https://dnscrypt.org/.