As pointed out in a comment (https://forums.theregister.com/forum/all/2021/12/21/tiktok_t...), the TikTok app seems to really spam up DNS requests, so we cannot be sure if it's really an active TikTok user or just background requests. On the other hand, Microsoft.com seems on the top also, which is reasonable except when you think it carefully that it should be office.com, live.com, or windows.com and not microsoft.com.
May be the app try to reconnect to TikTok BECAUSE he blocked the DNS. So no connection could be established and it will repeat again and again. Also, DNS spamming doesn't make much sense to me.
> Also, DNS spamming doesn't make much sense to me.
What do you think is the cause of the headaches of DNS operators when Facebook was MIA? It was less of an headache when Youtube went poof because theirs was set at 1hr instead of Facebook's 5mins.
Also, for the record, Tiktok has its TTL set to 1 minute, and Facebook apps requests domains at ~5min intervals, while other apps are much more behaved and queried at ~1hr. Both of them seems too aggressive in DNS refreshing for some reason, unlike Google which sets a ~1h refresh rate and Microsoft at 24hrs for non-Azure things (Azure is more aggressive at 3 minutes and 25 seconds? That's a weird value to set.)
3 comments
[ 3.3 ms ] story [ 20.4 ms ] threadWhat do you think is the cause of the headaches of DNS operators when Facebook was MIA? It was less of an headache when Youtube went poof because theirs was set at 1hr instead of Facebook's 5mins.
Also, for the record, Tiktok has its TTL set to 1 minute, and Facebook apps requests domains at ~5min intervals, while other apps are much more behaved and queried at ~1hr. Both of them seems too aggressive in DNS refreshing for some reason, unlike Google which sets a ~1h refresh rate and Microsoft at 24hrs for non-Azure things (Azure is more aggressive at 3 minutes and 25 seconds? That's a weird value to set.)