[Bug] Excessive DNS requests

[rsb-developer]

Describe the bug

Excessive DNS requests from PegaProx causing excessive overhead on the DNS server and prematurely filling logs. This is in line with issue #124 that was previously opened and then closed, but I think is still a bug. PegaProx is currently monitoring a single cluster with a single host. The excessive DNS queries would be greatly amplified with additional clusters and hosts. I do not consider this "normal" behavior as the amount of DNS queries makes PegaProx unusable in my environment.

Steps to Reproduce

1. From the Docker host, sudo tcpdump -ni any host <dns server ip> and port 53 which shows the volume of DNS activity taking place.
2. Checking the DNS dashboard, daily DNS activity increased from less than 600K to over 1.6M per day when PegaProx was deployed. See attached screen capture.

Expected behavior

I would consider a reasonable quantity of DNS queries to be the expected behavior and I do realize that PegaProx needs to poll each host to obtain needed info. Maybe this is a way to cache the host IP so DNS lookups are not being done at such an overwhelming rate?

Environment

• PegaProx Version: Latest
• Installation Method: Docker
• OS: Debian 12
• Browser: Safari
• Behind Reverse Proxy? No
• UI? Modern layout

Screenshots

Screen capture showing the huge increase in DNS queries

Thanks for considering, as I like where PegaProx is going.

[MrMasterbay]

Hi indeed @rsb-developer ,

I added here just a function that gets at the beginning the IP when the SSL Cert is unverified and checks it now daily when its verified.

Regards

[rsb-developer]

Thanks for implementing a fix, but I'm not sure it is actually working. I updated the container to v0.9.6 and monitored DNS queries and I still see the overwhelming DNS queries. Was there something else I needed to do for the fix on my end? Below is a snip from the DNS logs.

