Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] dynamic DNS delay

discuss AT

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] dynamic DNS delay

Chronological Thread  
  • From: Christoph Harder <c_harder AT>
  • To: discuss AT
  • Subject: Re: [opennic-discuss] dynamic DNS delay
  • Date: Wed, 13 Jan 2021 18:37:53 +0100

Hello Eric,

thank you for your fast reply.

Today I checked again, even when I open the link to update my dynamic dns entry in my browser the
IP doesn't seem to change
(<DOMAIN>?user=<USER>&auth=<TOKEN> of
course with DOMAIN, USER and TOKEN replaced by the appropriate values).

The site http://be.libre/ showed a different IP for the dynamic dns entry.
My router as well as multiple "what is my ip"-sites showed a different ip
from the one that be.libre showed.

On be.libre I tried to disable the site and enable it again. However now it
is not showing any ip address at all on be.libre

In addition to this, when I try to open the link to update the ip I get a "Not
Found The requested URL was not found on this server.", if I remenber correctly
in the past when I set this up I did get another reply.

I tried to use nslookup and the dns servers and,
both returned the wrong address and if I'm not mistaken nslookup doesn't
cache if a server is given.

Hope you have any suggestions what the problem might be.

Best regards,

Am 05.01.2021 um 15:14 schrieb Erich Eckner:
On Tue, 5 Jan 2021, Christoph Harder wrote:

Hello everybody,

Hi Christoph,

I hope this is the correct list for this topic. I'm using .dyn-addresses for
multiple places which have non-static addresses.
However even when updating the address regularly (every 10 Minutes) the
address update sometimes takes a long time (sometimes hours, sometimes days).
Is this related to the way the updates are handled or does the dns
propagation cause this delay?

The old adress will stay valid in (caching) resolvers, until the TTL expires.

Is there any way to improve the time that is required between an update and
using this address to access the correct ip?

lower the TTL to a reasonable level: too low, and you won't use the cache
much, but ask the authoritative server more (which is slower); too high, and
you will see the behaviour, which you currently notice.

I would suggest a value of several 5 minutes (depending on how long you're willing to
wait for an updated ip to get "through").

btw: this is a general dns "issue", not really related to opennic - but I'm
still happy to help :-)

Best regards,


> --------
> You are a member of the OpenNIC Discuss list.
> You may unsubscribe by emailing discuss-unsubscribe AT

Archive powered by MHonArc 2.6.19.

Top of Page