You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All DNS lookups (see above) show the old IP (80.XX.XX.YY) for the host REDACT.ED
Butddns-updaterbelieves (see start-up logs above) it has (set?) the correct IP 80.XX.XX.XX for the host REDACT.ED
Can someone maybe explain how/why ddns-updater has wrong IP information and isn't updating the domain/record?
I tried to change the RESOLVER_ADDRESS but couldn't find a clear answer. It seems (for me) ddns-updater is somehow caching the IP, instead of live requesting …(?)
I've also seen #891, discussion #894. Also #339, which I think does the same at Docker for RESOLVER_ADDRESS …
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🙋♂️️ Hi, can someone help me to find the cause (and resolution) for a strange DNS/IP problem?
Insights/Background
ddns-updater
:v2.9.0
(@NixOS)ipv4
only)@
RESOLVER_ADDRESS
👉️ start-up logs
Logs
Status
REDACT.ED
netcup
80.XX.XX.XX
80.XX.XX.YY
REDACT.ED
(as@
)👉️ DNS lookups
Local
[sokai@HOST:~]$ nslookup REDACT.ED. Server: 10.1.0.1 Address: 10.1.0.1#53 Non-authoritative answer: Name: REDACT.ED Address: 80.XX.XX.YY
Authorative
[sokai@HOST:~]$ nslookup REDACT.ED. 46.38.225.225 Server: 46.38.225.225 Address: 46.38.225.225#53 Non-authoritative answer: Name: REDACT.ED Address: 80.XX.XX.YY
3rd party
Problem
80.XX.XX.YY
) for the hostREDACT.ED
ddns-updater
believes (see start-up logs above) it has (set?) the correct IP80.XX.XX.XX
for the hostREDACT.ED
Can someone maybe explain how/why
ddns-updater
has wrong IP information and isn't updating the domain/record?I tried to change the
RESOLVER_ADDRESS
but couldn't find a clear answer. It seems (for me)ddns-updater
is somehow caching the IP, instead of live requesting …(?)I've also seen #891, discussion #894. Also #339, which I think does the same at Docker for
RESOLVER_ADDRESS
…KR
Beta Was this translation helpful? Give feedback.
All reactions