Telegram component and dns query

Development
1

Hi all,

I don’t know if it’s the right place to post or i should open an issue on github but… here it is.

I’m using the Telegram platform to send notification on my phone, but I’ve seen a lot of dns request to my local dns server, about one every five seconds, here is what I’m talking about:

Oct 30 15:20:08 dnsmasq[19282]: 3566 127.0.0.1/37303 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:20:13 dnsmasq[19282]: 3568 127.0.0.1/36185 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:20:18 dnsmasq[19282]: 3570 127.0.0.1/48509 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:20:25 dnsmasq[19282]: 3572 127.0.0.1/55140 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:20:30 dnsmasq[19282]: 3574 127.0.0.1/45211 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:20:36 dnsmasq[19282]: 3576 127.0.0.1/46554 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:20:41 dnsmasq[19282]: 3578 127.0.0.1/45435 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:20:47 dnsmasq[19282]: 3580 127.0.0.1/53241 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:20:53 dnsmasq[19282]: 3582 127.0.0.1/38856 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:20:58 dnsmasq[19282]: 3584 127.0.0.1/59221 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:21:03 dnsmasq[19282]: 3586 127.0.0.1/49408 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:21:09 dnsmasq[19282]: 3588 127.0.0.1/42173 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:21:14 dnsmasq[19282]: 3590 127.0.0.1/57437 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:21:20 dnsmasq[19282]: 3592 127.0.0.1/45484 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:21:25 dnsmasq[19282]: 3594 127.0.0.1/51368 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:21:30 dnsmasq[19282]: 3596 127.0.0.1/50591 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:21:35 dnsmasq[19282]: 3598 127.0.0.1/46044 query[A] api.telegram.org from 127.0.0.1
Oct 30 15:21:41 dnsmasq[19282]: 3600 127.0.0.1/60250 query[A] api.telegram.org from 127.0.0.1

I’m 100% sure that the query comes from Home Assistant because on localhost it’s the only thing running that could query for api.telegram.com. Is this behaviour normal? Why the ‘telegram’ module doesn’t keep in cache the hostname for at least the ttl time in the dns response?

Thanks all.

1 Like
3

Captura%20de%20ecr%C3%A3_2019-06-29_14-09-58
Captura%20de%20ecr%C3%A3_2019-06-29_14-09-58372×567 26.2 KB

Same here ±35000 dns queries every day.
2 queries every 5 seconds :open_mouth:

4

Can you do anything against it? This spamming is really anoying…

5

Hi ,
I’m facing exactly the same SPAM every seconds from the HA to API.telegram.com.
Any way to stop this ? it doesn’t provide me any value as I only use to post some messages and not the other way …

image
image656×685 25.7 KB

6

изображение
изображение720×561 26.1 KB

The same thing. Too many requests to api.telegram.org.

7

The same here, i think it is worst in the last release

photo_2020-08-08_20-50-23
photo_2020-08-08_20-50-231280×720 63.7 KB

Here can see when i update HA

8

I have been using telegram in Nodered without issues. I know that’s not the same as the HA component, but figured I’d mention it if it helps with debugging. Here’s the last 24hrs from my HA instance, and telegram isn’t even on the top requested domains:

 5365   api.weather.gov                           
 4375   version.home-assistant.io                 
 2006   raw.githubusercontent.com                 
 2006   grafana.com                               
 1188   api.telegram.org                          
 571    github.com                                whitelisted
 158    api.github.com                            
 50     usage.influxdata.com                      
 44     updater.home-assistant.io                 
 26     registry-1.docker.io