Description of problem:
I'm seeing dnsmasq service exit after a period of time (minimum 6 hours) on a RHEL 9.1 box. This is undesired, and manual intervention is required (systemctl restart dnsmasq) in order for service to be restored.

I'm not seeing anything of significance in logs or via journalctl. I added DumpCore=yes in /etc/systemd/system.conf in an attempt to get any useful logs, but none seem to be generated. In running strace on the master PID, I notice 1 EMFILE (Too many
> open files) and -1 EBADF (Bad file descriptor) at the end of the output right before the service goes down.

I see a climbing number of file descriptors also when I restart the service.

1. ls /proc/249121/fd | wc -l
   403

This value started at around 30. In my other lab with RHEL8 / dnsmasq, I see 23.

Version-Release number of selected component (if applicable):
dnsmasq-2.85-5.el9.x86_64

Steps to Reproduce:
1. Have dnsmasq service running, where service is acting as both a DHCP server and DNS resolver
2. Wait 6 hours
3. service shuts down on its own / dies, requires manual intervention

Additional info:
RHEL 9.1, 5.14.0-162.23.1.el9_1.x86_64 kernel.