At home, I have a Linux router with #dnsmasq where DHCP leases are in /etc/ethers and /etc/hosts.
My new #FLX1 is based on Android, and keeps changing the MAC address it advertises to DHCP servers. But I don't want this at home: there are no privacy issues there.
Fix:
nmcli con modify $NETWORK_NAME wifi.cloned-mac-address 00:11:22:33:44:55
A fun little project making my #NextCloud server a bit more performant from the local LAN. Using #Linux based #Docker, #dnsmasq and #nginx reverse proxying to set up a second reverse proxy onto a NextCloud AIO instance already proxied via Clourflare Tunnel.
Thanks @BigG for convincing me to go NextCloud.
@DJGummikuh Hi, #reForis is actually made to be compatible with #LuCI as much as possible. Only thing where we differ is #DNS settings. We are using #KnotResolver (for #DNSSEC and more). You can enable #dnsmasq and ignore DNS settings in reForis. For the rest of the system, we are just handling #updates 
But we push all necessary patches to #vanilla kernel, so you can install not only #OpenWrt (there is #community contributed howto on their wiki), but also many other #Linux distributions
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).
ICYMI: Ali Imran Nagori looks at the automatic installation method rolled out with Ubuntu 22.04, which borrows some tools from the cloud configuration toolbox
https://www.linux-magazine.com/Issues/2024/288/Ubuntu-autoinstall-with-cloud-init
#Ubuntu #cloud #YAML #TFTP #OpenSource #dnsmasq #DNS #DHCP #FOSS
It's a minor issue that we had with Dnsmasq, but we've run into this issue and documented it, so you don't have to
"Dnsmasq does not start because port 53 is busy"
https://blog.zero-iee.com/en/posts/dnsmasq-startup-error-with-systemd-resolved/
Wie finde ich die #UID von #dnsmasq unter #iodeOS heraus? Handy ist gerootet.
Ich will ausprobieren, ob folgendes bei mir auch beim Tethering hilft:
iptables -I afwall-wifi-tether 1 -p udp -m owner --uid-owner 1052 -m udp --sport 53 -j RETURN
iptables -I afwall-wifi-tether 1 -p tcp -m owner --uid-owner 1052 -m tcp --sport 53 -j RETURN
Edit: Die Befehle von omaer0 haben bei mir nichts bewirkt. Keine Ausgabe.
QEUM KVM unable to start default network #networkmanager #kvmvirtualization #qemu #dnsmasq #libvirt
This costed me *hours*. If you ever have this problem with #FreeBSD pkg:
------------------
pkg: No SRV record found for the repo 'FreeBSD'
pkg: packagesite URL error for pkg+http://pkg.FreeBSD.org/FreeBSD:13:amd64/quarterly/data.pkg -- pkg+:// implies SRV mirror type
-----------------
In other words, your computers fail to resolve "SRV" DNS records ... AND you are using #dnsmasq or #openwrt, then:
Check whether you have the option "filterwin2k" on. Switch it off. In the #openwrt router it is disguised as "Filter useless".
@Shamar I'm used to #dnsmasq, but there are probably others. I use it to serve my local network's #DHCP+#DNS coordinated services, meaning if a new client tells the DHCP server its hostname, DNS will abide to it and the rest of the machines will be able to reach it by name.
As for the system wide config, it depends a lot on which tool you're using to configure your network interfaces. It's most probably #NetwortManager, so check it's doc about setting a fixed DNS server.
@rfc2549 @geerlingguy We also had a namesaked repo at work, it combined #Ansible and #Terraform (and #LXD; now #incus) to deploy test clusters for our main product. It hit a wall when distributed LXD didn't allow us to mess with the DNS server (#dnsmasq on single host deployments) anymore :(((
@alexandreborges Interesting article, but does not mention in title MS AD is the problematic implementation. If it restricts updates to unused or dynamic-only names, it should be safe. Not a problem with #Dnsmasq.
@FLOSS_Weekly @webmink @JP_Bennett
Listening to it via Youtube: https://youtu.be/GeddWItBwcg now #dnsmasq @debian #debian #floss and running dnsmasq in my Linksys router running @OpenWrt :)
Several #DNSSEC related #vulnerabilities disclosed resulting in #resourceexhaustion and potential #denialofservice of DNS servers. If you're running DNS server(s) such as #Bind, #Unbound or #PowerDNS update as soon as possible. Apparently also #dnsmasq is affected. https://www.theregister.com/2024/02/13/dnssec_vulnerability_internet/ #infosec #cybersecurity
@mike #DNSmasq on #OpenWRT (#TurrisOmnia) and #Bind9 to define my own public NS.
