Sponsored Content
Special Forums Cybersecurity Need Help with this TCPDUMP output... Post 302908014 by RudiC on Thursday 3rd of July 2014 05:02:57 AM
Old 07-03-2014
I'd say it's not a query but the answer from a DNS server holding all the A records for a domain that has been queried.
 

10 More Discussions You Might Find Interesting

1. Programming

How To Use tcpdump

I have two net-card. one is 172.16.24.99(ENG) ,another is 172.16.25.99(ENG-B). Both masks is 255.255.255.0. I will monitor data on the tcp port 8055 in ENG, How do I set option of tcpdump command (2 Replies)
Discussion started by: chenhao_no1
2 Replies

2. UNIX for Dummies Questions & Answers

tcpdump

does anybody know what the -d -dd and -ddd options are used for ? thanks (2 Replies)
Discussion started by: ant04
2 Replies

3. Shell Programming and Scripting

Tcpdump in cron

I wrote a short BASH script to run tcpdump and save the output to a log file for when I'm away from my desk. The script runs fine normally, but fails to start in cron. Any ideas? #!/bin/bash today=`date +%Y%m%d` tcpdump -i eth0 -s 1500 -w ${today}.cap & exit (5 Replies)
Discussion started by: paulzeromi
5 Replies

4. Shell Programming and Scripting

analyzing tcpdump output

hello, i have a lot of pcap files (tcpdump output) that i want to compare. every tcpdump output has two file, server and client. what i want to do is: 1. take timestamp, source address, destination address, and packet id from each file (server and client) 2. find the packets sent from... (0 Replies)
Discussion started by: slumpia
0 Replies

5. Cybersecurity

i would like to know about tcpdump

i would like to know about tcpdump i would like to use tcpdump to get information about these - Date - time - source hostname - source mac address - source ip address - destination ip address - see outbound only then i use command like this tcpdump -i le0 -n -q -tttt -e src net... (0 Replies)
Discussion started by: chamnanpol
0 Replies

6. IP Networking

i would like to know about tcpdump

i would like to know about tcpdump i would like to use tcpdump to get information about these - Date - time - source hostname - source mac address - source ip address - destination ip address - see outbound only then i use command like this tcpdump -i le0 -n -q -tttt -e src net... (2 Replies)
Discussion started by: chamnanpol
2 Replies

7. Shell Programming and Scripting

write a script to parse some tcpdump output

i am trying to write a script to parse some tcpdump output, in each line of the tcpdump output, I know for sure there are 3 keywords exist: User{different usernamehere} NAS_ipaddr{different ip here} Calling_station{ip or dns name here} But the positions for these 3 keywords in the... (4 Replies)
Discussion started by: fedora
4 Replies

8. IP Networking

tcpdump vs. wireshark

Hi, I am trying to capture manually crafted IP packets, created using Scapy, to a pcap file that can later be replayed using tcpreplay. When using wireshark, I can successfully capture these packets and view them in wireshark. However, when using tcpdump, these packets are then shown in... (2 Replies)
Discussion started by: yotamhc
2 Replies

9. Debian

Tcpdump Help !

Hi. Need Help with TcpDump Trying to sniff associatio-request with tcpdump but when i run this tcpdump -i eth0 wlan subtype assoc-req i get this error can anyone help me with this error ? Thanks alot !!:) (1 Reply)
Discussion started by: SoulZB
1 Replies

10. IP Networking

TCPdump

I've recently started learning to use TCPdump, and I find it pretty interesting. There's one thing I don't understand. When I tell it to capture packets on, say, the WiFi interface en1, it often captures packets sent or received by other hosts on the network. How can it do this? My... (3 Replies)
Discussion started by: Ultrix
3 Replies
Net::DNS::Resolver::Programmable(3)			User Contributed Perl Documentation		       Net::DNS::Resolver::Programmable(3)

