Rwhois not serving all records - it is almost working though.
lesmith at ecsis.net
Wed May 4 16:53:19 CDT 2011
By no means an expert in rwhoisd, but my net directory has the
and the DATA directory contains the following:
From what you describe it sounds like things might not be in the
right places for rwhoisd to find them (but depends upon how heavily
your copy has been modified also)...
lesmith at ecsis.net
On Wed May 4 2011 14:40, Landon Stewart wrote:
> Hello NANOG,
> I sent this information to the rwhoisd mailing list originally but I've
> been informed that the mailing list is mostly dead now. I hope this is not
> too far off-topic for NANOG. One person replied to me off-list from the
> rwhois mailing list and had some help but I haven't found a solution yet.
> Scrapping our entire rwhois implementation and starting from scratch would
> be a shame since I don't have that many free cycles these days. If anyone
> has any info or can offer some information/help that'd be super duper
> Someone else installed this copy of rwhoisd and then that service was moved
> to a new server. The rwhois server we maintain is rwhois.hopone.net on
> port 4321. All of this used to work until the rwhois service and its
> directories were moved to a new server a few months ago. It hasn't worked
> quite right since then. I'm really not sure how it all works - I'm jumping
> into the middle of this since the person who set it up isn't around any
> more. I've checked for things as simple as permissions and file formatting
> but I can't find any problems.
> Anyway - The data files are exported from our customer database and look
> OK. By "OK" I mean they are getting exported, I'm not sure if there's a
> formatting issue or not. The files are generated regularly on another
> server that hasn't had any changes made to it so they should, in theory, be
> For this example I'll use 126.96.36.199 as the IP address in question. This
> is our address.
> When doing a lookup I see the following which is incomplete. Actually I'd
> like it to not display this at all personally. I'd like the customer
> information to be displayed instead but multiple records is fine (ours for
> the netblock and theirs for their allocation). See below for more
> information about the data files.
> # whois 188.8.131.52
> [Querying whois.arin.net]
> [Redirected to rwhois.hopone.net:4321]
> [Querying rwhois.hopone.net]
> %rwhois V-1.5:003fff:00 rwhois.hopone.net (by Network Solutions, Inc.
> network:Network-Name:Superb Internet Corporation
> network:Tech-Contact:hostmaster at superb.net
> network:Admin-Contact:hostmaster at superb.net
> network:Updated-By:rwhois at hopone.com
> %referral rwhois://root.rwhois.net:4321/auth-area=.
> The data files for this 184.108.40.206 are in a directory called
> /usr/local/rwhoisd/net-220.127.116.11-19. The directory looks like this:
> # pwd
> # ls -la
> total 40
> drwxr-xr-x 3 www wheel 4096 Mar 17 00:03 .
> drwxr-xr-x 26 rwhois rwhois 4096 Mar 17 00:03 ..
> drwxr-xr-x 3 www wheel 4096 Mar 17 00:05 data
> -rw-r--r-- 1 www wheel 125 Mar 17 00:03 schema
> -rw-r--r-- 1 www wheel 181 Mar 17 00:03 soa
> When changing into /usr/local/rwhoisd/net-18.104.22.168-19/data/network I see
> the data file that contains the information that should be served which is:
> # cat 1230-bakertrg.txt
> ID: 122.214.171.124.0/19
> Auth-Area: 126.96.36.199/19
> Network-Name: bakertrg
> Network-Block: 188.8.131.52-184.108.40.206
> Organization: Baker_TRG__Inc.
> IP-Used: 1
> Created: 20050124
> Updated: 20110317
> Updated-By: rwhois at hopone.net
> The local.db file at
> /usr/local/rwhoisd/net-220.127.116.11-19/data/network/local.db contains the
> following for this which I assume is correct
> Does anyone on this list have any idea why this data is not being served as
> expected through rwhois anymore? Some ideas on what to check would be
> helpful. I'd like to avoid resetting this up from scratch if there's an
> easy fix somewhere since it seems like its *almost* working.
> Thanks for taking the time to read this. I appreciate any help anyone can
> suggest on or off list.
More information about the NANOG