Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #1495
| From | MJ <me@invalid.org> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: "Timeout" DNS IP to name resolution |
| Date | 2012-06-27 07:44 +0000 |
| Message-ID | <a4vrv9F21bU2@mid.individual.net> (permalink) |
| References | <js5006016b1@news1.newsguy.com> |
On Sat, 23 Jun 2012 17:56:22 +0000, buck wrote in js5006016b1@news1.newsguy.com : > I run a rather busy Apache web server with HostnameLookups On because > management wants it so. > > The problem is IP addresses that don't resolve. ... Management would be well-advised to allow you to use the Perl script named "jdresolve" to resolve IP addresses whenever any logfile analyses are needed, or subsets thereof. It can quickly recurse through any addresses to resolve domains for which A or PTR records don't exist (such as your point of failure), e.g.: $ echo 192.168.1.254 | jdresolve -n -a -r - 192.168.1.254.starband.com $ echo 123.45.67.89 | jdresolve -n -a -r - 123.45.67.89.dns.kr or entire files: # jdresolve -r -n -a /var/log/apache.log > /tmp/resolved.apache.log Your management will be highly pleased with your creative shell-scripted uses of the program, I promise. An example "probe_report" script output of dropped, logged, unsolicited packets from iptables: # /usr/local/bin/probe_report Resolved_Address Packets Bytes Protocol(s) Dest.Port(s) 195.161.40.7.rt-comm.ru 1 28 ICMP 211.147.3.19.datadragon.net 1 44 TCP 22 acyv254.neoplus.adsl.tpnet.pl 1 44 TCP 110 192.168.1.99.starband.com 210 82600 UDP 631 59.108.123.83.in-addr.cn 1 44 TCP 8080 _____________________________________________________________ Totals 214 80.8KB for search pattern "UNSOLICITED"
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
"Timeout" DNS IP to name resolution buck <buck@private.mil> - 2012-06-23 17:56 +0000
Re: "Timeout" DNS IP to name resolution Chris Davies <chris-usenet@roaima.co.uk> - 2012-06-23 22:29 +0100
Re: "Timeout" DNS IP to name resolution buck <buck@private.mil> - 2012-06-24 01:05 +0000
Re: "Timeout" DNS IP to name resolution Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2012-06-24 11:52 +0200
Re: "Timeout" DNS IP to name resolution Chris Davies <chris-usenet@roaima.co.uk> - 2012-06-24 12:15 +0100
Re: "Timeout" DNS IP to name resolution Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2012-06-24 11:09 -0500
Re: "Timeout" DNS IP to name resolution buck <buck@private.mil> - 2012-06-24 19:50 +0000
Re: "Timeout" DNS IP to name resolution Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2012-06-24 19:12 -0500
Re: "Timeout" DNS IP to name resolution J G Miller <miller@yoyo.ORG> - 2012-06-25 10:22 +0000
Re: "Timeout" DNS IP to name resolution MJ <me@invalid.org> - 2012-06-27 07:44 +0000
Re: "Timeout" DNS IP to name resolution buck <buck@private.mil> - 2012-06-29 17:00 +0000
Re: "Timeout" DNS IP to name resolution Joe Beanfish <joebeanfish@nospam.duh> - 2012-06-29 15:43 -0400
Re: "Timeout" DNS IP to name resolution buck <buck@private.mil> - 2012-06-30 20:04 +0000
Re: "Timeout" DNS IP to name resolution Martijn Lievaart <m@rtij.nl.invlalid> - 2012-06-30 00:58 +0200
csiph-web