3 ms·
>> Why doesn't DNS simply accept the fact that either: 1) your hosts are public 2) DNS is a stateful protocol and different clients _may_ see different respo
by heavenlyblue 7y ago
>>
Why doesn't DNS simply accept the fact that either:
1) your hosts are public
2) DNS is a stateful protocol and different clients _may_ see different responses by server? (e.g. return false denials for unauthorized clients)
- firethief 7y ago> 2) DNS is a stateful protocol and different clients _may_ see different responses by server? (e.g. return false denials for unauthorized clients) Caching is what makes DNS usable. If you do this in a way that doesn't break caching, it's not so simple.
- tptacek 7y ago"DNS" doesn't get to accept whether hosts are public or not; people who run DNS zones get to make that choice. Overwhelmingly, professional operators who run zones do not want them public.