1. Current Location: Home >  Router Encyclopedia >  Even after changing the encrypted DNS, I still got rushed to answer. After capturing the packet, I saw that UDP 53 was just a postcard

Even after changing the encrypted DNS, I still got rushed to answer. After capturing the packet, I saw that UDP 53 was just a postcard

Encrypted DNS schematic: plaintext DNS runs on UDP53, like a postcard that can be answered halfway; DoH and DoT put the diversion strip into an envelope; browser secure DNS, Android private DNS, and router each have their own switches

Last time, I wrote about optical modem changing DNS, and at the end I just tossed out a line, "The only solution to this quick answer is encrypted DNS," so I didn't elaborate. Later, people started asking: What is encrypted DNS? I've changed my DNS to 223.5.5.5, but why do some websites still lead to strange places? This time, I checked the bag and switches one by one, explaining everything clearly.

Let's first see what this postcard looks like

To get straight to the point: every time you type a website, the 'Ask for Directions' sent by the browser is on port 53 of UDP, not encrypted.

I used Python to send a query to 223.5.5.5 and typed out the original byte it returned. After the 12-byte header, the URL you asked for is immediately followed — broken down into segments by point, length plus content, blatantly placed in the bag. From what I found, www.shunot.com three words in ByteFlow are readable with the naked eye, without even decoding. Whatever you ask, whatever it answers, every device on this road can see it clearly.

No one has taken this seriously because people assume "just watch, it's just an IP address." But if you can see it, you can make changes. And this plain road is not short: the home optical modem, corridor equipment, and the operator's metropolitan area network all the way, every hop is worth passing. webpages have long been packed into HTTPS envelopes, but the note for 'asking for directions' has always been a postcard, walking naked.

Encrypted DNS does only one thing: put postcards into envelopes. After installation, when you grab packets from outside, you can only see a connection to port 443, which looks exactly like the traffic you use when browsing web pages. It answers whatever questions you ask, but you can't see it from outside or get in.

How does the buzzer happen

?

The DNS protocol is designed to be especially polite: you shout a word, and whoever answers first gets the upper either. Normally, the DNS you asked for answers first, but on the plaintext route, any device along the way can get a fake one before the real answer is delivered. Your browser can't tell real from fake, first come, first served, and you'll end up getting led into the trench.

To verify if someone has been rushed to answer, no need to install any tools. 114 has set up a dedicated detection domain:

nslookup whether.114dns.com 223.5.5.5

The normal return is the official 114 IP; If you return to 127.0.0.1 or another strange address, congratulations, someone is rushing to answer on your road. Last time, after my cousin changed her DNS, the ads stopped for two months and popped up again. That's the reason—her DNS was correct, but the real issue was that the plaintext route was still in place, and people rushing to answer kept trying different ways to insert it.

By the way

, the ones who rush to answer are not necessarily the operators. Company networks, hotel WiFi, and unknown public networks all dare to do this. This is different from router being hacked and DNS changed: DNS being changed means someone tampered with the home router, and rushing to answer means someone intercepted on the road—one checks the house, the other checks the road.

DoH and DoT, two crypto postal services

There are two ways to pack an envelope; sooner or later, you'll come across these two abbreviations, so recognize the face first.

One is called DoH, which puts DNS queries into HTTPS and runs through port 443, mixing them with web traffic. The advantage is it's hidden; it's hard to remove it by itself—typing 443 is like blocking the entire webpage. The other is DoT, where you set up port 853 and use dedicated encrypted DNS—clearly separated, easy to manage and block. That's why company network administrators block private DNS with a single seal: the 853 dedicated port is too conspicuous, and the firewall rules take it away; And DoH is mixed in with the crowd; if you want to fight it, you have to take the webpage down with you.

I shook my hand on port 853 of 223.5.5.5, pulled out the certificate, and checked: CN is *.alidns.com, issuer is Alibaba, verification passed. This is another benefit of encryption—you have the credentials to decide who you're connecting to. In plaintext mode, the responder can pretend to be any DNS reply, but in encrypted mode, it cannot deliver a verifiable certificate and cannot be spoofed.

For home use, you don't need to memorize terminology—just remember one sentence: Android's 'private DNS' uses DoT, while the browser's 'secure DNS' mostly uses DoH. The envelopes are different, and they all contain your own asking list.

Each of the three switches has its own layer; don't expect one to cover everything

This is the easiest part to get confused by tutorials: the three switching transistors have completely different ranges across three layers, and opening the wrong layer is equivalent to not opening at all.

