4 ms·

The issue here being: what happens when you have your proxy configured as "proxy.lan" but you make a typo when entering it in local DNS or in your browser setti

The issue here being: what happens when you have your proxy configured as "proxy.lan" but you make a typo when entering it in local DNS or in your browser settings? That DNS request for "proxy.lan" will now go all the way out to the root servers for every page load, multiple times. Not so important for you with your 200 tabs open, but quite important to the people maintaining the root servers who see a significant percentage of all queries being for bogus domains that don't exist.

prox 5y ago
Does this happen often? How do they mitigate this?
- d2wa 5y ago
  They burn money on the problem.
rualca 5y ago
> (...) but quite important to the people maintaining the root servers who see a significant percentage of all queries being for bogus domains that don't exist. I get the boys out rule sentiment, but isn't resolving domain names, even those that don't exist, the whole purpose of root servers? I mean, your suggestion reads like asking not to type URLs wrong because a significant percentage of requests are 404s.
- ratsmack 5y ago
  >... even those that don't exist, the whole purpose of root servers? The root servers shouldn't be a dumping ground for unnecessary traffic when proper DNS configuration is not that difficult.
  - rualca 5y ago
    I'm not sure you're getting it. You're complaining about a scenario where there's a misconfiguration error that's totally unintentional. No one is intentionally driving traffic to domains that don't exist. In fact, of said traffic hits the root servers, odds are that the system is effectively down and not receiving the traffic it's expected to receive, and a few developers are trying to figure out what's broken.
Shank 5y ago
What if you make a typo on .home.arpa? e.g., .home.arps? How is that any different?
- d2wa 5y ago
  Because all DNS software is supposed to know that the .arpa domain name is managed by the IETF and not ICANN. Or, rather, they know not to try to resolve it. There are a handful of different .arpa domains in use, and they all require special handling from your DNS server. E.g. reverse DNS/rDNS uses in-addr.arpa., and the DNS server in even the dumbest consumer-grade router will know how to respond to requests under that domain.
  - manquer 5y ago
    that doesn't mean anything if you typo on ".arpa". No DNS hardware is smart enough to know that you meant ".arpa" not ".apra" you actually typed in. Typos are not really a valid argument, it can happen for any type of domain.
peanut-walrus 5y ago
If you want to be a polite DNS resolver operator, root servers from B to G allow zone transfer, so you can just host the root zone locally. This way none of the typos or other bogus requests will leave your network.

prox 5y ago

Does this happen often? How do they mitigate this?

d2wa 5y ago
They burn money on the problem.

rualca 5y ago

> (...) but quite important to the people maintaining the root servers who see a significant percentage of all queries being for bogus domains that don't exist. I get the boys out rule sentiment, but isn't resolving domain names, even those that don't exist, the whole purpose of root servers? I mean, your suggestion reads like asking not to type URLs wrong because a significant percentage of requests are 404s.

ratsmack 5y ago
>... even those that don't exist, the whole purpose of root servers? The root servers shouldn't be a dumping ground for unnecessary traffic when proper DNS configuration is not that difficult.
- rualca 5y ago
  I'm not sure you're getting it. You're complaining about a scenario where there's a misconfiguration error that's totally unintentional. No one is intentionally driving traffic to domains that don't exist. In fact, of said traffic hits the root servers, odds are that the system is effectively down and not receiving the traffic it's expected to receive, and a few developers are trying to figure out what's broken.

Shank 5y ago

What if you make a typo on .home.arpa? e.g., .home.arps? How is that any different?

d2wa 5y ago
Because all DNS software is supposed to know that the .arpa domain name is managed by the IETF and not ICANN. Or, rather, they know not to try to resolve it. There are a handful of different .arpa domains in use, and they all require special handling from your DNS server. E.g. reverse DNS/rDNS uses in-addr.arpa., and the DNS server in even the dumbest consumer-grade router will know how to respond to requests under that domain.
- manquer 5y ago
  that doesn't mean anything if you typo on ".arpa". No DNS hardware is smart enough to know that you meant ".arpa" not ".apra" you actually typed in. Typos are not really a valid argument, it can happen for any type of domain.

peanut-walrus 5y ago

If you want to be a polite DNS resolver operator, root servers from B to G allow zone transfer, so you can just host the root zone locally. This way none of the typos or other bogus requests will leave your network.