Replies to This Discussion

Permalink Reply by Mikael Lind on August 30, 2010 at 9:16am

Sometimes DNS cache can create issues when you switch servers. The old information can stay in cache for quite some time. It also happens that the DNS update from the tunnel server to the DNS server fails. To make sure that isn't the case you can reconnect the tunnel, which will reinitialize the update.

• ▶ Reply

Permalink Reply by Salvatore Scata' on August 30, 2010 at 9:47am

Thanks for your reply Mikael,

If I understand you mean to keep disconnect and reconnect the gw6c client until the statically assigned ipaddress of the tunnel interface is the same of the address resolution obtained pinging the broker.

Is this correct?

The other question is open: is some other host replying to the old address?

Regards
Salvatore
Regards

• ▶ Reply

Permalink Reply by Mikael Lind on August 30, 2010 at 1:06pm

What I meant was that it some times is necessary to reconnect to get the DNS update to work. If you always connect to the same server it is less of an issue but if you keep switching the update sometimes fails and you will be stuck with the old address until you reconnect.

• ▶ Reply

Permalink Reply by Salvatore Scata' on August 31, 2010 at 1:16am

Yes, I understand,

With my previous reply I was in fact thinking to a soluion for a non attended host. In this case there is no operator which may disconnect and reconnect but the overall procedute has to be done automatically.

Thanks

• ▶ Reply