NAME
Net::DNS::Resolver::Programmable - programmable DNS resolver class for offline emulation of DNS VERSION
0.003 SYNOPSIS
use Net::DNS::Resolver::Programmable; use Net::DNS::RR; my $resolver = Net::DNS::Resolver::Programmable->new( records => { 'example.com' => [ Net::DNS::RR->new('example.com. NS ns.example.org.'), Net::DNS::RR->new('example.com. A 192.168.0.1') ], 'ns.example.org' => [ Net::DNS::RR->new('ns.example.org. A 192.168.1.1') ] }, resolver_code => sub { my ($domain, $rr_type, $class) = @_; ... return ($result, $aa, @rrs); } ); DESCRIPTION
Net::DNS::Resolver::Programmable is a Net::DNS::Resolver descendant class that allows a virtual DNS to be emulated instead of querying the real DNS. A set of static DNS records may be supplied, or arbitrary code may be specified as a means for retrieving DNS records, or even generating them on the fly. Constructor The following constructor is provided: new(%options): returns Net::DNS::Resolver::Programmable Creates a new programmed DNS resolver object. %options is a list of key/value pairs representing any of the following options: records A reference to a hash of arrays containing a static set of Net::DNS::RR objects. The hash entries must be indexed by fully qualified domain names (lower-case, without any trailing dots), and the entries themselves must be arrays of the RR objects pertaining to these domain names. For example: records => { 'example.com' => [ Net::DNS::RR->new('example.com. NS ns.example.org.'), Net::DNS::RR->new('example.com. A 192.168.0.1') ], 'www.example.com' => [ Net::DNS::RR->new('www.example.com. A 192.168.0.2') ], 'ns.example.org' => [ Net::DNS::RR->new('ns.example.org. A 192.168.1.1') ] } If this option is specified, the resolver retrieves requested RRs from this data structure. resolver_code A code reference used as a call-back for dynamically retrieving requested RRs. The code must take the following query parameters as arguments: the domain, RR type, and class. It must return a list composed of: the response's RCODE (by name, as returned by Net::DNS::Header->rcode), the "aa" (authoritative answer) flag (boolean, use undef if you don't care), and the Net::DNS::RR answer objects. If an error string is returned instead of a valid RCODE, a Net::DNS::Packet object is not constructed but an error condition for the resolver is signaled instead. For example: resolver_code => sub { my ($domain, $rr_type, $class) = @_; ... return ($result, $aa, @rrs); } If both this and the "records" option are specified, then statically programmed records are used in addition to any that are returned by the configured resolver code. defnames dnsrch domain searchlist debug These Net::DNS::Resolver options are also meaningful with Net::DNS::Resolver::Programmable. See Net::DNS::Resolver for their descriptions. Instance methods The following instance methods of Net::DNS::Resolver are also supported by Net::DNS::Resolver::Programmable: search: returns Net::DNS::Packet query: returns Net::DNS::Packet send: returns Net::DNS::Packet Performs an offline DNS query, using the statically programmed DNS RRs and/or the configured dynamic resolver code. See the "new" constructor's "records" and "resolver_code" options. See the descriptions of search, query, and send for details about the calling syntax of these methods. print string: returns string searchlist: returns list of string defnames: returns boolean dnsrch: returns boolean debug: returns boolean errorstring: returns string answerfrom: returns string answersize: returns integer See "METHODS" in Net::DNS::Resolver. Currently the following methods of Net::DNS::Resolver are not supported: axfr, axfr_start, axfr_next, nameservers, port, srcport, srcaddr, bgsend, bgread, bgisready, tsig, retrans, retry, recurse, usevc, tcp_timeout, udp_timeout, persistent_tcp, persistent_udp, igntc, dnssec, cdflag, udppacketsize. The effects of using these on Net::DNS::Resolver::Programmable objects are undefined. SEE ALSO
Net::DNS::Resolver For availability, support, and license information, see the README file included with Net::DNS::Resolver::Programmable. AUTHORS
Julian Mehnle <julian@mehnle.net> perl v5.16.3 2014-06-09 Net::DNS::Resolver::Programmable(3)
All times are GMT -4. The time now is 02:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy