Re: [Dnsmasq-discuss] Problem with server=/local/127.0.0.1

2018-12-13 Thread Geert Stappers
On Thu, Dec 13, 2018 at 08:47:39PM +0300, Denis wrote: > On Thu, 13 Dec 2018 09:54:44 +0100 Geert Stappers wrote: > > On Thu, Dec 13, 2018 at 07:44:14AM +0300, Denis wrote: > > > Hello, everyone! > > > > > > In my dnsmasq.conf "server=/local/127.0.0.1" doesn't seem to work. > > > At least, it does

Re: [Dnsmasq-discuss] Problem with server=/local/127.0.0.1

2018-12-13 Thread Denis
My configuration: Manjaro Linux, 32-bit, one ethernet card. It is connected to a router with a cable, the router is connected to my ISP also with a cable. A netbook is connected to the router via Wi-Fi. On the PC: Avahi is installed and enabled (avahi-daemon active), systemd-resolved is disable

Re: [Dnsmasq-discuss] Problem with server=/local/127.0.0.1

2018-12-13 Thread Denis
In my previous letter there is a typo of course; "In all these cases my PC's ip address (192.168.1.2) is NOT resolved to my PC's name (DenDesktop)" On Thu, 13 Dec 2018 09:54:44 +0100 Geert Stappers wrote: > On Thu, Dec 13, 2018 at 07:44:14AM +0300, Denis wrote: > > Hello, everyone! > > > > In

[Dnsmasq-discuss] DHCP from dnsmasq in docker container

2018-12-13 Thread Craig Younkins
First, thank you for dnsmasq! I'm among a number of people[1][2][3][4] having trouble using dnsmasq for DHCP when it is running in a docker container. Everyone seems to get "no address range available for DHCP request via eth0" in their log unless they change to host networking mode. The code pat

Re: [Dnsmasq-discuss] Problem with server=/local/127.0.0.1

2018-12-13 Thread Geert Stappers
On Thu, Dec 13, 2018 at 07:44:14AM +0300, Denis wrote: > Hello, everyone! > > In my dnsmasq.conf "server=/local/127.0.0.1" doesn't seem to work. At > least, it doesn't work how I thought it was supposed to work. I was > under the impression that server=/$domainname/$address should cause the > $dom