Sponsored Content
Full Discussion: Traceroute and Whois mystery
Special Forums IP Networking Traceroute and Whois mystery Post 24017 by The Fridgerator on Wednesday 3rd of July 2002 10:44:23 PM
Old 07-03-2002
Traceroute should tell you which routers the IP packets go through to get to/from the developer. It should have the developers IP as the last one, the 2nd last address should be his ISP.

WHOIS will just show the domain name of the ip address.
 

9 More Discussions You Might Find Interesting

1. Solaris

The Mystery Directory

Hello Everyone, I am currently running a large Server with Veritas Volumen Manager, attached to a EMC. uname -a SunOS 5.8 Generic_117350-47 sun4u sparc SUNW,Sun-Fire-880 I have one directory that tends to change to a file.Once in a while and always in different time.The file is the... (1 Reply)
Discussion started by: Peterh
1 Replies

2. UNIX for Advanced & Expert Users

A perplexing mystery

A perplexing mystery... please note that i am not a lacky, and the error below is misleading recently something i do all the time broke (a script). now when i run this script i get this error. /usr/bin/awk: 0403-027 The parameter list is too long. note that the (parameter list is... (9 Replies)
Discussion started by: nullwhat
9 Replies

3. Filesystems, Disks and Memory

I/O Error Mystery

I burned identical raw encrypted data to three cds using my new external Toshiba drive. My internal IBM read only drive does not get an I/O Error when reading in Circumstance #1, but does get an I/O Error in Circumstance #2. But, the Toshiba drive can do both circumstances without an error. ... (1 Reply)
Discussion started by: darkstarxor
1 Replies

4. Shell Programming and Scripting

Mystery about Case Statement

Can I make use of two command variable in case statement case $2 $3 in stp) Firewall disabled echo " Changing the http Proxy configuration " ;; str) Firewall enabled echo " Setting right http Proxy... (4 Replies)
Discussion started by: raghunsi
4 Replies

5. Shell Programming and Scripting

sort mystery

Hi everyone, I can't seem to understand the behavior of sort on a particular case. cat tmp25 1 a 10 b 20 c 2 d I do that: sort -k1,1 tmp25 1 a 10 b 2 d 20 c This one I understand, it's what i expected, from a string point of view 1<10<2<20 sort -k1... (9 Replies)
Discussion started by: a.brassac
9 Replies

6. Shell Programming and Scripting

whois country help

Hello folks, I have list of ips like 1.1.1.1 2.2.2.2 3.3.3.3 4.4.4.4 whois 1.1.1.1 |grep -E 'country|Country' it show country=US or whatever. so i have number of ips in text file, how i can use above script to automate output like 1.1.1.1 US 2.2.2.2 CA 3.3.3.3 FR (3 Replies)
Discussion started by: learnbash
3 Replies

7. UNIX for Dummies Questions & Answers

File permission mystery ?

Hello, running AIX 6.1 # ls -la /home/user1 drwxrwxrwx 8 user1 staff 4096 Apr 19 2011 . drwxr-xr-x 8 bin bin 256 Feb 08 2011 .. drwx---r-x 2 user1 staff 256 Apr 13 2011 dir1 # su - user2 $ cd /home/user1 $ ls dir1 ls: dir1: The file... (1 Reply)
Discussion started by: vilius
1 Replies

8. UNIX for Advanced & Expert Users

Apache Mod_rewrite Mystery

Hi Folks, I am running on a CentOS 6.3 server, whose primary function until recently has been my Zimbra mail server exclusively. I added wordpress and I have not been disappointed, with this one exception of Apache mod_rewrite. I have already tried to set selinux to permisive to eliminate that... (5 Replies)
Discussion started by: cjm51213
5 Replies

9. Shell Programming and Scripting

Shell functions mystery

so i noticed that when a shell script has a function defined in it, running "sh -x" on that shell script from the command line doesnt show what the function is doing. i like this. is there anyway for anyone to get around that? to be able to see exactly what a function or functions are doing? (4 Replies)
Discussion started by: SkySmart
4 Replies
DNSTOP(8)						    BSD System Manager's Manual 						 DNSTOP(8)