. is . is
Where the switch is, who has a weakness
Browser security DNSChrome settings → privacy and security→ security → using secure DNS only cares about the browser itself, WeChat, and various apps are ignored
Android private DNS settings → network and internet→ private DNSactivated on the whole system, but if you fill in the wrong one and cannot access the internet, iOS doesn't have this entry point
Router-side encrypted DNSbasically not available for home firmware. Installing OpenWrt plugins with FamilyMart and IoT devices has a high entry barrier, and regular firmware is out of reach

The browser layer is the easiest to get started. Enter https://dns.alidns.com/dns-query in Chrome's custom box. Note that it only recognizes domain names; if you enter a pure IP like 223.5.5.5, it won't recognize it. Firefox needs to be opened manually in the settings; our network environment doesn't push it by default. There's a pitfall: If you fill in this box incorrectly, it doesn't report an error and quietly returns to plaintext. You think it's open, but actually it hasn't.

After

Android 9.0, there is a "private DNS" option. The path is shown in the table above. For hostnames, enter dns.alidns.com or Tencent's dot.pub. Don't accidentally add the HTTPS prefix—that is the DoT hostname, not the URL. iOS doesn't even have this setup portal. If you want system-level encryption and install a description file, that's far beyond what ordinary people can handle. My suggestion is that Apple users can just use the browser layer to get to the end.

The router layer is the most awkward. After searching all the home backends for Xiaomi Mercury, I couldn't find this feature. changing the router's DNS is still the plaintext setup. If you want your whole family to encrypt together, including the camera and vacuum cleaner, you have to flash OpenWrt to install plugins. I mentioned this threshold in my post < a href="https://www.shunot.com/en/lybk/741.html"> choosing public DNS, so it's not worth flashing for this. There's also the reality: even if the router encrypts this layer, the IoT device's built-in DNS can't be blocked. Whether this layer is enabled or not is the "big deal," not the "entirety."

The cost of the cost

must be settled on the table

Encryption isn't something you get for free—I tested it twice.

The first is delay. On the same machine, plaintext UDP takes 13 to 52 milliseconds to query two public DNS providers, while DoH takes 62 to 77 milliseconds to create a new connection — all that comes out is TLS handshakes. Fortunately, both browsers and systems reuse connections: the first time you ask for directions, you seal the envelope properly, then use the same envelope afterwards. You don't have to reseal every domain. So in real experience, the only real experience is a few dozen milliseconds slower, and the perception when browsing web pages is unnoticed. If you really care, try to choose a DNS as close as possible (domestic Alibaba and Tencent), since the handshake part is already short.

The second is scheduling. Using Alibaba and Tencent's encrypted DNS domestically doesn't really matter—it can see your real exit and send a photo to your nearest node that needs it. But if you use those overseas encrypted DNS systems like 1.1.1.1 or 8.8.8, video sites might set up a remote node for you, and watching videos will spin in circles. This pitfall was covered in the article

There's another pitfall to be mentioned in advance: some company and campus websites block both 853 and custom DoH. After entering the Android private DNS list, you find your phone can't access the internet. Don't panic—delete it and restore it. It's not that the phone is broken, but the network administrator won't allow it.

Who should drive, who should avoid trouble

To be honest: this is not a switch everyone should turn on.

? . If . The . There are
In your situation, do you want to open an order
Found out on nslookup that people rushed to answer and kept popping up ads. This is the cure-all
you don't have any symptoms, don't prescribe it just for the sake of it. Using Mingwen works fine
phone has been left unused for years, and the agent has already taken over the analysis
tons of smart home devices at home If the router layer can't be reached, it's accepted; the IoT traffic can't be managed

There's another easy expectation to hold on to first: encrypted DNS fixes "tampering on the road"—it can't fix the ads popped up by the website, nor the built-in promotions in certain apps you install. After launching, not a single ad was lost. First, think about where the ads actually came from—don't take the wrong medicine and get sick.

To wrap things up in order

: first use the whether.114dns.com line of command to check it thoroughly; if no one answers quickly, it's dispersed; After finding out, I tried opening the browser layer for a few days, but ads popped up before I accessed my phone's private DNS; Family-friendly encryption is a matter for those willing to mess with OpenWrt. By the way, after changing DNS not working, it's not all the fault of rushing to answer; half of it is because the cache hasn't expired. First, identify the root cause before acting.

Read More


Copyright Notice Scan to read on mobile
All Rights Reserved: 《SHUNOT》 => 《Even after changing the encrypted DNS, I still got rushed to answer. After capturing the packet, I saw that UDP 53 was just a postcard》
Article URL: https://www.shunot.com/en/lybk/1159.html
Unless otherwise stated, all articles are original by 《SHUNOT》. Reposting is welcome! Please indicate the original URL when reposting, thank you.

Contact Us

Online Consultation: Click here to send me a message

WeChat ID: master_135

Scan to follow