Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too many DNS queries #192

Open
SproOve opened this issue Sep 19, 2024 · 4 comments
Open

Too many DNS queries #192

SproOve opened this issue Sep 19, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@SproOve
Copy link

SproOve commented Sep 19, 2024

What happened?

Hi, i just changed my pihole from one server to another and realized, that a lot of DNS queries came from only one client (30K of 60K in ~12 hours), and all these queries came from my iobroker client and wanted to know the adress of ny opendtu instance.

In the folowing images you can see, what impact it had. My iobroker client joined the pihole DNS midday and from then the dns queries went bonkers.

grafik
grafik
grafik

In one of these we can see, that it asks for the ip of it 15 times in 1 second.
I just wanted to ask, if you could reduce the amount of queries, the adapter is doing or even make it customizable in the settings, so everybody could adjust it to its needs.

Some might consider this not being a bug, but i cannot tell, why its important to resolve the hostname 15 times in one second.

Best regards!

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

OpenDTU version

24.8.5

Adapter version

2.0.0

Log

No response

@SproOve SproOve added the bug Something isn't working label Sep 19, 2024
@SproOve
Copy link
Author

SproOve commented Oct 7, 2024

It did not change:
Every time, when it should poll (e.g.) 30 seconds, it sends 8 DNS-queries, 4 for the direct hostname and 4 with the suffix .firtz.box
grafik

The version did not really change by installing over github, i'm still at 2.0.0. (Did you miss to add a release?)
I even tried to delete the adapter completely to exclude install/update errors, but im still at 2.0.0.

I dont know, if the poll intervall input was there before, but i cannot increase it higher than 59 seconds, so a workaround like "poll only every 20 minutes" doesnt work too unfortunately.

@mattreim
Copy link
Contributor

mattreim commented Oct 7, 2024

Maybe you can reduce the queries a bit by deactivating the mDNS function in OpenDTU.

@mcm1957
Copy link
Member

mcm1957 commented Oct 20, 2024

Looks like you do not resolve IPv6 records (AAAA) and do not resolve opendtu-56c2d8. So the system falls back to query IPv4 and fully qualified domain name.

I would suggest to either enter the ip address OR to enter the fully qualified domain name.

@SproOve
Copy link
Author

SproOve commented Oct 20, 2024

I dont think, IPV6 wasnt answered (see the topmost 2 AAAA requests):
grafik
But your answer was a hint to a partial cause of the problem. Firstly the domain is requested with the .fritz.box suffix, which leads to NXDOMAIN answers 2 times for IPv4 and 2 times for IPv6, so this is basically not related to this adapter but rather my network setup @ home. Still excluding these 4 NXDOMAIN requests leaves 4 requests standing. I'd accept 2 (1 for IPv4, 1 for IPv6) but two for each still looks like an issue in the code.

For now i switched to the IP-address in the adapter settings, which leads to no DNS queries at all and is fine., But still i'm curious, what causes the (now only) doubled requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants