2 ms·
To make sure I'm tracking: the use case is setting up a dns server locally that can expose data over :53 and some other client can now get files over the dns pr
by sethammons 3y ago
To make sure I'm tracking: the use case is setting up a dns server locally that can expose data over :53 and some other client can now get files over the dns protocol. Is that right? So this is in hope that your work's network security is not monitoring DNS traffic?
- ldarby 3y agoNo, it's the other way round. You setup this DNS server to serve e.g. evil.com on the global internet. Then if you can control the client, you can just do regular DNS lookups for <longstring>.evil.com, that goes to the victim's DNS server, and that DNS server forwards it to this DNS server, which saves <longstring> (many of them) to a file. Edit: looking closer, this isn't exactly how this tool works, this DNS server assumes the client can send directly to this DNS server, I was assuming it didn't need to do that (and if it sends to the victim's DNS server instead, it's a lot harder to block). If you used it as I thought above, the output filename would just be "evil.com".