med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

373
active users

#dnsmasq

0 posts0 participants0 posts today

Wenn wer Ärger mit dem #NetworkManager im #AccessPoint Mode hat oder #DHCP, #DNS upstream, DNS port usw. individuell einstellen will...
...ich kann jetzt qualifiziert helfen...🙈

Kein Witz - ich habe sowohl im NetworkManager als auch #dnsmasq jede verfluchte Zeile im Code gelesen und verstanden die das Zusammenspiel beider Dienste im AP-Mode betrifft...

#piSpot...
(minimalistischer, mobiler #HotSpot #WLAN #WWAN #ETHERNET #VPN #Tor #AdBlock #ChildProtection #RaspberryPi #Raspberry #PiZero2)

Continued thread

2/2
offizielle Version übernehmen will...🤷‍♂️
Die beiden Wege die ich gefunden habe um den #dnsmasq Aufruf durch #NetworkManager zu übernehmen sind auch Mist, weil sie beide keine Distro-Updates überleben wenn dnsmasq ein Update erfährt...

Jetzt habe ich aber doch noch ne Idee die "vollautomatisch" (reboot überleben) laufen sollte... dann wäre ich aber von #systemd abhängig...🤪
Und das ist mir jetzt egal...🤷‍♂️

Mein #piSpot / #pitSpot...

(minimalistischer mobiler #HotSpot / #AccessPoint #WLAN #WWAN #ETHERNET #VPN #Tor #AdBlock #ChildProtection - #RaspberryPi #Raspberry #PiZero2)

Nachdem ich letztens 12h durch die Sourcen des #NetworkManager getaucht bin... habe ich das heute mit #dnsmasq wiederholt...🙈

Das was ich will geht einfach nicht ohne neu kompilieren des NetworkManager.
2 Zeilen müssten bloß raus - ZWEI...😭

Leider verstehe ich die Argumentation, warum der Maintainer das nicht in die
1/2

What's the easiest way to set up (e.g. using a nice script or other program) a local #DNS on a range of platforms, and configure it to handle wildcard subdomains on #localhost?

😆

A quick search shows #dnsmasq can be used on Linux and Windows at least, but I wonder if anyone has faced this problem before and made a neat cross-platform solution?

I want <anything>.localhost to resolve to localhost and be handled by a server which runs on the local device (ideally Win, Mac, Linux and Android).

edit:
Okay, apparently this is not possible

#dnsmasq #dns

Since I don't know how to turn this into a search engine query:
If I cofig dnsmasq to forward a specific TLD to a specific (authoritative) server, and this server returns a CNAME entry to another TLD for a query, it seems dnsmasq (or maybe, rather, the authoritative server?) will not automatically return the address of the CNAME - which results in browsers saying "no such domain"?

I.e.:
server=/fur/178.63.26.172
resolv-file=/tmp/resolv.conf.d/resolv.conf.auto

$ dig www.nic.fur +short
inet.v8.fellig.org.

vs

$ dig www.nic.fur +short @80.152.203.134
inet.v8.fellig.org.
49.12.203.237

Can I make dnsmasq automatically "follow-up" on the CNAME response itself?

Anyone know if it's possible to generate #DNS64 entries locally on #OpenWRT? The service I use (at 2606:4700:4700::64) seems to be misbehaving, but DNS is reported to be fully functional on the Cloudflare status page. It seems like #dnsmasq ought to have all the information it needs to generate an AAAA record corresponding to the A record, so I could just use standard #DNS upstream, but I can't figure out how to do it.

Is it possible to configure #dnsmasq to use localise-queries but also specify a default for the networks for which a name isn't on that network?

Use case:

I have three networks, 10.42.x.0, where x is 0, 1, and 2. Jellyfin is on 10.42.0.96 and 10.42.2.96. Jellyfin should resolve to 10.42.0.96 for hosts on 0 and 1, but 10.42.2.96 for hosts on 2.

Ideally:

Every network resolves 10.42.0.96. Only hosts on 2 resolve to 10.42.2.96.

Replied in thread

So I realized that I need to focus on the logs, more than behavioral observation...

I restarted
#dnsmasq having a terminal showing a tail of var/log/deamon.log and another one showing a tail of /var/log/syslog` and I catched this message:

Oct 23 06:10:16 dagobah dnsmasq[23309]: reading /run/dnsmasq/resolv.conf
Oct 23 06:10:16 dagobah dnsmasq[23309]: using nameserver 192.168.0.1#53

This means that it is not reading the upstreams file I defined with
resolv-file=/etc/resolv.dnsmasq.conf. I really don't know the reason, but I commented the line and defined the nameservers in the #dnsmasq config itself:
server=149.112.112.112
server=9.9.9.9
server=1.0.0.1
server=1.1.1.1
⚠️ Note that the order is inverse, I want 1.1.1.1 to be read first!
... and also I uncommented the line
no-resolv so that external resolv files won't be used. And restarted. And tested with a dig:
Oct 23 06:21:54 dagobah dnsmasq[23939]: query[A] ladragonera.com from 192.168.0.40
Oct 23 06:21:54 dagobah dnsmasq[23939]: forwarded ladragonera.com to 1.1.1.1
Oct 23 06:21:55 dagobah dnsmasq[23939]: reply ladragonera.com is 89.245.8.125

Yay!
🥳

And then flushed the DNS cache of my mac:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
.. and Firefox's one:
about:networking#dns

... and finally I have my computer resolving correctly
🎉

The next thing is to study why the resolv file was not loaded properly even it was defined and existing (maybe a link does not work?) and WTF happens with my ISP, my router and its DNSs!!
Continued thread

I found you!
Here is the exact sequence I mentioned,
#dnsmasq is forwarding the query to the router!

Oct 23 06:00:23 dagobah dnsmasq[9542]: query[A] ladragonera.com from 192.168.0.40
Oct 23 06:00:23 dagobah dnsmasq[9542]: forwarded ladragonera.com to 192.168.0.1
Oct 23 06:00:23 dagobah dnsmasq[9542]: reply ladragonera.com is 89.247.149.245

And then I use
#dig and it reuses what it cached:
Oct 23 06:05:28 dagobah dnsmasq[9542]: query[A] ladragonera.com from 192.168.0.40
Oct 23 06:05:28 dagobah dnsmasq[9542]: cached ladragonera.com is 89.247.149.245

#help #dnsmasq #dns #self-hosting #linux #debian #raspberrypi

A part of the slow propagation that the domain has to front when using Directnic's Dynamic DNS on a TLD, I am also facing an issue in my internal network where the dnsmasq has cached the old IP address and I have no way to get the new one.

-I've restarted the service (which should involve a cache flush)
-I've set up also the
resolvectl service (that wasn't there and also does not fix it)

With the dance of IP renewals of this morning, I catched a scenario where my service provider DNS was requested, but I don't have it in my list of
/etc/resolve.conf ... meaning that I suspect that the list of upstream DNS servers I defined is not used and just forwarded to the router to resolve (why? How?)

With
dig requesting the domain through my local DNS server (dig domain @127.0.0.1) it gives me the old IP, and requesting through the upstream servers (dig domain @1.1.1.1) the IP returned is the new, so the upstream servers are up-to-date.

The related line in dnsmasq's config is set and the file exist:
resolv-file=/etc/resolv.dnsmasq.conf, unless it should not be a link (it's a link to a file somewhere else, where I keep config files)

#help #dnsmasq #dns #self-hosting #linux #debian #raspberrypi

Ayer empezaron a utilizar mi servidor DNS como pantalla, o intermediario, para hacer un ataque DDoS. Tuve que cambiar la IP rápidamente. A parte de limitar las IPs que pueden acceder, ¿qué me recomendáis para proteger su uso o limitarlo? Ojo que busco que siga siendo público.
Voy a empezar limitando las IPs de mi zona y el número máximo de peticiones por IP.
#dns #dnsmasq