Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #1505
| From | buck <buck@private.mil> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: "Timeout" DNS IP to name resolution |
| Date | 2012-06-30 20:04 +0000 |
| Organization | Say What? |
| Message-ID | <jsnm4p01jqn@news4.newsguy.com> (permalink) |
| References | <js5006016b1@news1.newsguy.com> <a4vrv9F21bU2@mid.individual.net> <jskmvk02k52@news7.newsguy.com> <jsl0hn$q89$1@dont-email.me> |
Joe Beanfish <joebeanfish@nospam.duh> wrote in news:jsl0hn$q89$1@dont- email.me: > Not all IPs have names. Those will never resolve. > Question is whether jdresolve resolves any fewer than apache? Since Apache is now happy, I just reported my jdresolve "60% problem" for those who stumble across this thread. Apache does a lot better than jdresolve at rDNS. My upstream has 3 servers, 2 of which I'll call "balky" because they sometimes work and sometimes/often fail. Since I set up the system to use the one server that always works, the problem has been alleviated. Now, only a few timeouts a day occur. I think the problem with jdresolve is the Net::DNS Perl module it requires. If it were to become necessary, I could get the jdresolve script worked on to become hierarchical, first trying a caching DNS on the LAN, then the upstream NS, and finally - as a "last resort" effort - the root servers. But that isn't likely because the only benefits I find in jdresolve are that the IP can be anywhere in the logged line and that recursion can be turned on. Neither of those things are presently necessary. -- buck
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