NAME
dnstop -- displays various tables of DNS traffic on your network SYNOPSIS
dnstop [-46apsQR] [-b expression] [-i address] [-f filter] [-r interval] [device] [savefile] DESCRIPTION
dnstop is a small tool to listen on device or to parse the file savefile and collect and print statistics on the local network's DNS traffic. You must have read access to /dev/bpf*. COMMAND LINE OPTIONS
The options are as follows: -4 count only messages with IPv4 addresses -6 count only messages with IPv6 addresses -Q count only DNS query messages -R count only DNS reply messages -a anonymize addresses -b expression BPF filter expression (default: udp port 53) -i address ignore select addresses -p Do not put the interface into promiscuous mode. -r Redraw interval (seconds). -l level keep counts on names up to level domain name levels. For example, with -l 2 (the default), dnstop will keep two tables: one with top-level domain names, and another with second-level domain names. Increasing the level provides more details, but also requires more memory and CPU. -f input filter name The "unknown-tlds" filter includes only queries for TLDs that are bogus. Useful for identifying hosts/servers that leak queries for things like "localhost" or "workgroup." The "A-for-A" filter includes only A queries for names that are already IP addresses. Certain Microsoft Windows DNS servers have a known bug that forward these queries. The "rfc1918-ptr" filter includes only PTR queries for addresses in RFC1918 space. These should never leak from inside an organiza- tion. The "refused" filter, when used with the -R option, tells dnstop to count only replies with rcode REFUSED. The "qtype-any" filter tells dnstop to count only message of type ANY. -n name Only count messages within the domain name -P Print "progress" messages on stderr when in non-interactive mode. -B buckets Use buckets hash table buckets. -X Do not tabulate the sources + query name counters. This can significantly reduce memory usage on busy servers and large savefiles. savefile a captured network trace in pcap format device ethernet device (ie fxp0) RUN TIME OPTIONS
While running, the following options are available to alter the display: s display the source address table d display the destination address table t display the breakdown of query types seen r display the breakdown of response codes seen o display the breakdown of opcodes seen 1 show 1st level query names 2 show 2nd level query names 3 show 3rd level query names 4 show 4th level query names 5 show 5th level query names 6 show 6th level query names 7 show 7th level query names 8 show 8th level query names 9 show 9th level query names ! show sources + 1st level query names @ show sources + 2nd level query names # show sources + 3rd level query names $ show sources + 4th level query names % show sources + 5th level query names ^ show sources + 6th level query names & show sources + 7th level query names * show sources + 8th level query names ( show sources + 9th level query names ^R reset the counters ^X exit the program space redraw ? help NON-INTERACTIVE MODE If stdout is not a tty, dnstop runs in non-interactive mode. In this case, you must supply a savefile for reading, instead of capturing live packets. After reading the entire savefile, dnstop prints the top 50 entries for each table. HOW MESSAGES ARE COUNTED
By default dnstop examines only query messages and ignores replies. In this case the response code table is meaningless and will likely show 100% "Noerror." If you supply (only) the -R command line option, dnstop examines replies and ignores queries. This allows you to see meaningful response code values, as well as all the other tables. In this case all the query attributes (such as type and name) are taken from the Question sec- tion of the reply. Note, however, that it is common for a stream of DNS messages to contain more queries than replies. This could happen, for example, if the server is too busy to respond to every single query, or if the server is designed to ignore malformed query messages. Therefore, you might want to examine both queries and replies by giving both -R and -Q command line options. In this case, only the response code counts are taken from the replies and all other attributes are taken from the queries. AUTHORS
Duane Wessels (wessels@measurement-factory.com) Mark Foster (mark@foster.cc) Jose Nazario (jose@monkey.org) Sam Norris <@ChangeIP.com> Max Horn <@quendi.de> John Morrissey <jwm@horde.net> Florian Forster <octo@verplant.org> Dave Plonka <plonka@cs.wisc.edu> http://dnstop.measurement-factory.com/ BUGS
Does not support TCP at this time. BSD
21 March, 2008 BSD
All times are GMT -4. The time now is 01:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy