On Tue, 2024-03-19 at 21:14 +0100, Buck Horn via Dnsmasq-discuss wrote:
> On 19.03.24 20:38, Grundik wrote:
> > But, if the record in --address is only specified as IPv4, then
> >
> > requests are still forwarded further, and I found no way to make
> > dnsmasq to return NXDOMAIN instead (as
On 19.03.24 20:38, Grundik wrote:
But, if the record in --address is only specified as IPv4, then
requests are still forwarded further, and I found no way to make
dnsmasq to return NXDOMAIN instead (as it should do in first place,
according to my understanding of documentation).
Quoting
Hello!
Documentation says:
-A, --address=/[/...]/[]
Specify an IP address to return for any host in the given domains. A
(or ) queries in the domains are never forwarded and always replied
to with the specified IP address which may be IPv4 or IPv6.
But, if the record in --address is only
Thanks again. I will rephrase my question one last time:
Considering that I have the rule `address=/*.firebaseio.com/`, how can I allow
only the domain `firebaseio.com` without having to use the instruction
`server=/firebaseio.com/8.8.8.8`? (How can I block all the subdomains except
the main
On 16/03/2024 10:09, shamrock_sesame214--- via Dnsmasq-discuss wrote:
Hello,
I am attempting to run dnsmasq DNS resolver in gVisor. gVisor is a hardened
userspace kernel compatible with Kubernetes and Docker containers. At the
moment, gVisor does not seem to support some routing features such
Seems the problem is solved by allowing a DNS over TCP for clients.
While inability to forward larger EDNS querries ove UDS in 2.90 is
certainly a change, I understand that dnsmasq is now following the DNS
flag day suggestion instead RFC.
I'd like to still point out, that the
