Menu

Post image 1
Post image 2
1 / 2
0

DNS hijacking: when someone else answers in your domain's name

DEV Community·Regő Botond Ronyecz·24 days ago
#sf4FB4AJ
#dns#how#security#devops#domain#records
Reading 0:00
15s threshold

Your users type your domain into their browser. They get a login page that looks exactly like yours. They enter their credentials. You never see any of it. That's DNS hijacking. No one broke into your servers. No one touched your code. They just changed where your domain points. How DNS actually works (the part that matters) When someone visits yourapp.com , their browser asks a DNS resolver: "what IP address is this?" The resolver checks its cache, and if it doesn't have an answer, it walks up the DNS hierarchy until it finds one. Your authoritative nameserver, the one you control through your registrar, gives the final answer. The whole process takes milliseconds and happens invisibly. It's also built on a foundation of trust. DNS was designed in 1983, when the internet was a handful of universities sharing files. Authentication was an afterthought added decades later, and most of the internet still doesn't use it. That gap is where hijacking lives.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More