search

TechnitiumSoftware / DnsServer

Technitium DNS Server
https://technitium.com/dns/
GNU General Public License v3.0
4.47k stars 431 forks source link

Access problem to Dashboard #187

Closed 84sigmapit closed 4 years ago

84sigmapit commented 4 years ago

Hello after installation , i cant access to Dashboard panel. It is locked How i can active it ?

ShreyasZare commented 4 years ago

Thanks for the post. How are you trying to access the panel? Is the DNS server installed on the same machine you are trying to access the web panel or is it on another machine on the network? What is the OS on the DNS server?

84sigmapit commented 4 years ago

I completed installation DNS server to my computer. Then when i start program from taskbar i saw Dashboard is not active. You may see in attached Screen Shot. There is no another machine İssue

ShreyasZare commented 4 years ago

Thanks for the details. The Dashboard link is gets disabled when the DNS service is not running. Just check the 'Service' menu and see if the service is running, if not then click on the start menu item. Once the service starts then Dashboard link will get enabled.

84sigmapit commented 4 years ago

I apply exactly what you said.But After 'Service' and 'Start' menu i am getting this attached Adsız error.

ShreyasZare commented 4 years ago

Thanks for the details. Its seems the service is not starting due to some issue. Check once in the Services console for Technitium DNS Server and check its status. To open it press Win+R to start Run and enter services.msc to open Services console.

You can check the DNS server logs and see if there are any errors logged in it. You can find the log files in C:\Program Files (x86)\Technitium\DNS Server\config\logs folder. If you find any errors then post them here.

You can try to reboot Windows once and see if the service is starting. If the service is still not starting then you need to check Windows event logs using the Event Viewer. Find any error that you see in the Event Viewer for the DNS server and post them here.

84sigmapit commented 4 years ago

2020-10-28.log I took logs from (x86)\Technitium\DNS Server\config\logs. Could you check for me

ShreyasZare commented 4 years ago

Thanks for the log file. The issue is that your computer's name contains non ASCII character. The DNS server uses the computer's name as its initial domain name and since the name is not a valid domain name, there is an error causing the DNS server to crash.

I will update the code to fix this issue in next release. But, for now, you can run the DNS server with this workaround:

  1. Change your computer's name to contain only ASCII characters.
  2. Restart the computer so that the system name is updated.
  3. Once the computer starts, the DNS server will start too without any issues.

Let me know if there was any issue with this workaround.

niekvb commented 4 years ago

Same (kind of) problem here:

TechnitiumLibrary.Net.Dns.DnsClientException: Invalid domain name [desktop-pc-]: label cannot end with hyphen.

PC's name is set to: DESKTOP-PC-2

ShreyasZare commented 4 years ago

Same (kind of) problem here:

TechnitiumLibrary.Net.Dns.DnsClientException: Invalid domain name [desktop-pc-]: label cannot end with hyphen.

PC's name is set to: DESKTOP-PC-2

Thanks for the feedback. This will get fixed in the next release.

EHRETic commented 4 years ago

Same (kind of) problem here:

TechnitiumLibrary.Net.Dns.DnsClientException: Invalid domain name [desktop-pc-]: label cannot end with hyphen.

PC's name is set to: DESKTOP-PC-2

Thanks for the feedback. This will get fixed in the next release.

Maaaaann, the day I discover Technitium and try it out, I discover as well that it doesn't support "-" in dns name... and all my machines have one ! ^^

Is it affecting also CentOS ? I've tried both local fqdn and IP, same result, seems not to respond (and firewall is open:

public (active) target: default icmp-block-inversion: no interfaces: ens192 sources: services: cockpit dhcpv6-client dns ssh ports: 5480/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules:

Any fix to try out?

ShreyasZare commented 4 years ago

Same (kind of) problem here:

TechnitiumLibrary.Net.Dns.DnsClientException: Invalid domain name [desktop-pc-]: label cannot end with hyphen.

PC's name is set to: DESKTOP-PC-2

Thanks for the feedback. This will get fixed in the next release.

Maaaaann, the day I discover Technitium and try it out, I discover as well that it doesn't support "-" in dns name... and all my machines have one ! ^^

Is it affecting also CentOS ? I've tried both local fqdn and IP, same result, seems not to respond (and firewall is open:

public (active) target: default icmp-block-inversion: no interfaces: ens192 sources: services: cockpit dhcpv6-client dns ssh ports: 5480/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules:

Any fix to try out?

Its not an issue with "-" in the name, its when the machine name is read and due to the character limit on the name, the "-" comes in the end is when its not acceptable since a domain name cannot end with "-".

The next update will have this fixed so it wont be issue with machine name.

EHRETic commented 4 years ago

Its not an issue with "-" in the name, its when the machine name is read and due to the character limit on the name, the "-" comes in the end is when its not acceptable since a domain name cannot end with "-".

The next update will have this fixed so it wont be issue with machine name.

Mines are srv-xxx-yy.domain.local, is it also "supposed" to be affected? Just to be sure it's not something else... 😉

ShreyasZare commented 4 years ago

Mines are srv-xxx-yy.domain.local, is it also "supposed" to be affected? Just to be sure it's not something else... 😉

I don't know, you tell me if its causing issue. The issue is that Environment.MachineName is returning truncated name and in case there is a "-" at the end then it will cause an issue. Also, if there are non ASCII characters in the name then that too will cause issue since domain names can contain only ASCII characters.

Next update will have a check for this to handle it gracefully.

EHRETic commented 4 years ago

Mines are srv-xxx-yy.domain.local, is it also "supposed" to be affected? Just to be sure it's not something else... 😉

Well, I have an answer now: I've created 2 new VMs from scratch (CentOS 8 server), one with "-" in the name and one without, both worked... so I don't know what happened with the first one, probably a dependency I didn't pay attention before snapshoting it. Voilà! 😄

BTW, if I could get the "how to" SSL the admin console, it would be perfect (it doesn't seems to be in the doc anymore)

Thanks for your replies!

ShreyasZare commented 4 years ago

BTW, if I could get the "how to" SSL the admin console, it would be perfect (it doesn't seems to be in the doc anymore)

Unfortunately the built in web server that is being used does not support SSL. There is a plan to replace it in later updates. For now, I would recommend that you do reverse proxy with nginx or any other web server.

EHRETic commented 4 years ago

Unfortunately the built in web server that is being used does not support SSL. There is a plan to replace it in later updates. For now, I would recommend that you do reverse proxy with nginx or any other web server.

I know how to do that, no worries :-)

EHRETic commented 4 years ago

Unfortunately the built in web server that is being used does not support SSL. There is a plan to replace it in later updates. For now, I would recommend that you do reverse proxy with nginx or any other web server.

So I did install nginx to use SSL for the Dasboard, it's nice to have a secure way to access it.

Note for the people (like me) that doesn't know Linux "so good" : if you have SELinux active, it will not let nginx access another port and you will end up with a 502 gateway error. For me it was pretty easy to solve because SELinux in Cockpit will give you all the required commands but I don't know how this would work if you don't use Cockpit.

My 5 cents, just in case somebody is struggling and getting 502... 😉

ShreyasZare commented 4 years ago

Version 5.5 released which fixes this issue.