[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
--
Larry Smith
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
> appreciated.
>
> 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
> fine.
>
> For this example I'll use 66.36.235.19 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 66.36.235.19
> [Querying whois.arin.net]
> [Redirected to rwhois.hopone.net:4321]
> [Querying rwhois.hopone.net]
> [rwhois.hopone.net]
> %rwhois V-1.5:003fff:00 rwhois.hopone.net (by Network Solutions, Inc.
> V-1.5.9.5)
> network:Class-Name:network
> network:ID:66.36.224.0/19
> network:Auth-Area:66.36.224.0/19
> network:Network-Name:Superb Internet Corporation
> network:IP-Network:66.36.224.0/19
> network:Organization;I:Superb_Internet_Corporation
> network:Tech-Contact:hostmaster at superb.net
> network:Admin-Contact:hostmaster at superb.net
> network:Created:20050124
> network:IP-Total:8192
> network:IP-Used:3578
> network:IP-Available:4614
> network:IP-Usage:43.68
> network:Updated:20110317
> network:Updated-By:rwhois at hopone.com
>
> %referral rwhois://root.rwhois.net:4321/auth-area=.
> %ok
>
> The data files for this 66.36.231.147 are in a directory called
> /usr/local/rwhoisd/net-66.36.224.0-19. The directory looks like this:
> # pwd
> /usr/local/rwhoisd/net-66.36.224.0-19
> # 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-66.36.224.0-19/data/network I see
> the data file that contains the information that should be served which is:
> # cat 1230-bakertrg.txt
> ID: 1230.66.36.224.0/19
> Auth-Area: 66.36.224.0/19
> Network-Name: bakertrg
> Network-Block: 66.36.235.19-66.36.235.19
> 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-66.36.224.0-19/data/network/local.db contains the
> following for this which I assume is correct
> type:DATA
> file:net-66.36.224.0-19/data/network/1230-bakertrg.txt
> file_no:0
> size:220
> num_recs:1
> lock:OFF
>
> 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.