Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Looks like ddclient is not updating the DNS server unless I issue a manual "ddclient -force" command.
In the screen capture below, you can see that the current external IP is 189.47.93.111 and the previous one was 200.148.49.246
By the ddclient cache file, I think it detected the new IP, but, the dns server 208.76.61.3 still answer with the previous one, until a "ddclient -force" is issued.
What is wrong in my config file ?
Why ddclient is not updating the dns server right away but only after a force command ?
What I have to do the get the dns server updated at boot time without a manual "ddclient -force" commmand ?
Please, note that machine is online about 34min. No updates commands of any kind were issue until them, except the ddclient start at boot time, so, there is not any kinf of abuse on dns server that can cause an update block.
Code:
root@hahasiah:~# uptime
12:28:31 up 34 min, 4 users, load average: 0,16, 0,17, 0,26
root@hahasiah:~# systemctl status ddclient.service
● ddclient.service - LSB: Update dynamic domain name service entries
Loaded: loaded (/etc/init.d/ddclient; generated)
Active: active (running) since Mon 2018-05-21 12:27:20 -03; 1min 29s ago
Docs: man:systemd-sysv-generator(8)
Process: 8335 ExecStop=/etc/init.d/ddclient stop (code=exited, status=0/SUCCESS)
Process: 8341 ExecStart=/etc/init.d/ddclient start (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/ddclient.service
└─8348 ddclient - connecting to checkip.dyndns.com port 80
mai 21 12:27:20 hahasiah systemd[1]: Starting LSB: Update dynamic domain name service entries...
mai 21 12:27:20 hahasiah systemd[1]: Started LSB: Update dynamic domain name service entries.
root@hahasiah:~# systemctl restart ddclient.service
root@hahasiah:~# dig @208.76.61.3 +short rozsas.homelinux.net
200.148.49.246
root@hahasiah:~# cat /var/cache/ddclient/ddclient.cache
## ddclient-3.8.3
## last updated at Sat May 19 10:25:54 2018 (1526736354)
atime=0,backupmx=0,custom=0,host=rozsas.homelinux.net,ip=189.47.93.111,mtime=1526736245,mx=,script=/nic/update,static=0,status=good,warned-min-error-interval=0,warned-min-interval=0,wildcard=0,wtime=30 rozsas.homelinux.net
root@hahasiah:~# ddclient -force
SUCCESS: updating rozsas.homelinux.net: good: IP address set to 189.47.93.111
root@hahasiah:~# dig @208.76.61.3 +short rozsas.homelinux.net
189.47.93.111
Your configuration file shows you are set to update DDNS every 16 minutes. However, that should also happen first at boot time. Which distro are you on, including version? There might be some information in the relevant logs, but those vary a little per distro.
You could also try running ddclient directly and see what it complains about, but it would be best to check the logs first.
Your configuration file shows you are set to update DDNS every 16 minutes. However, that should also happen first at boot time. Which distro are you on, including version? There might be some information in the relevant logs, but those vary a little per distro.
I am running Ubuntu 18.04, installed from zero, it was not an update over the previous version.
I've tried to run in foreground as you suggested. No warnings, no errors, nothing. Just the blinking cursor in the next line.
I left it running for about 40 min in foreground before I've interrupted it.
Code:
root@hahasiah:~# dig @208.76.61.3 +short rozsas.homelinux.net
191.254.167.229
root@hahasiah:~# cat /var/cache/ddclient/ddclient.cache
## ddclient-3.8.3
## last updated at Mon May 21 13:29:04 2018 (1526920144)
atime=0,backupmx=0,custom=0,host=rozsas.homelinux.net,ip=189.47.93.111,mtime=1526916557,mx=,script=/nic/update,static=0,status=,warned-min-error-interval=0,warned-min-interval=0,wildcard=0,wtime=30 rozsas.homelinux.net
root@hahasiah:~# systemctl stop ddclient.service
root@hahasiah:~# ddclient -foreground -file /etc/ddclient.conf
^C
root@hahasiah:~# dig @208.76.61.3 +short rozsas.homelinux.net
191.254.167.229
root@hahasiah:~# ddclient -force
SUCCESS: updating rozsas.homelinux.net: good: IP address set to 189.47.93.111
root@hahasiah:~# dig @208.76.61.3 +short rozsas.homelinux.net
189.47.93.111
root@hahasiah:~#
As you can see, the cache already has the new IP but not the DNS server (208.76.61.3).
Immediately after I ran "ddclient -force", the dns server shows the new, updated IP.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.