Hey folks,
Thank you all for the replies. Initially I expected that dhcp-option
would work dynamically or take effect every time the IP of an upstream
server was changed. This was a misunderstanding. If understood right
from all the replies, dhcp-option plays a role only when a dhcp request
On 2020-07-30 08:09, wkitt...@gmail.com wrote:
On 7/29/20 7:59 PM, Dan Schaper wrote:
You've told dnsmasq to send a lease with option 6 (DNS) set to
10.88.13.3. Where dnsmasq forwards the queries to is not relevant to
your issue, you only have one upstream server configured.
are you saying tha
On Thu, Jul 30, 2020 at 02:20:42PM +, Horn Bucking wrote:
>
> On 7/30/20, wkitt...@gmail.com wrote:
>
> > On 7/29/20 7:59 PM, Dan Schaper wrote:
> > > You've told dnsmasq to send a lease with option 6 (DNS) set to
> > > 10.88.13.3. Where dnsmasq forwards the queries to is not relevant to
> >
wkitt...@gmail.com wrote on 7/30/2020 5:09 AM:
> On 7/29/20 7:59 PM, Dan Schaper wrote:
>> You've told dnsmasq to send a lease with option 6 (DNS) set to
>> 10.88.13.3. Where dnsmasq forwards the queries to is not relevant to
>> your issue, you only have one upstream server configured.
>
> are you
On 7/30/20, wkitt...@gmail.com wrote:
On 7/29/20 7:59 PM, Dan Schaper wrote:
You've told dnsmasq to send a lease with option 6 (DNS) set to
10.88.13.3. Where dnsmasq forwards the queries to is not relevant to
your issue, you only have one upstream server configured.
are you saying that this
On 7/29/20 7:59 PM, Dan Schaper wrote:
You've told dnsmasq to send a lease with option 6 (DNS) set to
10.88.13.3. Where dnsmasq forwards the queries to is not relevant to
your issue, you only have one upstream server configured.
are you saying that this
dhcp-option=tag:red,option:dns-server,1
What DNS server does the client MOEDW1CKH5 think is it's DNS? If it's a
linux client then check /etc/resolv.conf to see or sniff the wire for
the DHCP request/response.
You've told dnsmasq to send a lease with option 6 (DNS) set to
10.88.13.3. Where dnsmasq forwards the queries to is not relevant
Here are a few experiments that have been done.
Config file:
port=53
bogus-priv
no-resolv
local=/localnet/
user=dnsmasq
group=dnsmasq
interface=enp5s0
listen-address=127.0.0.1,192.168.13.1
expand-hosts
domain=irlanet.org
dhcp-range=192.168.13.224,192.168.13.255,2h
dhcp-authoritative
cache-size=0
On 2020-07-29 2:40 p.m., S Irlapati wrote:
Thanks for the quick reply.
I have changed it to
dhcp-host=00:a1:b0:08:61:67,floater,tag:red,192.168.13.109
dhcp-host=00:c0:a8:be:ed:d0,Ziong,tag:green,192.168.13.110
dhcp-option=tag:red,option:dns-server,10.88.13.3
dhcp-option=tag:green,option:dns-se
Yes, that was a cut and paste error. I have simplified the file to make
things easier to debug.
Here is what it looks like now, I will paste the whole file here
port=53
bogus-priv
no-resolv
local=/localnet/
user=dnsmasq
group=dnsmasq
interface=enp5s0
listen-address=127.0.0.1,192.168.13.1
expand
On Wed, Jul 29, 2020 at 03:42:27PM -0400, Daryl Richards wrote:
> On 2020-07-29 2:40 p.m., S Irlapati wrote:
> > Thanks for the quick reply.
> >
> > I have changed it to
> >
> > dhcp-host=00:a1:b0:08:61:67,floater,tag:red,192.168.13.109
> > dhcp-host=00:c0:a8:be:ed:d0,Ziong,tag:green,192.168.13.1
dhcp-host=00:a1:b0:08:61:67,floater,set:red,192.168.13.109
> The set: construct sets the tag whenever this *--dhcp-host*
> directive is in use. This can be used to selectively send DHCP options
> just for this host. More than one tag can be set in a *--dhcp-host*
> directive (but not in other plac
On 7/29/20 1:21 PM, S Irlapati wrote:
dhcp-host=00:a1:b0:08:61:67,floater,tag:red,192.168.13.109
dhcp-host=00:c0:a8:be:ed:d0,Ziong,tag:green,192.168.13.110
dhcp-option=tag:red,option:dns-server,10.88.13.3
dhcp-option=tag:green,option:dns-server,10.88.13.4
server=10.88.13.4#53
The above does not
Thanks for the quick reply.
I have changed it to
dhcp-host=00:a1:b0:08:61:67,floater,tag:red,192.168.13.109
dhcp-host=00:c0:a8:be:ed:d0,Ziong,tag:green,192.168.13.110
dhcp-option=tag:red,option:dns-server,10.88.13.3
dhcp-option=tag:green,option:dns-server,10.88.13.4
server=10.88.13.4#53
It sti
Hi Folks,
I am trying to configure dnsmasq to selectively send requests to
different upstream servers based on their IP addresses which have been
given by them by dnsmasq. Here are the relevant lines of code.
dhcp-host=00:a1:b0:08:61:67,floater,tag:red,192.168.13.109
dhcp-host=00:c0:a8:be:ed:
On 28/09/17 17:35, Jeff wrote:
> I have a server my.natted.server NAT'ed behind a public firewall, with
> config lines for both of my upstream ISP nameservers:
> server=
> server=
>
> I chose to use both ISP nameservers for redundancy, but this is not a
> requirement.
>
> I see dnsmasq query eith
I have a server my.natted.server NAT'ed behind a public firewall, with
config lines for both of my upstream ISP nameservers:
server=
server=
I chose to use both ISP nameservers for redundancy, but this is not a
requirement.
I see dnsmasq query either upstream server, without issue. Here are 2
suc
Jay Guerette wrote:
I was surprised; and expecting a load balancing of the 3 configured
servers. The man entry for the 'strict-order' option says:
"... dnsmasq will send queries to any of the upstream servers it knows
about and tries to favour servers to are known to be up..."
I interpreted t
On 3/14/07, Simon Kelley wrote:
Jay Guerette wrote:
> In my dnsmasq.conf I have the following lines:
>
> server=199.2.252.10
> server=204.97.212.10
> server=204.117.214.10
>
> If I run tcpdump to examine the DNS traffic, I'll see something like
> this right after dnsmasq starts:
>
> 15:50:06.302
Jay Guerette wrote:
In my dnsmasq.conf I have the following lines:
server=199.2.252.10
server=204.97.212.10
server=204.117.214.10
If I run tcpdump to examine the DNS traffic, I'll see something like
this right after dnsmasq starts:
15:50:06.302001 IP 10.0.2.10.33109 > 199.2.252.10.53: 35868+
In my dnsmasq.conf I have the following lines:
server=199.2.252.10
server=204.97.212.10
server=204.117.214.10
If I run tcpdump to examine the DNS traffic, I'll see something like
this right after dnsmasq starts:
15:50:06.302001 IP 10.0.2.10.33109 > 199.2.252.10.53: 35868+ A?
www.google.com. (3
21 matches
Mail list logo
