What's new

Tutorial DNS IP Hunt using Termux [Updated]

You do not have permission to view the full content of this post. Log in or register now.
Screenshot_20240103-221104.jpg
 

Attachments

turn off your pinging feature to a DNS server, a proper dns response from dig command is enough, your target is dns tunneling, not icmp tunneling, you'll get alot of false positive result because of that feature. find for dns servers that can answer from a recursion-desired query, yun yung legit na aandar sa dnstt.. im pretty sure nakita nyo na yung script leak ni Bon-chan, thats the pattern of preparing your dns server for dns tunneling
1. cache your query by calling A record first
2. then call the NS record to prepare the tunnel
its on bamsoftware readme git also.
 
turn off your pinging feature to a DNS server, a proper dns response from dig command is enough, your target is dns tunneling, not icmp tunneling, you'll get alot of false positive result because of that feature. find for dns servers that can answer from a recursion-desired query, yun yung legit na aandar sa dnstt.. im pretty sure nakita nyo na yung script leak ni Bon-chan, thats the pattern of preparing your dns server for dns tunneling
1. cache your query by calling A record first
2. then call the NS record to prepare the tunnel
its on bamsoftware readme git also.
boss pwede Hindi na gayahin Yung setup no boss PHC-TheGlock tapos Yung command na dig sapat na para ma Hunt dns
 
boss pwede Hindi na gayahin Yung setup no boss PHC-TheGlock tapos Yung command na dig sapat na para ma Hunt dns
yes actually ganon ang pinaka easier way: find way to print cidr into iplist, then loop them with dig command. to make it faster do multithreading or alternative make sets of processes by running with multiple screens in termux
 
turn off your pinging feature to a DNS server, a proper dns response from dig command is enough, your target is dns tunneling, not icmp tunneling, you'll get alot of false positive result because of that feature. find for dns servers that can answer from a recursion-desired query, yun yung legit na aandar sa dnstt.. im pretty sure nakita nyo na yung script leak ni Bon-chan, thats the pattern of preparing your dns server for dns tunneling
1. cache your query by calling A record first
2. then call the NS record to prepare the tunnel
its on bamsoftware readme git also.
Never pa ako nangalkal ng script ng iba, di ko nga alam na naleak mga scripts nila whatsoever. This cli-tool is using dig. what i meant for (only works for ping) is works only via ICMP but not dns-tunneling, may false positive kasi na DNS server na nagreresponse sa dig na di gumagana via DNSTT... Also this tool is not using ping (icmp) requests.
 
Never pa ako nangalkal ng script ng iba, di ko nga alam na naleak mga scripts nila whatsoever. This cli-tool is using dig. what i meant for (only works for ping) is works only via ICMP but not dns-tunneling, may false positive kasi na DNS server na nagreresponse sa dig na di gumagana via DNSTT... Also this tool is not using ping (icmp) requests.
Never pa ako nangalkal ng script ng iba
nasa trending threads yan yung nakaraan
what i meant for (only works for ping) is works only via ICMP but not dns-tunneling, may false positive kasi na DNS server na nagreresponse sa dig na di gumagana via DNSTT
You dont really need ICMP for checking, just a proper dns response from that server and you are done, do recursion check if you received a dns response thats all. If nakareceive ka ng connection reset issue, that means port 53 is an active service that is not actually a dns server or rather a restrictive firewall that automatically filters out incoming packets, tatagos talaga yan if babase ka sa timeout, kaya siguro naisipan mo lagyan ng ICMP Checking. Check your code, you need refined conditionals if connection reset occurs, kasi if hindi mo gagawin yan talagang dadaan ka sa ganyang logic (ICMP checking). 'fast response != success result'
 

Users search this thread by keywords

  1. Dnstt resolver
  2. Ip hunt
Back
Top