|
Hi. My DNS operator sent me an email lately that I was using up all my DNS queries. I didn't even know I had a quota, but it lead me to check the usage on their dashboard, and starting on the day that installed tuwunel, I saw a 10x increase in incoming DNS requests. |
Replies: 3 comments 1 reply
|
It is normal. You connect to 4000+ servers on the matrix, and they are communicating. Leave that DNS operator, it's a scam. |
|
The Matrix protocol uses DNS. When you join other federated rooms that aren't locally hosted on your server, inbound and outbound DNS requests are made to other servers participating in that room for things like the homeserver key verification, event signing, the join process, fetching remote media, and just standard normal event/message sending; just to name some things. This is just how federated Matrix works. The volume of these requests greatly increases the more larger federated rooms you join. Even if you're the only single local user on your server, a single local user can still join many large federated rooms and generate lots of traffic and bandwidth. If you do not have a server provider that allows large amounts of DNS requests or connections or has strict/low bandwidth constraints, you may need to find a different provider. |
|
I figured as much. I was just hoping that there was some cache setting or something that might fix this. You're absolutely right that DNS requests shouldn't be capped, and that I might have to find another provider. Thanks =) |
|
We do have a built-in DNS cache that you can probably try tweaking, see https://github.com/matrix-construct/tuwunel/blob/main/tuwunel-example.toml#L212-L236 or maybe try using your own DNS cache with something like unbound (our recommendation). But really there shouldn't be a limit on your DNS requests... |
The Matrix protocol uses DNS. When you join other federated rooms that aren't locally hosted on your server, inbound and outbound DNS requests are made to other servers participating in that room for things like the homeserver key verification, event signing, the join process, fetching remote media, and just standard normal event/message sending; just to name some things.
This is just how federated Matrix works. The volume of these requests greatly increases the more larger federated rooms you join. Even if you're the only single local user on your server, a single local user can still join many large federated rooms and generate lots of traffic and bandwidth.
If you do not have a server …