This topic should probably be split, I don't think it has to do with nocords in particular. It seems a DNS issue on your network/host.
In any case, 267 milliseconds to a localhost nameserver is quite high, even considering this answer not being from cache - and esp. considering your low latency ping. mine returns in 4ms uncached and 0ms cached. Obviously Channels shouldn't time out at <=267ms, but it points to a place to investigate.
Can you run this command again, at least twice, so that the 2nd answer should come from cache? is 267ms a rather constant response time? Does it get even higher?
assuming any firewalls are configured to allow dns responses from the internet:
After doing that, try dig +trace nocords.xyz | grep Received. The response times that the dig client gets from the name servers are interesting.
Then, try dig +norecurse @ingrid.ns.cloudflare.com nocords.xyz | grep time:. This will ignore your local stuff and get the answer straight from the source. If this answer is fast, the issue is likely how your local nameserver is configured/behaving. I would experiment with not using the localhost nameserver and using your ISP's or Cloudflare's* directly. I don't use Ubuntu (or any systemd) but I think this blog or this thread is a good place to start.