DDNS breaks after reboot on micro-instance

[Christian Roess]

After a reboot of a TK-core micro-instance with elastic IP, i can not connect via DDNS-Name to the server. A manual hubdns-update doesn't help. A hubdns-info shows the correct IP associated.

Any suggestions?

[Jeremy Davis (jedmeister)]

Has this resolved itself? Or do we need to escalate it?

Could you connect to your appliance via the elastic IP? My (limited) understanding is that the elastic IP remains static and should always point to the real IP of the appliance, thus making DNS much more reliable (because the elastic IP remains static, even if the real IP changes).

[Christian Roess (christian-roess)]

No it has not resolved itself.

This happens also, if an elastic IP is activated.

It seems that the DDNS Client can not update the settings immediatly AND the DNS points to another IP (nirvana) if the instance was down.

Best regards

Am Jan 30, 2012, KW 5 um 2:51 PM schrieb JedMeister:

> Has this resolved itself? Or do we need to escalate it?
>
> Could you connect to your appliance via the elastic IP? My (limited)
> understanding is that the elastic IP remains static and should always
> point to the real IP of the appliance, thus making DNS much more
> reliable (because the elastic IP remains static, even if the real IP
> changes).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/917142
>
> Title:
> DDNS breaks after reboot on micro-instance
>
> Status in TurnKey Linux:
> New
>
> Bug description:
> After a reboot of a TK-core micro-instance with elastic IP, i can not
> connect via DDNS-Name to the server. A manual hubdns-update doesn't
> help. A hubdns-info shows the correct IP associated.
>
> Any suggestions?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/turnkeylinux/+bug/917142/+subscriptions