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

Conference noted::seal

Title:SEAL
Moderator:GALVIA::SMITH
Created:Mon Mar 21 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1989
Total number of notes:8209

1768.0. "Generic Proxy, information cached, source changed?" by TENNIS::KAM (AltaVista Software 714/261-4133 DTN 535.4133) Tue Feb 04 1997 23:07

    A customer created a Generic Proxy to gateway.compuserve.com, I think
    they are relaying their CompuServe Mail to their local Company.  
    
    It appears that when they made this Host entry and Added it, the name
    server on the Firewall went out, got the IP address of
    gateway.compuserve.com, and cached it locally.  It appears that
    compuserve changed this value and all hell broke loose.
    
    The customer deleted the proxy and re-created it and everything started
    working again.  Is there a way on the firewall NOT to cache this value
    forever?
    
    On the DNS Defaults screen are the following:
    
       Postmaster 
       Serial Number
       Refresh Time
       Retry Time
       Expire Time
       Minimum Time to Live
    
    I assume that these Values Control how the Firewall's DNS values are
    controlled?
    
    One thing I can't understand is why CompuServe changes the
    gateway.compuserve.com periodically.
    
    
    	Regards,
    
T.RTitleUserPersonal
Name
DateLines
1768.1QUICHE::PITTAlph a ha is better than no VAX!Wed Feb 05 1997 08:537
    This is documented elsewhere in here, and also the bug that if you
    remove it, it leaves the IP address in one of the files ...
    
    I hope this is going to be changed in the future, since it is quite a
    pain in a number of places ...
    
    T
1768.2TENNIS::KAMAltaVista Software 714/261-4133 DTN 535.4133Wed Feb 05 1997 11:408
    I should have mentioned that this is the AV FW for NT, was the file 
    issue associated with the DUNIX version?  Removing this in the NT 
    and adding it back corrected the problem, it appears.
    
    I'll do some searching to see what the previous threads were.
    
    	Regards,