Hey Simon,
IANA assigned two new RRTypes yesterday:
HHIT 67 Hierarchical Host Identity Tag
BRID 68 UAS Broadcast Remote Identification
https://www.iana.org/go/draft-ietf-drip-registries-28
It should be safe to add them to dnsmasq at this point.
Best,
Dominik
servers? My interpretation
is that they shouldn't be sent upstream here...
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
is an instant fix
for me.
Best,
Dominik
Am 2/6/25 um 6:50 PM schrieb Simon Kelley:
Great, thanks. patch applied and rc2 tagged.
Cheers,
Simon.
On 2/6/25 12:02, Helge Deller wrote:
Some of my PA-RISC UNIX machines boot remotely via tftp, but dnsmasq
randomly fails to deliver (the ident
come back to you once
we find something more sturdy.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
isconnects (and the TCP fork exits
accordingly), the received reply will never be received and find its way
in the mother process's cache.
Could we postpone the shutdown of TCP forks in case a refreshment query
is still ongoing?
Best,
Dominik
ready rings a bell as to what may be happening (like maybe
not resetting the next server to be used, etc.) in case of a config like
the one I described above.
Best
Dominik
Am 1/23/25 um 1:37 AM schrieb Simon Kelley:
I tagged and pushed 2.91test9.
I'm hoping to go to a release candidate ne
dhcp-host=AA:BB:CC:DD:EE:FF,192.168.1.5,server,infinite
Best,
Dominik
On 02.12.24 00:53, Simon Kelley wrote:
Patch applied.
Thanks for your contribution!
Cheers,
Simon.
On 11/27/24 12:40, Reynir Björnsson wrote:
Please find below a patch that will error out on multiple host names
passed to -
Hey all,
and another one: DSYNC
I add all three patches to this mail for completeness.
Best,
Dominik
On 26.07.24 19:59, Dominik Derigs wrote:
Dear Simon,
this week three additional RRTypes NXNAME (128), CLA (263), and IPN
(264) have been added, patch meant to come on top of my previous
Hey Simon,
a very simple fix for PXE packets not always counted for the metrics
attached.
Best,
Dominik
From 7f07ee96f01eae3a924b928ae0766e82a7d79af3 Mon Sep 17 00:00:00 2001
From: Dominik Derigs
Date: Fri, 6 Dec 2024 19:48:31 +0100
Subject: [PATCH] Count PXE packet
Signed-off-by: Dominik
but maybe we can improve logging for this case. I
will send the pcap in a second mail off-list as the record itself
contains sensitive information about my local network.
Dynamically switching over to TCP on UDP truncation seems to be working
as expected.
I wil
patch gets merged, when and, if.
Best,
Dominik
On 07.10.24 02:13, Erik Karlsson wrote:
Hi everyone,
Does anyone have something to say about this patch? I sent it for the
first time about 6 months ago but the discussion quickly died down and
it seems to have been forgotten about since then.
To
:46:53 dnsmasq[1861633]: 25 127.0.0.1/45027 reply is truncated
For testing, "dig +ignore + notcp time.nist.gov" is handy as it is
guaranteed to be truncated with dnsmasq and DNSSEC enabled if the domain
isn't already in your local cache through a preceding TCP query.
Best,
Domin
configuration.
Best,
Dominik
>Am 25. August 2024 12:21:27 MESZ schrieb Dimitry Andric
>:
>>On 25 Aug 2024, at 11:07, Danil Smirnov wrote:
>>>
>>> There is some evidence on the Internet that dnsmasq doesn't play well with
>>> Docker (when run
showing up.
Best,
Dominik
On 28.07.24 10:19, renmingshuai via Dnsmasq-discuss wrote:
Hi,
I have a problem with a Segmentation fault. The log is as follows:
024-07-24T17:06:00.540592+08:00 info kernel[-][25317.980044]
dnsmasq[597243]: segfault at 9 ip 15257897bObe sp 7fffba533380
error 4
send_from (forward.c:38)
Note that the line-numbers are not necessarily 100% accurate. We have
not noticed any abnormal behavior, however, fixing this reported error
is easy enough.
Best,
Dominik
From fd37817ec8ae02c8c4d449df339d179f767caba4 Mon Sep 17 00:00:00 2001
From: Dominik Derigs
Dat
Dear Simon,
this week three additional RRTypes NXNAME (128), CLA (263), and IPN
(264) have been added, patch meant to come on top of my previous
attached to this mail.
Best,
Dominik
On 24.06.24 07:30, Dominik Derigs wrote:
Hey Simon,
yesterday, the IANA started listing a new query type
Hey Simon,
yesterday, the IANA started listing a new query type WALLET that was
assigned RRType 262.
Best,
Dominik
From 4b7b659503cacdccbcdffc48bfecea54a7da1f64 Mon Sep 17 00:00:00 2001
From: Dominik Derigs
Date: Fri, 21 Jun 2024 20:59:04 +0200
Subject: [PATCH] Add newly assigned RRTYPE WALLET
early (within the loop). The crash
does not happen for prefix lengths {8,16,24,32} as the loop runs only
once. However, for other prefixes, the loop runs more often (e.g. 128x
for /25 networks as above).
Best,
Dominik
From bf4c149f814ce2826f7db487a44d3eef7209ba14 Mon Sep 17 00:00:00 2001
From
Dear list,
we have added this commit to the currently running Pi-hole v6.0 beta. It
was confirmed by multiple users to fix aforementioned issues.
https://github.com/pi-hole/FTL/pull/1965
Have a great weekend!
Dominik
On 29.04.24 20:44, Erik Karlsson wrote:
From: Erik Karlsson
Not doing
misinterpreted when SIGALRM is used so I thought your patch wouldn't be
effective in our case. Sorry for this and thanks for challenging my
earlier statement.
Best,
Dominik
On 06.05.24 11:39, Erik Karlsson wrote:
Hi Dominik,
Are you sure the patch I sent does not solve this? I think it s
1 May 5 19:00:00 dnsmasq[4395]: DHCP 192.168.2.141 is
May 5 19:00:00 dnsmasq[4395]: forwarded
141.2.168.192.in-addr.arpa to 1.0.0.1|
The final immediate "forwarded" line comes from dnsmasq itself and
confirms that this was triggered by use-stale-cache.
Best,
Dominik
P.S.: The
but continued
hammering the server. This was especially true for embedded devices
where any kind of DNS "error" may simply trigger endless repetitions.
The best compromise we could come up with was in fact defining a "valid"
response (A 0.0.0.0, ::) for blocking.
Best,
this more complex path.
The proposed option --no-ANY simply ensures dnsmasq will not add any RRs
for such questions.
We are looking forward to enable it by default in Pi-hole v6.0+ given
this patch is accepted.
Best,
Dominik
From ac3134c48ef3ee6ec9be2f3b0993f710ac36f8f8 Mon Sep 17 00:00:00
get
a wide testing audience (it is enabled to cache ANY in Pi-hole) but more
testing is always welcome!
Best,
Dominik
On Thu, 2023-12-07 at 14:05 -0600, Evandro Menezes via Dnsmasq-discuss
wrote:
> Current OSes are now using the HTTPS record to query the addresses and the
> canonical na
Hey Evandro,
see my reply to your other question as the questions are just two
aspects of the same thing:
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2023q4/017363.html
Best,
Dominik
P.S. Your address evandro+dnsm...@gcc.gnu.org throws an "user unknown"
error.
On Th
Hey Simon,
today the IANA started listing a new query type RESINFO that was
assigned to RR Type no. 261. The simple attached patch adds this RR Type
to dnsmasq.
Best,
Dominik
From a6331078d3b22c960df8ad78106da567cb76e82c Mon Sep 17 00:00:00 2001
From: DL6ER
Date: Thu, 2 Nov 2023 17:57:54 +0100
sq/forward.c:1319
#9 0x560c710d5dff in check_dns_listeners (now=now@entry=1693587879)
at /app/FTL/src/dnsmasq/dnsmasq.c:1836
#10 0x560c710d7d2d in main_dnsmasq (argc=,
argv=) at /app/FTL/src/dnsmasq/dnsmasq.c:1271
#11 0x560c71036f76 in main (argc=,
argv=0x7ffe4bdab088) at /ap
memory corruption happens.
As said, I wasn't able to do such debugging myself as the issue stopped
happening and was happening rarely even before.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.the
and wants some extra protection against such
letter confusion "attacks".
Best
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
n SERVFAIL happens, EDE codes are
used to differentiate "normal" from DNSSEC-related reasons.
As I have mentioned before and we have discussed here, relying on the AD
bit for the IN-/SECURE determination is the best we have with proxy-
dnssec but it is by far not very good.
--dnsse
Hey Peter,
On Thu, 2023-04-13 at 12:15 +0200, Peter Russel wrote:
>
> Dominik, your questions and comments.
>
> Thanks for explaining "add-cpe-id=01234", meaning that it informs
> upstream that it is capable of processing EDNS data, nothing more.
> This implies dn
a direct line with the pi-hole developer, if
> you do, you could discuss this directly, I'm just the middle man here,
> knowledgeable enough to test, not to change the code...
We listen and respond here, too, when we have something valuable to
contribute :-)
Dest,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
everything you can". May this be "--cache-
rr" without options, some special "--cache-rr=all" or maybe
a dedicated option like "--cache-all".
Others than that - thanks for working on this! I already
started testing
/1db9943c6879c160a5fbef885d5ceadd3668b74d
The proposed fix:
https://github.com/pi-hole/dnsmasq/pull/13
Best,
Dominik
From 6f39ec984e00aad03c045f2b7f9e814f671099bf Mon Sep 17 00:00:00 2001
From: DL6ER
Date: Fri, 3 Mar 2023 18:05:26 +0100
Subject: [PATCH] Fix --rev-server option. It was broken in
Hey Simon,
totally an oversight on my side. Updated patch attached.
Best
Dominik
On Mon, 2023-01-16 at 22:46 +, Simon Kelley wrote:
> The patch moves the relevant code to after processing of command-line
> arguments, but not reading configuration file(s). I can't think of any
&
(strings)".
I thought about adding the possibility to only disable a
subset of these CHAOS records but it seems to just add to
much code complexity for such a small feature. Hence a "all
or nothing" seems the best fit for me here.
Best,
Dominik
On Tue, 2023-01-03 at 10:48 +, P
source.
This patch adds a new run-time option --no-ident to achieve
the same without the need for recompiling.
I wish you some nice and hopefully relaxing Christmas days!
Best regards,
Dominik
From bb796f57bdf6a3ad9517e930096dd38cfebf937a Mon Sep 17 00:00:00 2001
From: DL6ER
Date: Fri, 23 Dec 2022 12
ased) behavior from
serving expired content forever to a default value of one day.
This is freely configurable (I will set it down to one hour on
our systems) and can even be made serving forever, just as before
by explicitly setting the optional value to 0.
Best,
Dominik
Internal tracking is happeni
econd example
(no IPv6 address for a hostname but IPv6 source address given)
but this may be a real edge-case where we can expect users to
understand what they're doing and read the logs. Catching this
would require extra logic (valid hostnames are returned but none
is used -> error out).
Hey all,
and here comes the third resubmission of my patches. I do still
believe that they are improvements. Even one year after writing
them, them do still apply cleanly on the master branch.
Best,
Dominik
Forwarded Message
From: Dominik Derigs
To: dnsmasq-discuss
torial are available to see whether the issue is dnsmasq not responding
or the queries not making their way to dnsmasq or if something happens to
the queries sent upstream to the forward destionation, or whatever else may
be happening. We can surely give some assistance here,
ot;dnssec-retry[DNSKEY]" : "dnssec-
> > retry[DS]", 0);
>
> I see more changes as commit message says.
What do you see in addition?
It is a minimal invasive change that fixes the omission in a
previous commit as already said in the first mail:
On Sun, 2022-04-10 at 10:
try[DS] microsoft.net
to 127.0.0.1
This is added by this patch implementing it in the same way as
used already when logging "dnssec-query" in the code.
Best,
Dominik
From 00b8789e4119a25da7f286ca1cefd5fe66383b30 Mon Sep 17 00:00:00 2001
From: Dominik Derigs
Date: Sat, 2 Apr 2022 21:45:47 +0200
acks.
From 93f597e943283124af2e39620e748635cc6a04d6 Mon Sep 17 00:00:00 2001
From: Dominik Derigs
Date: Thu, 3 Feb 2022 16:12:16 +0100
Subject: [PATCH] Extend server to accept hostnames for upstream resolver
Signed-off-by: DL6ER
---
man/dnsmasq.8 | 4 +++
src/config.h | 3 +++
src/opti
Dear Simon,
Second resubmission of my patches.
They still apply cleanly to current master.
Best,
Dominik
Forwarded Message
From: Dominik Derigs
To: dnsmasq-discuss@lists.thekelleys.org.uk
, Simon Kelley
Subject: [PATCH] Addressing hostsdir shortcomings
Date: Sat, 08 Jan 2022
two values. Hence, I still find it meaningful to
reduce the number.
Otherwise, I perfectly agree with you on that 1232 is some
guesswork and that there will be no ultimate answer.
Best,
Dominik
On Tue, 2022-01-11 at 11:52 +0100, Petr Menšík wrote:
> I doubt that small difference matters. 1280 or 1
`
(currently `4096`) to ensure fragmentation will never happen, but
I don't think we really want to do this given the steady growth
in DNSSEC-enabled zones (see trend graphs on
https://stats.dnssec-tools.org).
Best,
Dominik
From 1113ef0c3102adb9106a21a8c1c97137fa21cd32 Mon Sep 17 00:00:00 2001
alias interface (see other PR for details).
Instead, it only adds logging for which interface is actually
used when a different was configured.
I personally prefer the other fix as this one would be a mere
bandaid and not fixing the actual issue.
Best,
Dominik
From 33605d70b01f0ae2c60112d12c4376203
issues.
This already has proven helpful when resolving a VLAN induced
issue (2 hops away) here:
https://discourse.pi-hole.net/t/dnsmasq-warn-ignoring-query-from-non-local-network/52346/14?u=dl6er
Best,
Dominik
From 9f4df221c014bb7ee8492a5bd8996dc7529cb1e6 Mon Sep 17 00:00:00 2001
From: Dominik
and stop working once an
alias interface is specified (even if valid).
Best,
Dominik
[resubmission of rebased patches, original submission in
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q4/015938.html]
From cc07a92ba26c3d9b3142a97e1c750fdb1a09e6e5 Mon Sep 17 00:00:00 2001
From: D
Yes, strict-order applies to all server configuration, regardless
where it was defined.
> > 2)
> >
> > can i have multiple ignore-address= ?
> >
> >
Yes.
> >
> > --
> >
> > Regards
> > Justin He
Best,
Dominik
&g
n be called before running
read_hostsfile() to insert new stuff. I added MOVE_FROM and
DELETE to inotify_add_watch() so we catch if a file was removed.
In this case, we only remove old entries.
Issue 3 is fixed by adding a loop over cache_find_by_name() in
add_hosts_entry() to check possible mult
20326 8 2
SF IC config
Best,
Dominik
From be26a63372b18bd0dd567c4a40ed285e292fe7d5 Mon Sep 17 00:00:00 2001
From: Dominik Derigs
Date: Sat, 18 Dec 2021 10:08:01 +0100
Subject: [PATCH 1/2] Fix header of cache dump. The width of the host and
a
)
Best,
Dominik
From eba5c590bc98b3cd5ca54ff59f654cb9da1aee8c Mon Sep 17 00:00:00 2001
From: Dominik Derigs
Date: Fri, 19 Nov 2021 10:08:01 +0100
Subject: [PATCH] Log server port when forwarding upstream
Signed-off-by: DL6ER
---
src/cache.c | 8 ++--
src/dnsmasq.h | 1 +
src/forward.c | 10
client information
somewhere upstream when ECS is used in lower DNS layers in our
local network. Some upstream servers, for instance, Google DNS,
even refuse to answer when ECS contains a 192.168.0.0/16 address.
Best,
Dominik
From cb72bf20ce317a8d4c727d7818b2e20b33832eae Mon Sep 17 00:00:00 2001
://discourse.pi-hole.net/t/dnsmasq-warn-reducing-dns-packet-size/51803/31
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
and then ANY + underscores
following thereafter. I see the man page wording could be
improved.
Happy New Year!
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
ybe a correlation with a domain that is early
requested and has a TTL of 12 hours (entirely hypothetical at
this point).
> Currently I'm using this version:
>
> commit 1176cd58c90fc37bf98a6f774b26fc1adc8fd8e9
> Fix regression in --rebind-domain-ok in 2.86
Does it
setup.icloud.com is a CNAME pointing to setup.fe.apple-
> dns.net
As Geert already mentioned, dnsmasq is neither meant nor designed
to post-process replies from upstream DNS server.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@list
ou could take a look (I don't want to break any other features).
The patch isn't highly optimized but prepared for readability.
Best,
Dominik
From 763f46948844eab25859e7ab72816733be3e533c Mon Sep 17 00:00:00 2001
From: Dominik Derigs
Date: Fri, 19 Nov 2021 10:59:25 +0100
Subject: [PATCH] D
s needed and adjust it accordingly. We'll import all tests
we consider useful for our project and assume it won't be all of
them. As dnsmasq will be tested independently, it won't be super-
important to run all the same tests in our repository again.
Best,
Dominik
___
lated files (e.g.
if you are using dhcp-hostsfile or dhcp-hostsdir)?
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
o the previous (entirely unrelated)
query. Setting the ID is incorrect at this point.
The third log is somewhat different, it may be a separate issue.
I cannot reproduce the issue in the first two logs but I can pass
on a patch.
Best,
Dominik
Oct 14 04:08:53 dnsmasq[29757]: 8722 fddc:704f:99b9:178:
Hey Petr,
On Tue, 2021-10-12 at 04:40 +0200, Petr Menšík wrote:
> Hi Dominik,
>
> those tests look great. Something like that is exactly what I had
> on
> mind for dnsmasq itself. Would you mind if I borrow few things
> and try
> to make some dnsmasq-only parts, not dep
I do agree it should be like --filter-a=/example.com/
Maybe this option could simply be syntactic sugar for
server=/example/#
address=/example.com/::
but with a real filter instead of forcing it to ::
Best,
Dominik
___
Dnsmasq-discuss mailing l
Hey Tobias,
On Thu, 2021-10-07 at 12:29 +0200, Tobias via Dnsmasq-discuss
wrote:
> it would be useful (at least for me)
In general, it is a bad idea to do this but I assume you know
this. So what is your use case for manipulating the TTL of only
particular domains?
Best,
Domi
tps://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q3/015711.html
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
which is sourced through dnsmasq.h
dnsmasq cannot be compiled within these projects.
The attached patch fixes this.
Best,
Dominik
From 776cdcdad6c8164593804d2b0a3f063923385e7e Mon Sep 17 00:00:00 2001
From: Dominik Derigs
Date: Thu, 7 Oct 2021 09:30:31 +0200
Subject: [PATCH] dnsmasq.h has to be inc
g the line to server=/fritz.box/192.168.0.1 restores the
> previous handling. However, according to the dnsmasq manpage "-
> -local is a synonym for --server to make configuration files
> clearer in this case."
Best,
Dominik
From 57461836c48deda17c468ae3c2033d0cc3dc34ec Mon Sep 17 00:00:0
in another project. There is no unittest library
whatsoever involved. The tests simply run on a compiled binary.
You can find everything here if you're curious:
https://github.com/pi-hole/FTL/tree/master/test
Best,
Dominik
___
Dnsmasq-dis
to not need two independent
files but serve DHCP and DNS from a single source of knowledge.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
r obsolete sounds like a good idea.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
er, is to keep the difference between our fork and
dnsmasq minimal. Even with all the stuff we do on top, the diff between our
fork and the main project is less than 100 lines and the vast majority of
patches to this mailing list applies cleanly right away.
Best
terfaces due to
the missing label. Not that this should be the reason for making this
change. This reasoning is given above (correct warnings in dnsmasq).
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
e they think you want to cheat on their geo-
fencing with your VPN. When they use Netflix over their native IPv4,
everything works.
I was a bit surpised about this, but it does make sense.
Best
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-d
d. This can be called before running
read_hostsfile() to insert new stuff. I added MOVE_FROM and
DELETE to inotify_add_watch() so we catch if a file was removed.
In this case, we only remove old entries.
Issue 3 is fixed by adding a loop over cache_find_by_name() in
add_hosts_entry() to check possible
h should preserve backwards compatibility it I'm not
mistaken. And since we're using the label variable everywhere
else...
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
and
more already existing entries. Hostname checking is a non-linear
task, too (because it depends on the length of the individual
names), so I'd say CNAME insertion goes roughly like O(N^2.5).
This seems to fit your experiment pretty well.
Best,
On Thu, 2021-09-23 at 11:00 +0100, Simon Kelley wrote:
> I just pushed a pretty straightforward patch to fix this.
Can confirm this fixes it.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
ht
nsmasq: bad dynamic directory hosts: not a directory
instead in this case.
Best,
Dominik
From 066a79e48b129e845744ad0e8d88be5181875ba0 Mon Sep 17 00:00:00 2001
From: Dominik Derigs
Date: Wed, 22 Sep 2021 15:32:59 +0200
Subject: [PATCH] Correcly warn if dynamic directory is actually no directory
Si
200, Jean-Philippe Lambert wrote:
> Is this a bug
I guess so and it is likely linked to
On Wed, 2021-09-22 at 12:29 +0200, Jean-Philippe Lambert wrote:
> dnsmasq: warning: no upstream servers configured
Best,
Dominik
___
Dnsmasq-disc
upstream but never receives a reply, hence, considers all
of them as dead.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
e same string multiple times if
more than one virtual interface is present.
Patch 2 fixes a crash I've seen on a small embedded device that
crashed when there wasn't enough memory available for allocating
a TCP packet (66 kilobytes).
Best regards,
Dominik
From e2112e432917caf510b256d51089252
rately from everything else.
Do you have a change to try the current version v2.86? We
recently improved logging and the issue you're mentioning should
already be fixed.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekell
the code is consistently indented when using the
standard tabwidth.
On Thu, 2021-09-16 at 20:19 +, Carson Riker wrote:
> would a PR standardizing things be welcome?
See
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2019q4/013414.html
Best regards,
D
0.1
> server=/bo.net/#
> address=/bo.net/::
resulting in "A bo.net" being sent to 192.168.0.1
Something is definitely fishy here.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.theke
ll when "address=..." is in
use, see my most recent two mails to the list for some details.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
lace, e.g., "->sfd" to "-
>extra->serv->sfd", the amount of work sound not too dramatic.
However, as this is a design decision and as you may want to do
it differently altogether, I'm not attaching a patch here.
Best,
Dominik
log-queries=extra
port=5000
no-r
data eventually leading to a crash.
The attached patch tries to fix this by first checking if we are
really dealing with a full "struct server" here. I cannot get
dnsmasq to crash with it.
---
How to reproduce the crash yourself:
1. Use the attached config line.
2. Query "di
re servers to be
shown that we log (this is limited by SERVERS_LOGGED = 30)
Best,
Dominik
From 58343618ffee18c24a9c81b7a668cb5dcc7e847d Mon Sep 17 00:00:00 2001
From: Dominik DL6ER
Date: Mon, 6 Sep 2021 22:27:00 +0200
Subject: [PATCH] --rev-server: Add support for arbitrary IPv4/6
prefix-lengt
also with removed explanation (I don't think we have
had the server explanation last year when I wrote this patch).
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
DHCP). It applies
cleanly to the current master.
I guess it's pretty self-explanatory, more details can be found
in my last submission:
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2020q2/013985.html
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2020q2/01399
upport for /10
might come in the next release (if the patches are accepted).
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
ovsx rcx, eax
sal rdx, 4
cmp DWORD PTR typestr[rdx], r1d
jne .FOR_LOOP
[... stuff if found ...]
Given we call library functions like strlen() and sprintf(), our loop
here is surely not any kind of bottleneck. Even if it'd be even larger.
Best,
Do
ing.
I'm involved in the process now and get notified if the IANA RR types
table gets updated and will send new patches if this is the case.
Best,
Dominik
From 97ca3ae9ff6a33ac70fb982d282a1728dee5a9cd Mon Sep 17 00:00:00 2001
From: Dominik DL6ER
Date: Thu, 9 Sep 2021 14:28:28 +0200
Subjec
On Sat, 2021-09-04 at 22:04 +0100, Simon Kelley wrote:
> Dominik, you were the one pushing for 2.86. Thoughts?
Hey Simon,
I didn't really intend to push for v2.86, but, yes, I'd personally like
to see it soon(ish). Also given that v2.85 was almost half a year ago.
Maybe we coul
1fe126e0670c;hb=HEAD#l27
and the line below. The default probing could likely be made less
often, but else than that, I don't think there is an inconsistency
here.
Best,
Dominik
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.or
.2.0/2:00:00,M11.1.0/2:00:00"
and
> dhcp-option = option:tzdb-timezone,"Europe/Berlin"
Best,
Dominik
From fba30c5aa94d0fd6b98b690fbf72913e8683de7f Mon Sep 17 00:00:00 2001
From: DL6ER
Date: Fri, 3 Sep 2021 13:51:18 +0200
Subject: [PATCH] Add RFC 4833 DHCP options "posix-ti
ke
to see a hint that you should really only set this option in IPv6-only
environments (when you are absolutely sure about the guaranteed absence
of upstream IPv4) and what the implications are (A queries will never
be answered). And maybe even a single line paragraph to the CHANGELOG.
Best,
Do
LL, aqtype) ->
querystr("", aqtype) in the "else" branch of "if (aqtype == T_TXT)" but
that's entirely your call.
Also, DNSSEC signed TXT records were not logged as such with log-
queries=extra. print_txt() needs secflag for this. Patch attached.
I'
1 - 100 of 178 matches
Mail list logo
