[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference help::dns

Title:DECdns - Digital's Distributed Name Service
Notice:not to be confused with DNS: Domain Name Service (Kits: 1420,947))
Moderator:BULEAN::WHEATER
Created:Tue Apr 14 1987
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1443
Total number of notes:5833

1441.0. "DNS server & 'time jumps'" by COPCLU::PALMANN () Fri May 23 1997 05:55

About DNS-server version 2 and 'time jump'

My customer has a VMS based DNS server, ( witch for unknown reasons ) has been 
running, for a small period of time, in september-1998.
When the customer discovered the problem, DTSS was ajusted, and the server 
was brought back to may 1997.

Question :
I know DNS servers do not like this. Still...
Can we expect a DNS server to have the follow'ing problems after what it's been
trough. 
The customers server do not work anymore, but looks normal, expect from the 
following details :


show'ing that the DNS server is running, 

0000020E DNS$ADVER       LEF      5     2744   0 00:00:02.40      8909   2739
000002DB DNS$Server      LEF      9     1685   0 00:02:19.62     39652   7216

but

NCL>show dns server all

Node 0 DNS Server
at 1997-05-21-18:05:56.959+02:00Iinf

Status

    State                             = On

Characteristics

    Minimum Protocol Version          = V1.0.0
    Maximum Protocol Version          = V2.0.0
    UID                               = 6CAD9A18-D1E8-11D0-88E6-08002B9AB741
    Future Skew                       = +0-00:05:00.000I0.000
    Version                           = V2.0.0

Counters

    Creation Time                     = 1997-05-21-14:42:17.968+02:00Iinf
    Incompatible Protocol Errors      = 0
    Authentication Failures           = 0
    Read Accesses                     = 0
    Write Accesses                    = 0
    Skulks Initiated                  = 0
    Skulks Completed                  = 0
    Times Lookup Paths Broken         = 0
    Possible Cycles                   = 0
    Crucial Replica Removals Backed Out = 0
    Child Pointer Update Failures     = 0
    Security Failures                 = 0

NCL>
The server don't do a anything.
This could be do the fact that :
 
NCL>show dns server clear *

Node 0 DNS Server Clearinghouse *
at 1997-05-21-18:14:32.422+02:00Iinf

command failed due to:
 no such object instance
  
NCL>
and
DNS> show clear .denmark_ch
                                SHOW
                       CLEARINGHOUSE  XXXX:.denmark_ch
                                  AT  21-MAY-1997:18:25:44
Error on entity: XXXX:.denmark_ch
%DNS-E-NOCOMMUNICATION, Unable to communicate with any DECdns server

DNS>

( clering house name change for privacy to customer )

		-------------------------------

PS: The DNS server has been restored, and is now running.

			Jan.
T.RTitleUserPersonal
Name		DateLines
1441.1DRAGNS::SAUNDERSJohn Saunders, DECdns Engineering, (508) 275-5424Fri May 23 1997 11:0725
I'm new here, so I haven't seen this before. However:

Were there any interesting messages in the DNS$SERVER.LOG when the time was
restored? Any OPCOM messages?

I can easily see the server rejecting the clearinghouse if the clearinghouse was
updated in the future. In that case, you'd see no "DNS SERVER CLEARINGHOUSE"
entities (no such object instance). The inability to communicate to the server
could be caused by the same thing.

I assume from your PS that the customer restored his backup, and all is OK?


REMINDER FOR THOSE CONTEMPLATING YEAR 2000 TESTING ON DNS SERVER SYSTEMS:

BACK UP YOUR SYSTEM!!!!
BACK UP YOUR SYSTEM!!!!
BACK UP YOUR SYSTEM!!!!
BACK UP YOUR SYSTEM!!!!

... (replicated...)


John Saunders
DECdns Engineerin