On Fri, Oct 25, 2024 at 09:36:20AM +0100, Joe wrote: > On Fri, 25 Oct 2024 08:03:43 +0100 > Chris Green <c...@isbd.net> wrote: > > > > Yes, OP here again, that's why I said in my original post "(I know > > they're not quite the same thing, but the result works OK)" > > I think (on Ubuntu it did anyway) that systemd-resolved.service > > provides a DNS caching service. The trouble is that it does it wrong > > (in many people's opinion), if the 'first' DNS server fails to give an > > answer it tries the 'second' (correct enough) but it then sticks to > > using the 'second'. If your local LAN DNS fails (even momentarily) > > then it never gets used again and you lose LAN DNS. This has been > > argued over endlessly with the systemd developers. > > > > I don't know if it's significant, but that's how Microsoft domain DNS > works, meaning that unless multiple DNS servers replicate. a short loss > of connection cuts the clients off from Active Directory, rather more > serious.
That's one of the first things we teach the poor folks using Windows in our net: "ipconfig /flushdns". Followed by a hint that we, non-Windows folks don't need it :-) Cheers -- t
signature.asc
Description: PGP signature
