truthfultemporarily

Seems weird to me, the router would need to do deep packet inspection of DNS and selectively block specific ones. It feels more like you've set up your DNS to do forwarding instead of resolution. Can you post a network diagram and the DNS config?

It's a gas where the chemical reaction of the combustion has produced enough energy to heat it up to a temperature where it emits visible light. Kind of like a glowing piece of metal, but in gas form.

It's a mixture of black body radiation and individual spectral lines.

The spectral lines happen when electrons fall from a high to a low energy state and the energy difference is emitted as light.

Black body radiation describes the fact that everything constantly emits electromagnetic radiation (=light). But what kind of light depends on the temperature with colder bodies like us humans emitting infrared whereas warmer bodies like the sun emit visible light. That is also why light temperature is a thing and the unit is Kelvin.

Here are some graphs and stuff: https://physics.stackexchange.com/questions/648273/does-fire-emit-black-body-radiation

Do tcpdump host $server instead. Otherwise you will only see the request (the response goes to a different port).

Just to be sure you do dig A @server $domain (with the "A") and can confirm the following

SERVER is your server

;; ANSWER SECTION is empty (or doesn't exist)

;; AUTHORITY SECTION mentions your local DNS server

Also check

dig NS @server $domain

Is your server in the answer section?

Mine doesn't seem to exist anymore sorry.

Here is how I would diagnose (I'm assuming you have Linux / WSL on a client)

1. Check the DNS record is actually set (yes do it again)
2. Do these steps on the client:
3. dig $domain check which server answered
4. dig a $domain should give a record
5. dig a $domain @server to make sure you're querying the right server

If none work, probably network issue (DNS boind to wrong IP, firewall, etc)

If 3 and 5 work but 4 doesn't, your DNS isn't authorative.

If only 5 works DNS settings on the client is wrong.

If you assume everything is compromised, there is no safety. You have to trust something at some point.

Usually, speaking from a professional IT perspective, people trust encryption. Once you do that, it does not matter how safe or unsafe the place where you store your data is.

AES, the encryption standard used by pretty much everything, is safe. It has not been weakened in any meaningful way since its inception and is also quantum - safe.

You could use for example openssl or Veracrypt or even just 7zip to encrypt it. If you don't trust these tools, encrypt it twice with two different ones, just put a txt file next to it with the exact steps to decrypt, because you will forget in which order you have done things.

Personally I have a homeserver that is encrypted at rest and then it uses restic to store encrypted backups in the cloud.

Ultrasonic cleaner! Really awesome for glasses, jewelry, all kinds of small stuff. I fill it with isopropanol solution and clean my phone case in it.

Thank you, I deleted my post so as to not share false info.

They should re-use that old apple ad "there is an app for that!"

"There is a boxer for that!"