At the time of this writing the server ha s over 5 5 0 K Query Resolution Policies to deny query attempts to domains listed within thos e Q RPs. This was implemented on a non-domain joined physical server using Windows Server 2019. ![]() I did this using PowerShell, DNS policy, and some block lists from GitHub. Time is money!įor this scenario, I've developed a customized Windows based version of the popular Pi-Hole, just without the pretty GUI. In order to do this, I'll share some examples of how you can parse the DNS Analytical Log to find possible items of interest, since just scrolling through literally, what can be millions of lines of events, just doesn't sound like a fun time to me Nor is it really feasible. In this edition and in some future editions of the series, I'll be focusing on collecting data from the DNS Analytical Log, based on ce rtain use cases and presenting it in a more concise and useful manner. Now, I ga ve you gu ys a b re ak in Part 2 of the series an d kept that one s hor t, but br eak time is over, team I'm going back to a bit of a m ore in-depth discussion today, so buckle up and ge t comfortab le. ![]() Hi Team, it's Eric Jansen again, and as al ways, I'm excited to show you guys what I ha ve in store for y ou.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |