iTHiNDiL 0 Posted December 26, 2020 Share Posted December 26, 2020 Yes, by default it's disabled but i did enable the scope and restart the container just in case. The problem is that the port UDP 67 it's closed when I test the port with PortQryUI, it's a tool that I use at my work with this purpose. That is why the DHCP server can't receive the broadcasts DHCPDISCOVER and respond with an DHCPOFFER message to the client, or at least that is what I thinks it's the problem. I really don't know why it's not maping the port UDP 67 from the container to the Host, this is as far i can go. Maybe it's this? At file Dockerfile.amd64: Only port 5380 and 53/upd are maped here. Quote Link to post
Roxedus 61 Posted December 26, 2020 Author Share Posted December 26, 2020 As I noted in this PR. Expose is not the issue. https://github.com/Roxedus/docker-TS-DnsServer/pull/2#issuecomment-751127753 Quote Link to post
Roxedus 61 Posted December 26, 2020 Author Share Posted December 26, 2020 Are you using macvlan? Quote Link to post
iTHiNDiL 0 Posted December 27, 2020 Share Posted December 27, 2020 Nope, I was using bridge and after your question I did tried to use a manually created network, didnt' work I also tried to use host and curiously port 67 was not maped: Quote Link to post
faicec 0 Posted January 9 Share Posted January 9 (edited) Afternoon, Running two dockers of this application, both updated overnight and neither are functional this morning. Attempted a redeploy, however the same error regarding .net 5 is visible in the logs: It was not possible to find any compatible framework version The framework 'Microsoft.NETCore.App', version '5.0.0' was not found. - The following frameworks were found: 3.1.0 at [/usr/share/dotnet/shared/Microsoft.NETCore.App] You can resolve the problem by installing the specified framework and/or SDK. The specified framework can be found at: - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=5.0.0&arch=x64&rid=alpine.3.12-x64 It was not possible to find any compatible framework version Edit - This has been reported on the project page by another user. Craig Edited January 9 by faicec found report on github Quote Link to post
alientim 0 Posted January 10 Share Posted January 10 Just a Solution until they Update it, You can Easly downgrad by set a direct release. Edit your Docker Repo from roxedus/ts-dnsserver to roxedus/ts-dnsserver:2021-01-01_22.08 for the last working release as static. Quote Link to post
iTHiNDiL 0 Posted January 11 Share Posted January 11 On 1/9/2021 at 3:03 PM, faicec said: Afternoon, Running two dockers of this application, both updated overnight and neither are functional this morning. Attempted a redeploy, however the same error regarding .net 5 is visible in the logs: It was not possible to find any compatible framework version The framework 'Microsoft.NETCore.App', version '5.0.0' was not found. - The following frameworks were found: 3.1.0 at [/usr/share/dotnet/shared/Microsoft.NETCore.App] You can resolve the problem by installing the specified framework and/or SDK. The specified framework can be found at: - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=5.0.0&arch=x64&rid=alpine.3.12-x64 It was not possible to find any compatible framework version Edit - This has been reported on the project page by another user. Craig Same problem here, but I belive that the issue i'ts not on Technitium DNS Server, the container do not contain Framework 5.0 files. @Roxedus, if you have a moment can you confirm that the problem is on the container? thanks Quote Link to post
Roxedus 61 Posted January 11 Author Share Posted January 11 17 minutes ago, iTHiNDiL said: problem is on the container? It was. They have hid their changelog in a way that there is no reliable way to get notifications. They silently updated the requirements. Runs on latest build 1 Quote Link to post
iTHiNDiL 0 Posted January 11 Share Posted January 11 (edited) On 1/11/2021 at 10:19 AM, Roxedus said: It was. They have hid their changelog in a way that there is no reliable way to get notifications. They silently updated the requirements. Runs on latest build Thanks for your quick response @Roxedus. Folks, until the latest version of the container is updated with the Framwork 5.0 files we must change the tag as @alientim said: On 1/10/2021 at 5:47 AM, alientim said: Just a Solution until they Update it, You can Easly downgrad by set a direct release. Edit your Docker Repo from roxedus/ts-dnsserver to roxedus/ts-dnsserver:2021-01-01_22.08 for the last working release as static. Edit: Already working with "latest" tag Edited January 14 by iTHiNDiL Quote Link to post
iTHiNDiL 0 Posted January 16 Share Posted January 16 On 12/21/2020 at 9:48 AM, iTHiNDiL said: Hi @Roxedus, After some research I decided to install this container to have an DNS with sinkhole capabilites and DHCP server in single container and not deploying a VM for that but I'm having problems with the DHCP server I deployed the container as Custom:br0 with custom IP 192.168.1.200 but after setting up the DHCP pool no device in my internal network is able to receive any IP configuration from the DCHP server. I tried to add UDP port 67 for the DHCP discovery just in case but it's not working. The DNS server is working without any problems as my internal DNS server but nothing to do with DHCP. I check the port 67 and it's closed/filtered. I'm a newbie with containers but maybe the container needs some modifications for the port 67? You can call me crazy or something worse but after more digging i saw that at the bottom of Dockerfile.amd64 there is a line that looks like "expose" ports for the container: EXPOSE 5380 53/udp, maybe can be changed to add port 67/udp and then DHCP will be accesible? Thanks. After the last update DHCP start working without a problem, looks like they fixed, whatever it was ... Quote Link to post
erlipton 1 Posted February 4 Share Posted February 4 (edited) @Roxedus there's a bug in the ts-dnsserver docker... if I set a specific port on docker initial setup (example 8180) then the server's settings page will not update the auto-filled port from 5380 --> 8180. Result, if you update a setting unrelated to the port, it will actually also update to 5380 & confuse the hell out of me for 20 minutes Edited February 4 by erlipton so that i sound smarter than i actually am Quote Link to post
Roxedus 61 Posted February 4 Author Share Posted February 4 10 hours ago, erlipton said: settings page will not update the auto-filled This is not a bug. The container has no idea what port you set on the host-side. Quote Link to post
xPliZit_xs 3 Posted February 5 Share Posted February 5 Hi, would it be possible to have this TS-DNSSERVER work together with DNScrypt-Proxy running on another machine? I currently have a unbound dns server forwarding to dnscrypt-proxy on another machine and wanted to give this docker a try but i dont want to miss out on the features of dnscryp-proxy. Thanks. Quote Link to post
iTHiNDiL 0 Posted February 15 Share Posted February 15 (edited) Hi @Roxedus, The DNS resolution stop working last night after updating the container with the latest version. After performing some tests the port 53 is closed from the network to the container. Edited February 15 by iTHiNDiL Quote Link to post
Roxedus 61 Posted February 16 Author Share Posted February 16 I didnt touch anything, if anything changed it had to be technium pushing a update thats not in the changelog, or that one of the few dependencies broke something. Quote Link to post
40 posts in this topic Last Reply
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.