N8N is DDOS-ing my DNS server

Describe the problem/error/question

Hey everyone, I recently started experimenting with N8N on my local home server to evaluate it’s use cases and benefits to my workflow. I tried to implement it with mattermost (slack-like communication tool) and as a result my network became unreachable and I was esentially DDOS-ing myself. I have spent hours and hours trying to resolve this and finally got a breakthrough when I enabled debug logs on my DNS server. Looks like that for my instance, N8N is going into some kind of a infinite loop when trying to resolve chaneels from mattermost. Interesting thing is that there are no logs on N8N and the mattermost logs seem normal, only the DNS gets spammed.

For the first few attempts, when I didn’t know what was happening, the result of this was complete failure of my local network which forced me to unplug the server LAN cable and reset the modem. In the meantime I added rate limiting to my DNS server, which reduced the bursts to 20 per second (my limit) but after the limit expires, it sends 20 by 20 by 20 until it breaks my home network again (this time it takes hours instead of minutes).

I would like to see if this is something that is expected and that should be handled outside of n8n or is this a bug. I don’t see a reason why does the DNS need to be pinged every time, especially as I have multiple cache layers.

My Home network setup is like this:

Proxmox PVE0 machine: NAS storage + proxmox + small compute

Proxmox PVE1 machine: k3s VM + bind9 VM + pi hole VM

DNS setup:

Pod reaches out to coredns (k3s dns) which proxies all tuxhub.cloud (my own domain) records to bind9 which will either resolve it to a local IP or forward it to pihole which will eventually contact 8.8.8.8.

The only fix for this is to kill the n8n pod and start again

What is the error message (if any)?

Attached is the video, keep in mind that

Please share your workflow

No saveable workflow, video attached.

Information on your n8n setup

  • n8n version: 2.0.3
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker/kubernetes
  • Operating system: proxmox debian

Video: Watch Screen Recording 2025-12-22 at 15.50.47 | Streamable

Looks like you’ve got a tricky DNS loop happening. I’d recommend checking the Mattermost node configuration in n8n to see if there are any settings related to polling or DNS resolution frequency. You could try adjusting those to see if it reduces the load on your DNS server. Let me know if this works!