i'm not looking for an DDOS script
((Your not looking for a script???)) yet what I have below is the best method I can come up with, and it requires a batch script unless of course you want to hand key it to execute it manually, but the goto routine I dont think you could run unless you create a single lined concatenated batch file...lol
Best solution I can suggest is a goto loop in a batch file that writes the output to a text file. I would also add Date/Time Stamp to it in between each write of ping results so that when you have issues, you will have a somewhat good idea as to when it happened and for how long.
@echo OFF
:REPEAT
@echo. %date% at %time% >>PingLog.txt
ping www.google.com >>PingLog.txt
goto REPEAT
I used a batch similar to this a while back for issues, but got further info from traceroutes where my ISP had a bad DNS path due to them buying up cheap and not so reliable taps to the Internet Backbone. The engineer at my ISP who took quite a few on hold phone hops to get to found it rather embarrasing that a home user was able to find this issue through a batch file and traceroutes, while most people would just accept poor performance or blame their home hardware.
If you are having strange issues with DNS being resolved, manually change your DNS to an IP from another DNS provider like OpenDNS and see if you get different results. Maybe you too will find out your ISP has junky DNS paths to the Internet.
*Also this batch is very crude, in that you could make it better to strip it of everything but the ping results to be written to file if you want something clean with date/time and ping response times. Also you can change your ping path etc. I used Google since it is usually the best indicator of ISP issues since you should have pings less than 80ms, with 30-40ms being the best I have seen from my location. Also you may see the IP's change from where Google resolves as it is handled by the many Points of Presence that Google has for their search engine. Last time I checked I think the count was like 14 different IPs that
www.google.com resolves at.
Also you can alter the ping
www.google.com to ping
www.google.com -n 60 >>PingLog.txt if you want say 60 pings per date/time stamped interval, using the -n followed by the ping-count of times to ping as shown.