10:24:30.743851 ens18 Out IP 172.31.101.63.37223 > 172.31.101.3.53: 49481+ A? pve1.example.com. (31) 10:24:30.743869 ens18 Out IP 172.31.101.63.40911 > 172.31.101.3.53: 26442+ AAAA? pve1.example.com. (31) 10:24:30.762827 ens18 Out IP 172.31.101.63.50168 > 172.31.101.3.53: 63712+ AAAA? pve1.example.com. (31) 10:24:30.762852 ens18 Out IP 172.31.101.63.36647 > 172.31.101.3.53: 51438+ A? pve1.example.com. (31) 10:24:30.781474 ens18 Out IP 172.31.101.63.38300 > 172.31.101.3.53: 65016+ A? pve1.example.com. (31) 10:24:30.781485 ens18 Out IP 172.31.101.63.42478 > 172.31.101.3.53: 6137+ AAAA? pve1.example.com. (31) 10:24:30.797005 ens18 Out IP 172.31.101.63.60702 > 172.31.101.3.53: 4397+ AAAA? pve1.example.com. (31) 10:24:30.797014 ens18 Out IP 172.31.101.63.46758 > 172.31.101.3.53: 9267+ A? pve1.example.com. (31) 10:24:30.819469 ens18 Out IP 172.31.101.63.35906 > 172.31.101.3.53: 32476+ A? pve1.example.com. (31) 10:24:30.819475 ens18 Out IP 172.31.101.63.40890 > 172.31.101.3.53: 59602+ AAAA? pve1.example.com. (31) 10:24:30.836541 ens18 Out IP 172.31.101.63.39279 > 172.31.101.3.53: 10537+ AAAA? pve1.example.com. (31) 10:24:30.836546 ens18 Out IP 172.31.101.63.54386 > 172.31.101.3.53: 61739+ A? pve1.example.com. (31) 10:24:30.882010 ens18 Out IP 172.31.101.63.36560 > 172.31.101.3.53: 27071+ AAAA? pve1.example.com. (31) 10:24:30.882084 ens18 Out IP 172.31.101.63.35888 > 172.31.101.3.53: 2237+ A? pve1.example.com. (31) 10:24:30.882799 ens18 Out IP 172.31.101.63.40720 > 172.31.101.3.53: 1513+ AAAA? pve1.example.com. (31) 10:24:30.882850 ens18 Out IP 172.31.101.63.46123 > 172.31.101.3.53: 51690+ A? pve1.example.com. (31) 10:24:30.883968 ens18 Out IP 172.31.101.63.35197 > 172.31.101.3.53: 59263+ AAAA? pve1.example.com. (31) 10:24:30.883999 ens18 Out IP 172.31.101.63.33168 > 172.31.101.3.53: 34686+ A? pve1.example.com. (31) 10:24:30.886705 ens18 Out IP 172.31.101.63.47298 > 172.31.101.3.53: 52549+ AAAA? pve1.example.com. (31) 10:24:30.886756 ens18 Out IP 172.31.101.63.51645 > 172.31.101.3.53: 7494+ A? pve1.example.com. (31) 10:24:30.919554 ens18 Out IP 172.31.101.63.55937 > 172.31.101.3.53: 55708+ AAAA? pve1.example.com. (31) 10:24:30.919575 ens18 Out IP 172.31.101.63.50858 > 172.31.101.3.53: 10394+ A? pve1.example.com. (31) 10:24:30.923605 ens18 Out IP 172.31.101.63.60503 > 172.31.101.3.53: 23480+ A? pve1.example.com. (31) 10:24:30.923621 ens18 Out IP 172.31.101.63.35736 > 172.31.101.3.53: 28602+ AAAA? pve1.example.com. (31) 10:24:30.943725 ens18 Out IP 172.31.101.63.50685 > 172.31.101.3.53: 12282+ A? pve1.example.com. (31) 10:24:30.943731 ens18 Out IP 172.31.101.63.60563 > 172.31.101.3.53: 54008+ AAAA? pve1.example.com. (31) 10:24:30.945043 ens18 Out IP 172.31.101.63.50459 > 172.31.101.3.53: 32481+ AAAA? pve1.example.com. (31) 10:24:30.945084 ens18 Out IP 172.31.101.63.59763 > 172.31.101.3.53: 19950+ A? pve1.example.com. (31) 10:24:30.965176 ens18 Out IP 172.31.101.63.54811 > 172.31.101.3.53: 11120+ AAAA? pve1.example.com. (31) 10:24:30.965221 ens18 Out IP 172.31.101.63.51486 > 172.31.101.3.53: 25714+ A? pve1.example.com. (31) 10:24:30.980364 ens18 Out IP 172.31.101.63.57847 > 172.31.101.3.53: 1703+ AAAA? pve1.example.com. (31) 10:24:30.980394 ens18 Out IP 172.31.101.63.38035 > 172.31.101.3.53: 56481+ A? pve1.example.com. (31) 10:24:30.995643 ens18 Out IP 172.31.101.63.48350 > 172.31.101.3.53: 61278+ AAAA? pve1.example.com. (31) 10:24:30.995653 ens18 Out IP 172.31.101.63.49696 > 172.31.101.3.53: 4700+ A? pve1.example.com. (31) 10:24:31.857726 ens18 Out IP 172.31.101.63.40907 > 172.31.101.3.53: 28282+ AAAA? pve1.example.com. (31) 10:24:31.857741 ens18 Out IP 172.31.101.63.57303 > 172.31.101.3.53: 50549+ A? pve1.example.com. (31) 10:24:31.878776 ens18 Out IP 172.31.101.63.34053 > 172.31.101.3.53: 27416+ A? pve1.example.com. (31) 10:24:31.878782 ens18 Out IP 172.31.101.63.45957 > 172.31.101.3.53: 12314+ AAAA? pve1.example.com. (31) 10:24:31.894279 ens18 Out IP 172.31.101.63.56167 > 172.31.101.3.53: 21009+ AAAA? pve1.example.com. (31) 10:24:31.894521 ens18 Out IP 172.31.101.63.54023 > 172.31.101.3.53: 34320+ A? pve1.example.com. (31) 10:24:31.910402 ens18 Out IP 172.31.101.63.56910 > 172.31.101.3.53: 40104+ AAAA? pve1.example.com. (31) 10:24:31.910412 ens18 Out IP 172.31.101.63.42312 > 172.31.101.3.53: 57262+ A? pve1.example.com. (31) 10:24:31.926808 ens18 Out IP 172.31.101.63.34961 > 172.31.101.3.53: 51122+ AAAA? pve1.example.com. (31) 10:24:31.926814 ens18 Out IP 172.31.101.63.46702 > 172.31.101.3.53: 2227+ A? pve1.example.com. (31) 10:24:31.944990 ens18 Out IP 172.31.101.63.59537 > 172.31.101.3.53: 12641+ A? pve1.example.com. (31) 10:24:31.944996 ens18 Out IP 172.31.101.63.39000 > 172.31.101.3.53: 49791+ AAAA? pve1.example.com. (31) 10:24:32.672246 ens18 Out IP 172.31.101.63.48070 > 172.31.101.3.53: 28613+ A? pve1.example.com. (31) 10:24:32.672252 ens18 Out IP 172.31.101.63.46199 > 172.31.101.3.53: 16586+ AAAA? pve1.example.com. (31) 10:24:32.849731 ens18 Out IP 172.31.101.63.46989 > 172.31.101.3.53: 12357+ A? pve1.example.com. (31) 10:24:32.849738 ens18 Out IP 172.31.101.63.52755 > 172.31.101.3.53: 2119+ AAAA? pve1.example.com. (31) 10:24:32.867422 ens18 Out IP 172.31.101.63.40941 > 172.31.101.3.53: 20941+ AAAA? pve1.example.com. (31) 10:24:32.867428 ens18 Out IP 172.31.101.63.46737 > 172.31.101.3.53: 11212+ A? pve1.example.com. (31) 10:24:32.965591 ens18 Out IP 172.31.101.63.35713 > 172.31.101.3.53: 30043+ A? pve1.example.com. (31) 10:24:32.965597 ens18 Out IP 172.31.101.63.37769 > 172.31.101.3.53: 43610+ AAAA? pve1.example.com. (31) 10:24:32.984784 ens18 Out IP 172.31.101.63.60613 > 172.31.101.3.53: 56759+ AAAA? pve1.example.com. (31) 10:24:32.984852 ens18 Out IP 172.31.101.63.60176 > 172.31.101.3.53: 21689+ A? pve1.example.com. (31) 10:24:32.998703 ens18 Out IP 172.31.101.63.39826 > 172.31.101.3.53: 24200+ A? pve1.example.com. (31) 10:24:32.998718 ens18 Out IP 172.31.101.63.52592 > 172.31.101.3.53: 6799+ AAAA? pve1.example.com. (31) 10:24:32.999475 ens18 Out IP 172.31.101.63.47272 > 172.31.101.3.53: 64160+ A? pve1.example.com. (31) 10:24:32.999483 ens18 Out IP 172.31.101.63.55658 > 172.31.101.3.53: 48801+ AAAA? pve1.example.com. (31) 10:24:33.027889 ens18 Out IP 172.31.101.63.55483 > 172.31.101.3.53: 7618+ A? pve1.example.com. (31) 10:24:33.027896 ens18 Out IP 172.31.101.63.59118 > 172.31.101.3.53: 20158+ AAAA? pve1.example.com. (31) 10:24:33.028799 ens18 Out IP 172.31.101.63.44191 > 172.31.101.3.53: 34015+ AAAA? pve1.example.com. (31) 10:24:33.028847 ens18 Out IP 172.31.101.63.47545 > 172.31.101.3.53: 60864+ A? pve1.example.com. (31) 10:24:33.051526 ens18 Out IP 172.31.101.63.58955 > 172.31.101.3.53: 2714+ AAAA? pve1.example.com. (31) 10:24:33.051552 ens18 Out IP 172.31.101.63.52642 > 172.31.101.3.53: 54685+ A? pve1.example.com. (31) 10:24:33.067220 ens18 Out IP 172.31.101.63.39318 > 172.31.101.3.53: 28803+ AAAA? pve1.example.com. (31) 10:24:33.067225 ens18 Out IP 172.31.101.63.52008 > 172.31.101.3.53: 17280+ A? pve1.example.com. (31) 10:24:33.194727 ens18 Out IP 172.31.101.63.60295 > 172.31.101.3.53: 26735+ A? pve1.example.com. (31) 10:24:33.194735 ens18 Out IP 172.31.101.63.47578 > 172.31.101.3.53: 18797+ AAAA? pve1.example.com. (31) 10:24:33.396827 ens18 Out IP 172.31.101.63.46653 > 172.31.101.3.53: 41702+ A? pve1.example.com. (31) 10:24:33.396833 ens18 Out IP 172.31.101.63.33357 > 172.31.101.3.53: 63973+ AAAA? pve1.example.com. (31) 10:24:33.588367 ens18 Out IP 172.31.101.63.59844 > 172.31.101.3.53: 63510+ A? pve1.example.com. (31) 10:24:33.588377 ens18 Out IP 172.31.101.63.38221 > 172.31.101.3.53: 35345+ AAAA? pve1.example.com. (31) 10:24:33.791242 ens18 Out IP 172.31.101.63.45907 > 172.31.101.3.53: 8378+ A? pve1.example.com. (31) 10:24:33.791251 ens18 Out IP 172.31.101.63.33749 > 172.31.101.3.53: 63941+ AAAA? pve1.example.com. (31) 10:24:33.939441 ens18 Out IP 172.31.101.63.36818 > 172.31.101.3.53: 8340+ A? pve1.example.com. (31) 10:24:33.939870 ens18 Out IP 172.31.101.63.33774 > 172.31.101.3.53: 33175+ AAAA? pve1.example.com. (31)

My temporary workaround was to remove all the Proxmox hosts and re-add them using the IP address, which stops the DNS queries. I did miss Pegaprox when I had it stopped.