|
You are here |
ariadne.space | ||
| | | | |
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... | |
| | | | |
venam.nixers.net
|
|
| | | | | Resolving hostnames (DNS?) might not seem like it, but it's complicated. Let's take a moment to see if we can at least demystify what happens on the client side instead of seeing it as a big tangled mess of configurations, libraries, and tools. | |
| | | | |
jameshfisher.com
|
|
| | | | | `nscd`, a local DNS resolver within `glibc`, is non-standard. Instead, use a local DNS server like `named` or `dnscache`. | |
| | | | |
blog.ikuamike.io
|
|
| | | Introduction After passing my OSCP, I am planning on doing CRTP and CRTO sometime this year. I took the OSCP exam before the updates that are focused on Active Directory so I didn't actively focus on this area. So to learn and practice on AD and Windows and also as some prep for the certifications I plan on taking, I will be doing some machines that are AD related and try to get into the details of the included misconfigurations and vulnerabilities. | ||