Badli,
On Mon, Apr 24, 2023 at 12:24:50AM +0000, Badli Al Rashid via BitFolk Users wrote:
> If I set the listen to specific, bind9 would fail to listen. Example.
You don't show HOW you did this. i.e. what exact changes you made to
bind's configuration.
> 13-Apr-2023 23:00:07.711 network: info: no longer listening
> on 2001:ba8:1f1:f0b5::2#53
> 13-Apr-2023 23:00:07.711 network: info: no longer listening
> on fe80::216:5eff:fe00:5f5%2#53
> 13-Apr-2023 23:03:41.664 network: info: no longer listening
> on 127.0.0.1#53
> 13-Apr-2023 23:03:41.664 network: info: no longer listening
> on 85.119.83.49#53
> 13-Apr-2023 23:03:41.664 network: info: no longer listening
> on 85.119.82.135#53
> 13-Apr-2023 23:03:41.664 network: info
You don't show what commands you typed to restart/reconfigure bind9
after changing its config.
You don't show the full logs, only some parts that you think are
interesting. Whether restart or reconfig, there would be much more
than the above. Also the ones above are from 10 days ago!
We can't tell why your bind9 stopped listening on all interfaces
when you show neither your config, the full logs nor the commands
you typed.
It is just too hard to help you with this drip feed of partial
information. I can't go another round of asking all the above
questions and getting no or partial answers, so I'm going to have to
give up now. Sorry.
Regards,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting