Explore >> Select a destination
|
You are here 
|
csirt.lacnic.net | ||
| | | | |
brianreiter.org
|
|
| | | | | The DNS protocol traditionally runs over UDP on port 53. This is very fast but totally insecure. DNS queries can be snooped or potentially altered by anyone on the network. In my office, I use a pfSense firewall with the unbound DNS resolver configured to resolve DNS over TLS. That way my ISP neither my... | |
| | | | |
zwischenzugs.com
|
|
| | | | | InAnatomy of a Linux DNS Lookup - Part II covered: nsswitch /etc/hosts /etc/resolv.conf pingvshoststyle lookups and inAnatomy of a Linux DNS Lookup - Part III covered: systemdand itsnetworkingservice ifupandifdown dhclient resolvconf and ended up here: A (roughly) accurate map of what's going on Unfortunately, that's not the end of the story. There's still more things... | |
| | | | |
staex.io
|
|
| | | | | DNS protocol is one of the attack vectors on your corporate network and IoT devices in particular. Most operating systems access DNS servers using legacy unencrypted protocol by default despite the fact that there are modern secure enhancements for this protocol: DNSSEC, DNS-over-HTTPS, DNS-over-TLS. In this article we discuss these enhancements and explain how to configure them in your network. | |
| | | | |
thevisualchronicle.com
|
|
| | | 1 post published by Joe on October 14, 2024 | ||
