Timeline for Losing client side domain name resolution after rebooting the corresponding DHCP/DNS server based on 'dnsmasq'
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 8, 2022 at 20:16 | history | edited | G-Man Says 'Reinstate Monica' | CC BY-SA 4.0 |
Fixed spelling; improved grammar/wording, punctuation and formatting.
|
| Sep 6, 2022 at 14:27 | vote | accept | Tamás Tóth - ebola | ||
| Sep 6, 2022 at 14:26 | answer | added | Tamás Tóth - ebola | timeline score: 0 | |
| Jul 17, 2022 at 16:51 | comment | added | Slartibartfast | Sounds like the name to IP address mapping is lost on reboot until the clients refresh. The info could be lost because it isn't saved, but the service restarts would argue against that. I'm a little curious if it is lost due to the clock / timeout for time-bounded leases, knowing that the Raspb. Pi doesn't have a built-in clock. | |
| Jul 17, 2022 at 16:21 | history | edited | Tamás Tóth - ebola | CC BY-SA 4.0 |
added 1790 characters in body
|
| Jul 17, 2022 at 15:57 | comment | added | Tamás Tóth - ebola |
Thanks @JourneymanGeek for your fast response. What I can tell you now is the following: - After restart just 'dnsmasq' (sudo systemctl restart dnsmasq.service), there is no problem. All devices reach the net and name resolution works fine. - After restart just 'networkd' (sudo systemctl status systemd-networkd), there is no problem. All devices reach the net and name resolution works fine. - After restart the whole machine, previous clients loose name resolution until their network reconnect. In some minutes I will expand my original post with the corresponding config entries.
|
|
| Jul 17, 2022 at 13:54 | comment | added | Journeyman Geek♦ | When I was running dnsmasq on ubuntu 20.04, I had a ton of problems with the 'default' netplan network management system. I switched back to the traditional /etc/networks and its worked great. I didn't dig deeper but I suspect its a misconfiguration of netplan and dnsmasq. Try restarting just dnsmasq and see what happens, and a proper solution would be to take a look at the systemd units for both and seeing whether the dependancies are correct | |
| Jul 17, 2022 at 13:32 | history | asked | Tamás Tóth - ebola | CC BY-SA 4.0 |