disabling dns-o-matic updates in the linux ddclient

Follow
Avatar
Permanently deleted user

Hi,

Whenever my ISP changes my IP address I get a lapse in service.  The new IP appears on my OpenDNS dashboard, but it is greyed out, and the old one is still there in bold.  I have to manually update the info on the dashboard whenever I realise this has happened, and this fixes things.

I have read that this can be solved by "disabling DNS-o-matic updates".  Is that what I should do, and if so how do I do that on the Linux client called ddclient?

Thanks,

Alex

0

Comments

6 comments

Sort by Date Votes
  • Avatar
    rotblitz (Edited )

    ddclient does not have such an option, so you cannot disable it.  But you can send your updates from ddclient through DNS-O-Matic.

    You login with your OpenDNS credentials at DNS-O-Matic and configure your OpenDNS network as a service there.  Then you proceed with these instructions:
    http://dnsomatic.com/wiki/ddclient

    I suggest enabling SSL at the top of the configuration (ssl=yes # use ssl-support.)

    I believe you can update OpenDNS also directly, without going through DNS-O-Matic.
    https://support.opendns.com/hc/en-us/articles/227987727
    Try this:

    ##
## OpenDNS account-configuration
##
    daemon=1800
    syslog=yes
    pid=/var/run/ddclient.pid
    ssl=yes
use=web, web=myip.dnsomatic.com
server=updates.opendns.com
protocol=dyndns2
login=opendns_username
password=opendns_password
your_network_label

     

    0
    Comment actions Permalink
  • Avatar
    Permanently deleted user

    Thanks for your help.  It looks like I probably wasn't using dns-o-matic after all, given that my ddclient.conf looks very much like the one you've posted above.

    I have followed your instructions for using dns-o-matic, and I'll see how it goes.  It looks vaguely positive at the moment but I'll need to wait till my public IP address from my ISP changes before I know for sure.

    Cheers.

    PS: I switched to openDNS because BT's parental controls don't work, and I couldn't get any help online.  As always, support you get for free turns out to be vastly better than stuff you pay for! :-)

    0
    Comment actions Permalink
  • Avatar
    clardold

    I  see in the /var/log/syslog that ddclient is working.
    $ grep ddclient /var/log/syslog
    Nov 2 15:38:48 myguy ddclient[26143]: WARNING: file /var/cache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''
    Nov 2 15:38:51 myguy ddclient[26143]: SUCCESS: updating Kindle_Fire: good: IP address set to 73.15.40.123

    How can I see when it updates on the OpenDNS dashboard? Do I just assume that if my logs are good, I'm done?
    I only have a free personal account, so I don't have audit logs.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    If you go through DNS-O-Matic, then you can check the log for each service at DNS-O-Matic to ensure the update took effect.  Else you can visit the OpenDNS dashboard after the update to see if your network shows the new IP address.

    0
    Comment actions Permalink
  • Avatar
    clardold

    If I log in at https://www.dnsomatic.com/, it doesn't seem that I have any services there.
    I can't check to see if my new IP is listed, because I changed it manually at opendns before installing ddclient.

    sudo systemctl status ddclient.service

    ● ddclient.service - LSB: Update dynamic domain name service entries
    Loaded: loaded (/etc/init.d/ddclient; generated; vendor preset: enabled)
    Active: active (running) since Tue 2019-11-05 16:01:18 PST; 2h 56min ago
    Docs: man:systemd-sysv-generator(8)
    Process: 546 ExecStart=/etc/init.d/ddclient start (code=exited, status=0/SUCCESS)
    Tasks: 1 (limit: 4915)
    CGroup: /system.slice/ddclient.service
    └─666 ddclient - sleeping for 200 seconds

    Nov 05 16:01:16 piaware systemd[1]: Starting LSB: Update dynamic domain name service entries...
    Nov 05 16:01:18 piaware systemd[1]: Started LSB: Update dynamic domain name service entries.
    Nov 05 16:01:18 piaware ddclient[674]: WARNING: cannot connect to myip.dnsomatic.com:80 socket: IO::Socket::INET: Bad hostname 'myip.dnsomatic.com'
    pi@piaware:~ $ ping myip.dnsomatic.com
    PING myip.dnsomatic.com (146.112.255.205) 56(84) bytes of data.
    64 bytes from 146.112.255.205 (146.112.255.205): icmp_seq=1 ttl=55 time=41.6 ms

    That doesn't look as happy as it did yesterday.  I rebooted for other reasons this afternoon.
    Nov 5 16:01:10 piaware kernel: [ 0.000000] Booting Linux on physical CPU 0x0
    Maybe the network wasn't actually up by the time ddclient started running.
    Nov 5 16:01:18 piaware dhclient[703]: DHCPACK of [...]
    appears about 20 lines after the ddclient lines.


    0
    Comment actions Permalink
  • Avatar
    rotblitz

    I do not understand why this should work if you go through/to DNS-O-Matic but have no service defined there.  And as I said above 3 years ago, you do not need to go through DNS-O-Matic but can go directly to OpenDNS.

    And yes, your log entries indicate network issues, for example myip.dnsomatic.com could not be resolved via DNS: Bad hostname 'myip.dnsomatic.com'

    Whatever, it may be best to ask in a ddclient or Linux support forum.  It doesn't look like your problem has to do with OpenDNS.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post