I am not laughing ..:)


Peter van Oostrum 
Tel. +31 (0)186  707812 
Fax +31 (0)186  61 641505 
Mobile +3106-52322503 

http://www.dylangroup.com 
PO. Box 1208 
3260 AE  Oud-Beijerland 
The Netherlands 

================================================================== 

NOTICE - This communication may contain confidential and privileged
information that is for the sole use of 
the intended recipient. Any viewing, copying or distribution of, or
reliance on this message by unintended 
recipients is strictly prohibited. If you have received this message in
error, please notify us immediately by 
replying to the message and deleting it from your computer. Thank you. 
================================================================== 

 

-----Oorspronkelijk bericht-----
Van: [email protected]
[mailto:[EMAIL PROTECTED] Namens Dave Stewart
Verzonden: dinsdag 25 november 2008 20:41
Aan: InterMapper Discussion
Onderwerp: Re: [IM-Talk] dns resolve got really slow

On Nov 25, 2008, at 3:00 AM, William W. Fisher offered:

> debbie Fligor wrote:
>> i didn't track when this happened to know if it coincides with a
>> specific intermapper release, a change to our DNS here or something
>> else.  but it used to be when I put in a device by IP and set "update
>> name from ip" that it would pickup it's name in under a minute or  
>> if I
>> hit cmd-k for reprobe.  Now when I use that setting it can take more
>> than 30 minutes (after that I get busy and get back to it some  
>> hours or
>> days later).
>
> InterMapper's timer for updating each device's DNS is tied to the  
> TTL of the associated DNS record on your DNS server
> (min. 2 minutes, max 24 hours). I wonder if the DNS TTL's have  
> changed? If the TTL is low enough, reprobing the device
> or using a sub-minute poll interval can make the DNS update appear  
> nearly instantaneous. That's just a side effect
> though; the reprobe command does not reset the timer for DNS.


That's interesting. I wouldn't expect to have to change the DNS TTL to  
make map changes, so there must be a way to reset Intermapper - force  
it to reload zone. Would it take a restart of Intermapper to do this?  
Is there a more pleasant way?



Dave Stewart
Aqua~Flo Supply (Goleta CA)
dstewart at aquaflo dot com

Murphy's Law:
     Anything that can go wrong, will.
Murphy's Corollary:
     Left to themselves, things tend to go from bad to worse.
Murphy's Constant:
     Matter will be damaged in direct proportion to its value.
Quantized review of Murphy's Law:
     Everything goes wrong all at once.
O'Tooles Commentary:
     Murphy was an optimist.

____________________________________________________________________
List archives: 
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]

____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]

Reply via email to