Petr Novotny <[EMAIL PROTECTED]> writes:
> got dnscache-0.92 from cr.yp.to, compiled, run ./dnsname 204.71.191.17
> The result is dnsname hogging 100% of CPU (the same way tcpserver does).
> This means two things:
> 1. I can temporarily solve the problem with tcpserver for SMTP
> service by disabling reverse lookups.
> 2. There's some bug in the DNS library.
(run against a local dnscache)
windlord:~> dnsname 204.71.191.17
dnsname: fatal: unable to find host name for 204.71.191.17: temporary failure
(run against a local BIND cache)
windlord:~> dig 204.71.191.17 @171.64.7.77
; <<>> DiG 2.2 <<>> 204.71.191.17 @171.64.7.77
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10
;; flags: qr aa rd ra; Ques: 1, Ans: 0, Auth: 0, Addit: 0
;; QUESTIONS:
;; 204.71.191.17, type = A, class = IN
;; ...truncated
;; Total query time: 7 msec
;; FROM: windlord.stanford.edu to SERVER: 171.64.7.77
;; WHEN: Tue Mar 14 06:25:33 2000
;; MSG SIZE sent: 31 rcvd: 31
I'm not seeing the runaway problem that you are, but reverse DNS for that
IP address definitely does not appear to be working.
Excerpts from dnstrace:
1 name.iad.gblx.net 209.130.187.10
name.iad.gblx.net 3600 A 204.152.166.155
1 name.iad.gblx.net 206.165.6.10
iad.gblx.net cache NS name.roc.frontiernet.net
iad.gblx.net cache NS name.phx.frontiernet.net
name.iad.gblx.net 3600 A 204.152.166.155
12 17.191.71.204.in-addr.arpa 209.130.187.10
ALERT: lame server; refers to .
12 17.191.71.204.in-addr.arpa 206.165.6.10
ALERT: resolution took more than 1 second
ALERT: lame server; refers to .
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
