> On 11/05/2022 12:41, Kamil via Dnsmasq-discuss wrote:
> > Hi!
> >
> > I've configured Dnsmasq with the following config:
> >
> > interface=eth0
> > bind-interfaces
> > dhcp-option=3,192.168.6.1
> > dhcp-option=6,8.8.8.8
> > set long-lasting records.
> > dhcp-range=192.168.
On 5/13/22 3:48 PM, Simon Kelley wrote:
So queries are being received, and answered, but the reply is being dropped by
the kernel because the send queue is full of replies to dead hosts? If the hosts
are dead, where are the queries coming from to generate these blocked replies?
reading the OP
On 10/05/2022 16:40, Tom Keddie via Dnsmasq-discuss wrote:
Hi All,
I think you're saying that it's not surprising that dnsmasq is not
reading from the socket because the send queue is also full.
As per this thread on netdev
(https://lore.kernel.org/netdev/cabuuw65r3or9hehsmt_isvx1f-
Set the configuration --log-queries.
That will allow you to see if the queries are getting to dnsmasq, and it
will give you a full dump of the DNS cache (including DHCP derived
names) if you send the dnsmasq process SIGUSR1.
Both of these will help in diagnosing the problem.
Cheers,
Simon.
On 11/05/2022 12:41, Kamil via Dnsmasq-discuss wrote:
Hi!
I've configured Dnsmasq with the following config:
interface=eth0
bind-interfaces
dhcp-option=3,192.168.6.1
dhcp-option=6,8.8.8.8
set long-lasting records.
dhcp-range=192.168.6.11,192.168.6.20,255.255.255.0,12h
I think you should be able to use dhcp-mac to assign tags, then use
separate dhcp-range only for selected tags. If you are able to create
patterns matching this way, no external script would be required.
dhcp-mac=set:special,AA:BB:CC:*:*:*
dhcp-range=tag:special,192.168.2.2,192.168.2.255
dhcp-ran
