windows error - Githubissues

liang-hiwin commented 3 years ago

[2020-12-13 04:26:25 UTC] Logging started.
[2020-12-13 04:26:25 UTC] DHCP Server successfully saved scope file: C:\Program Files (x86)\Technitium\DNS Server\config\scopes\Default.scope
[2020-12-13 04:26:25 UTC] DNS Server config file was not found: C:\Program Files (x86)\Technitium\DNS Server\config\dns.config
[2020-12-13 04:26:25 UTC] DNS Server is restoring default config file.
[2020-12-13 04:26:25 UTC] DNS Server config file was saved: C:\Program Files (x86)\Technitium\DNS Server\config\dns.config
[2020-12-13 04:26:25 UTC] DNS Server is loading allowed zone file: C:\Program Files (x86)\Technitium\DNS Server\config\allowed.config
[2020-12-13 04:26:25 UTC] DNS Server is loading blocked zone file: C:\Program Files (x86)\Technitium\DNS Server\config\blocked.config
[2020-12-13 04:26:25 UTC] [0.0.0.0:53] [UDP] DNS Server was bound successfully.
[2020-12-13 04:26:25 UTC] [0.0.0.0:53] [TCP] DNS Server was bound successfully.
[2020-12-13 04:26:25 UTC] [[::]:53] [UDP] DNS Server was bound successfully.
[2020-12-13 04:26:25 UTC] [[::]:53] [TCP] DNS Server was bound successfully.
[2020-12-13 04:26:25 UTC] DHCP Server successfully loaded scope: Default
[2020-12-13 04:26:25 UTC] DHCP Server successfully loaded scope file: C:\Program Files (x86)\Technitium\DNS Server\config\scopes\Default.scope
[2020-12-13 04:26:25 UTC] [0.0.0.0:5380] Web Service (v5.5.0.0) was started successfully.
[2020-12-13 04:26:45 UTC] [10.10.10.104:0] [admin] User logged in.
[2020-12-13 04:26:46 UTC] [10.10.10.104:0] Check for update was done {updateAvailable: False; updateVersion: 5.5; displayText: New Update (v5.5) Available!; downloadLink: https://download.technitium.com/dns/DnsServerSetup.zip;}
[2020-12-13 04:26:56 UTC] DNS Server config file was saved: C:\Program Files (x86)\Technitium\DNS Server\config\dns.config
[2020-12-13 04:26:56 UTC] [10.10.10.104:0] [admin] Password was changed for user.
[2020-12-13 04:27:38 UTC] [10.10.10.104:0] [admin] DNS Settings were updated {serverDomain: desktop-tang; dnsServerLocalEndPoints: 0.0.0.0:53,[::]:53; webServicePort: 5380; enableDnsOverHttp: False; enableDnsOverTls: False; enableDnsOverHttps: False; tlsCertificatePath: ; preferIPv6: False; logQueries: False; allowRecursion: True; allowRecursionOnlyForPrivateNetworks: True; proxyType: none; forwarders: https://idns.removed.com/dns-query; forwarderProtocol: HttpsJson; blockListUrl: false;}
[2020-12-13 04:27:38 UTC] DNS Server config file was saved: C:\Program Files (x86)\Technitium\DNS Server\config\dns.config
[2020-12-13 04:28:07 UTC] [10.10.10.104:0] System.Net.Sockets.SocketException (0x80004005): 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。
   在 TechnitiumLibrary.Net.Dns.DnsClient.<>c__DisplayClass36_0.<<InternalResolveAsync>g__DoResolveAsync|1>d.MoveNext()
--- 引发异常的上一位置中堆栈跟踪的末尾 ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 TechnitiumLibrary.Net.Dns.DnsClient.<InternalResolveAsync>d__36.MoveNext()
--- 引发异常的上一位置中堆栈跟踪的末尾 ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 TechnitiumLibrary.Net.Dns.DnsClient.<ResolveAsync>d__40.MoveNext()
--- 引发异常的上一位置中堆栈跟踪的末尾 ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 DnsServerCore.WebService.<ResolveQuery>d__87.MoveNext()
--- 引发异常的上一位置中堆栈跟踪的末尾 ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 DnsServerCore.WebService.<ProcessRequestAsync>d__37.MoveNext()
[2020-12-13 04:28:30 UTC] [10.10.10.104:0] System.Net.Sockets.SocketException (0x80004005): 向一个无法连接的网络尝试了一个套接字操作。
   在 TechnitiumLibrary.Net.Dns.DnsClient.<>c__DisplayClass36_0.<<InternalResolveAsync>g__DoResolveAsync|1>d.MoveNext()
--- 引发异常的上一位置中堆栈跟踪的末尾 ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 TechnitiumLibrary.Net.Dns.DnsClient.<InternalResolveAsync>d__36.MoveNext()
--- 引发异常的上一位置中堆栈跟踪的末尾 ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 TechnitiumLibrary.Net.Dns.DnsClient.<ResolveAsync>d__40.MoveNext()
--- 引发异常的上一位置中堆栈跟踪的末尾 ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 DnsServerCore.WebService.<ResolveQuery>d__87.MoveNext()
--- 引发异常的上一位置中堆栈跟踪的末尾 ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 DnsServerCore.WebService.<ProcessRequestAsync>d__37.MoveNext()
[2020-12-13 04:29:58 UTC] [10.10.10.104:0] DnsServerCore.WebServiceException: Invalid username or password: admin
   在 DnsServerCore.WebService.<LoginAsync>d__53.MoveNext()
--- 引发异常的上一位置中堆栈跟踪的末尾 ---
   在 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   在 DnsServerCore.WebService.<ProcessRequestAsync>d__37.MoveNext()
[2020-12-13 04:29:59 UTC] [10.10.10.104:0] [admin] User logged in.
[2020-12-13 04:30:00 UTC] [10.10.10.104:0] Check for update was done {updateAvailable: False; updateVersion: 5.5; displayText: New Update (v5.5) Available!; downloadLink: https://download.technitium.com/dns/DnsServerSetup.zip;}

ShreyasZare commented 3 years ago

Thanks for the feedback. It seems there is network connectivity issue so the DNS server is unable to resolve names.

Use DNS Client to query directly to the forwarder that you are using or if no forwarder is configured then do "Recursive Query" option as server. This test will tell if the DNS server can reach the forwarder or the name servers.

liang-hiwin commented 3 years ago

The DOH transponder I configured works normally. But it seems to have no effect in the DnsServer program.

ShreyasZare commented 3 years ago

From the logs you have it configured with HttpsJson protocol that could be the reason since most DoH servers support only Https wire format protocol and only a few support json format protocol.

Do try querying the forwarder directly from DNS Client and confirm if its working.

liang-hiwin commented 3 years ago

From the logs you have it configured with HttpsJson protocol that could be the reason since most DoH servers support only Https wire format protocol and only a few support json format protocol.

Do try querying the forwarder directly from DNS Client and confirm if its working.

It seems that the ip of the doh domain name I configured cannot be resolved and the dns fails. Do I need to add ip after doh? For example: https://dns.google/dns-query(8.8.8.8);

ShreyasZare commented 3 years ago

ya its best to add IP after the URL ends. The syntax is to add <space> and then put the IP address in round brackets,

liang-hiwin commented 3 years ago

ya its best to add IP after the URL ends. The syntax is to add <space> and then put the IP address in round brackets,

## doh cannot be used. dot is normal

C8RDE1SO`WNBSN`4RAF)9EB 377ZK$4RS6XFC8)XERWLVKF }Y2GM@%9AJ6`_YQ0SIYHB5L $(AI5$2_GS$795QVGNJ{GH)2$

liang-hiwin commented 3 years ago

error dns https://www.114dns.com/

S6_8V)3M33BI5L1H%WZWZ@T

~P~)$1W_XRL6Y314ZHTKLTP

ShreyasZare commented 3 years ago

Use Google DoT then if that is working.

I don't know anything of the other IP addresses that you are trying to use as forwarders so I cannot tell anything about them not working.

Basically, if you can query any server via the DNS Client then you can use it as forwarder. If the forwarder you wish to use does not work then its network connectivity issue for which nothing can be done from my end.

liang-hiwin commented 3 years ago

The video I recorded has been sent to your mailbox, please check it out.

ShreyasZare commented 3 years ago

The video I recorded has been sent to your mailbox, please check it out.

I saw the video and it seems you really confused:

When you set forwarder in the DNS server, to test it from DNS Client you must select "This Server" and then query. What you are doing is just changing the forwarder in settings and in DNS Client querying to some other server and thinking that the response came from local DNS server.
When you query "This Server" for google.com once and then change the forwarder in settings and then query "This Server" again for google.com then the response you get comes from the cache. Its not coming from the new forwarder. You need to flush cache if you change forwarder and then query This Server to test.
Instead of changing forwarders frequently and testing via DNS Client, you must test the server you want to use as forwarder by querying via DNS Client. If you can query the server via DNS Client and are getting suitable response then you go and set it as forwarder in settings.
I just tested the DoH end point you are trying to configure and its working well here. Just query to <removed> as the server in DNS Client with protocol set to Http and it should work, If its working then set the complete string as the forwarder in settings with DNS-over-HTTPS protocol and it will work since it worked when you queried with DNS Client.

ShreyasZare commented 3 years ago

Another thing from the video:

The DNS server does not support tls://server:port type URL syntax for DoT so it wont work at all. You need to use <domain>:<port> and use TLS protocol. Optionally you can add the IP address to avoid resolution so the TLS server becomes <domain>:<port> (<ip-address>).
There is "Name server returned error. DNS RCODE: ServerFailure (2); Name server: desktop-tang:53 (127.0.0.1:53)" error in your logs as well as in video. This is indicating the the DNS server is trying to query desktop-tang:53 (127.0.0.1:53) which is itself and thus not getting any response. Check if you have configured any zone as conditional forwarder that could affect the resolution process.

ShreyasZare commented 3 years ago

I am not sure why its not working there. But, it does work and you can test it using dnsclient.net hosted tool here: https://dnsclient.net/

Since you tested this on another command line tool and it was working there, you can install Wireshark tool on your system and see what IP address the command line tool is sending the request to. You wont see the request since its encrypted but you will see the IP address and then use the same IP address.

liang-hiwin commented 3 years ago

I am not sure why its not working there. But, it does work and you can test it using dnsclient.net hosted tool here: https://dnsclient.net/

Since you tested this on another command line tool and it was working there, you can install Wireshark tool on your system and see what IP address the command line tool is sending the request to. You wont see the request since its encrypted but you will see the IP address and then use the same IP address.

I can't find the reason for windows. I switch Raspberry Pi to try

liang-hiwin commented 3 years ago

I am not sure why its not working there. But, it does work and you can test it using dnsclient.net hosted tool here: https://dnsclient.net/

Since you tested this on another command line tool and it was working there, you can install Wireshark tool on your system and see what IP address the command line tool is sending the request to. You wont see the request since its encrypted but you will see the IP address and then use the same IP address.

Raspberry Pi is used normally, I'm about to cry

ShreyasZare commented 3 years ago

Raspberry Pi is used normally, I'm about to cry

Good to know its working at least on your Pi.

liang-hiwin commented 3 years ago

Raspberry Pi is used normally, I'm about to cry

Good to know its working at least on your Pi.

thank you

ShreyasZare commented 3 years ago

welcome :)

liang-hiwin commented 3 years ago

Can you help me delete the DOH address mentioned in this discussion! I'm afraid of being vandalized!

liang-hiwin commented 3 years ago

@ShreyasZare

ShreyasZare commented 3 years ago

Can you help me delete the DOH address mentioned in this discussion! I'm afraid of being vandalized!

done

TechnitiumSoftware / DnsServer

windows error #207