Exactly, thanks for the tip, Daryl.
Additionally to the resolv.conf change I had to adjust dnsmasq.conf as well
with two listen-addresses:
listen-address=127.0.0.1
listen-address=192.168.1.1 #SERVER1 IP
server=8.8.8.8 #the upstream DNS for WAN resolving, I chose google here, this
could be open-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks for the heads-up. It took 'till 2.75 to get a stable release,
but I'm back to committing fixes now, and I'll include this.
Cheers,
Simon.
On 05/08/15 12:39, Ermanno Scaglione wrote:
> Hi, what about this (minor) issue?
>
> On Tue, Jun 9,
I would say that you need to change the server's /etc/resolv.conf to
point to 127.0.0.1 as the nameserver...
On 2015-08-04 7:39 AM, Mayk Eskilla wrote:
Resend, had to loose HTML coding in my mailer, sry for that!
My dnsmasq server does a fine job offering dhcp leases to clients and
nameservic
