How can avahi daemon backward resolution be working while forward is not?

After a reboot of my server, I noticed the hostname wasn't resolving. I checked the firewall-cmd to see if mdns/5353/udp was open, which it was.

Then, I went to check if Avahi daemon was running, which it is.

[vestatian@etune ~]$ systemctl status avahi-daemon
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service;>
     Active: active (running) since Mon 2025-02-10 15:13:27 +08; 

Furthermore, sudo netstat -tuln showed that the server was in fact listening here

udp        0      0 0.0.0.0:5353            0.0.0.0:*

It was after I ran the below commands, I realized that the mdns was in fact resolving, but only backwards. What about avahi-daemon might be causing this behaviour?

vestatian@pegasus:~/sources/frappe_podlet$ avahi-resolve -n etune.local
Failed to resolve host name 'etune.local': Timeout reached
vestatian@pegasus:~/sources/frappe_podlet$ avahi-resolve -a 192.168.50.241
192.168.50.241  etune

Additional info:

Operating System: Red Hat Enterprise Linux 9.5 (Plow)     
     CPE OS Name: cpe:/o:redhat:enterprise_linux:9::baseos
          Kernel: Linux 5.14.0-503.21.1.el9_5.x86_64
    Architecture: x86-64