I notice the old restartdns command has gone so tried sudo pihole disable and enable and got the responses below.
I don't know how to restart the service otherwise, so rebooted and now it's working again.
Sorry it's vague, but if you need more details, please let me know.
Kind regards,
Paul.
> $ sudo pihole disable
> curl: (3) URL using bad/illegal format or missing URL
> curl: (6) Could not resolve host: communicationsauth
> curl: (6) Could not resolve host: errorauth
> curl: (6) Could not resolve host: toauth
> curl: (6) Could not resolve host: timedauth
> curl: (3) URL using bad/illegal format or missing URL
> curl: (6) Could not resolve host: communicationsauth
> curl: (6) Could not resolve host: errorauth
> curl: (6) Could not resolve host: toauth
> curl: (6) Could not resolve host: timedauth
> curl: (3) URL using bad/illegal format or missing URL
> curl: (6) Could not resolve host: communicationsauth
> curl: (6) Could not resolve host: errorauth
> curl: (6) Could not resolve host: toauth
> curl: (6) Could not resolve host: timedauth
> curl: (3) URL using bad/illegal format or missing URL
> curl: (6) Could not resolve host: noauth
> curl: (6) Could not resolve host: serversauth
> curl: (6) Could not resolve host: couldauth
> curl: (6) Could not resolve host: beauth
> curl: (6) Could not resolve host: reachedauth
> curl: (6) Could not resolve host: reachedauth
> No response from FTL server. Please check connectivity
> $ sudo pihole enable
> curl: (3) URL using bad/illegal format or missing URL
> curl: (6) Could not resolve host: communicationsauth
> curl: (6) Could not resolve host: errorauth
> curl: (6) Could not resolve host: toauth
> curl: (6) Could not resolve host: timedauth
> curl: (3) URL using bad/illegal format or missing URL
> curl: (6) Could not resolve host: communicationsauth
> curl: (6) Could not resolve host: errorauth
> curl: (6) Could not resolve host: toauth
> curl: (6) Could not resolve host: timedauth
> curl: (3) URL using bad/illegal format or missing URL
> curl: (6) Could not resolve host: communicationsauth
> curl: (6) Could not resolve host: errorauth
> curl: (6) Could not resolve host: toauth
> curl: (6) Could not resolve host: timedauth
> curl: (3) URL using bad/illegal format or missing URL
> curl: (6) Could not resolve host: noauth
> curl: (6) Could not resolve host: serversauth
> curl: (6) Could not resolve host: couldauth
> curl: (6) Could not resolve host: beauth
> curl: (6) Could not resolve host: reachedauth
> curl: (6) Could not resolve host: reachedauth
> No response from FTL server. Please check connectivity
Sorry for the delay in responding. Sure, debugging can run as long as you like. I, for instance, have it on 24/7 on my own Pi-hole. Attaching the gdb debugger also doesn't affect performance in any noticeable way (except, maybe, if your machine is realllyy slow).