Service keeps using the same IP address

[Guest]

We have an application that uses .Net remoting to allow remote servers to
connect to a master server to synchronize data. The format of the url we use
to the master server looks like “tcp://master.company.com/wilson.serverâ€. If
the IP address of the master server changes the remote server keep using to
old IP address until they are restarted.

The A rescored in the DNS server has a Time To Live setting of 1 hour. Why
does the remote service have to be restarted before it starts using the new
IP address? Is there anything I can do force remoting to refresh it’s local
IP address cache?

 

[Kevin Spencer]

Do yourself a favor and use the IP address in the uri. The problem you are
experiencing is due to the nature of DNS. DNS records are cached with an
expiration datetime, and will only be refreshed with they expire, by
querying a DSN server. This does not, however, guarantee that the DNS server
has refreshed *its* cached record. These changes can take days to propogate.

--
HTH,

Kevin Spencer
Microsoft MVP
Software Composer

A watched clock never boils.

 

[Guest]

Kevin,

Thanks for responding. I have used nslooup on the remote server to make
sure the DNS server it is using has the correct IP address. I have also
checked the time to live value of the DNS record to verify that it is set for
24 hours. We changed the IP address four days ago but the remote service
keeps using the old address. I think there is something else going on. I am
using Activator.GetObject to create the remote object. Does the Activator
class keep a cash of some kind?