Apparently this is something that just started yesterday and has affected
others as well. Here's what our system manager had to say:
If you want to answer your own tru64-unix mesg, the solution was to
add a DNS host reverse PTR file for each network that falls within
the below range of privately reserved networks. Also, you will
need to add these files to the named boot file, named.boot. The
changes will need to be made on any local secondary DNS hosts as
well.
Class A: 10.x.x.x
Class B range: 172.16.0.0-172.31.0.0
Class C range: 192.168.1.x-192.168.254.x
For more information on the private networks, refer to RFC 1918.
We had noticed that the problem didn't occur for two of our networks and
realized that they had entries already defined for them. It's been working
great ever since the changes were made.
================================================================================
Don Newcomer Dickinson College
Director of System and Network Management P.O. Box 1773
newcomer_at_dickinson.edu Carlisle, PA 17013
Phone: (717) 245-1256
FAX: (717) 245-1690
> We're running Digital UNIX 4.0B and something really strange started
> happening this afternoon. Starting at about 4:12 pm, users on our non-
> routable internal student networks started showing host names of
> read-rfc1918-for-details.iana.net. We rebooted, tried restarting named, to
> no avail. Have we been hacked or is there something else going on
> here? Thanks in advance.
Received on Wed Apr 21 1999 - 19:05:45 NZST