<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ddclient sleep 1200 but getting HTTP / 1.1 429 Too Many Requests e in OpenDNS</title>
    <link>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5374815#M18792</link>
    <description>&lt;P&gt;After increasing the delay/sleep (decreasing the update frequency), waiting 48 hours (48 hourly, ddclient daemon=3600, updates), and then reviewing the log, I see that I received two "429 Too Many Requests" warning messages.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since this is a warning (not a fatal error) and the next update 1 hour later succeeds, I am going to consider this issue resolved with a work-around.&lt;/P&gt;&lt;P&gt;I encourage OpenDNS to review the capacity of their dynamic IP and name server infrastructure to allow a more consistent response capability to avoid "429 Too Many Requests" errors. Asking all customers to reduce their load on the infrastructure will only be a bandaid since some customers will follow the recommendation and others will not. Ideally, to maintain good security service OpenDNS needs to provide consistent dynamic IP update capacity. With these observed results, my network is protected, on average, for 23 hours out of 24. A bit more risk than I'd like. But I'm taking advantage of a free service, so perhaps I shouldn't complain too much.&lt;/P&gt;</description>
    <pubDate>Thu, 05 Mar 2026 17:16:19 GMT</pubDate>
    <dc:creator>geoperkins</dc:creator>
    <dc:date>2026-03-05T17:16:19Z</dc:date>
    <item>
      <title>ddclient sleep 1200 but getting HTTP / 1.1 429 Too Many Requests error</title>
      <link>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5373927#M18779</link>
      <description>&lt;P&gt;I am getting intermittent errors when re-registering my IP to OpenDNS. Even when the IP is not changed I still need to check in case my ISP DHCP lease may expire and be reassigned. So I have ddclient (most current version, using a docker latest image) running with a sleep set to 1200 seconds (20 minutes). Documentation says minimum sleep is 300 seconds, so I assume 1200 would be safe and not saturate the myip.dnsomatic.com service?&lt;/P&gt;&lt;P&gt;Error messages:&lt;/P&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;PRE&gt;reply: HTTP/1.1 429 Too Many Requests&lt;BR /&gt;Server: nginx&lt;BR /&gt;Content-Type: text/html&lt;BR /&gt;Content-Length: 162&lt;BR /&gt;Connection: keep-alive&lt;BR /&gt;Strict-Transport-Security: max-age=15768000; includeSubDomains&lt;BR /&gt;429 Too Many Requests&lt;BR /&gt;did not find an IPv4 or IPv6 address&lt;BR /&gt;unable to determine IP address&lt;/PRE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I enabled debug and verbose in the ddclient syslog to catch the error (see below).&lt;/P&gt;&lt;P&gt;I checked using a Chrome web browser and the myip.dnsomatic.com URL is correctly responding with my IP at the moment.&lt;/P&gt;&lt;P&gt;Anyone at OpenDNS able to tell me if your servers will reject 1200 second requests? Should I increase the sleep interval or use a different URL?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;PRE&gt;ddclient  | DEBUG:   &amp;gt; sleep 1200
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; proxy    = &amp;lt;undefined&amp;gt;
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; protocol = https
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; server   = myip.dnsomatic.com
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; url      = 
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]&amp;gt; curl config:
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  silent
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  include
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  user-agent="ddclient/4.0.0"
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  connect-timeout=120
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  max-time=120
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  request=GET
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  url="https://myip.dnsomatic.com/"
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; CURL: curl
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; CURL Tempfile: /tmp/ddclient_lMzTqtQDYp
ddclient  | === opt ====
ddclient  | opt{cache}                           : /run/ddclient-cache/ddclient.cache
ddclient  | opt{file}                            : /config/ddclient.conf
ddclient  | opt{foreground}                      : 1
ddclient  | opt{fw-banlocal}                     : CODE(0x7fff31875b30)
ddclient  | opt{help}                            : CODE(0x7fff31411f50)
ddclient  | opt{if-skip}                         : CODE(0x7fff31875b30)
ddclient  | opt{list-devices}                    : CODE(0x7fff31875c38)
ddclient  | opt{list-protocols}                  : CODE(0x7fff31875d40)
ddclient  | opt{list-web-services}               : CODE(0x7fff31875e18)
ddclient  | opt{quiet}                           : 0
ddclient  | opt{version}                         : CODE(0x7fff31875f68)
ddclient  | === globals ====
ddclient  | globals{cache}                       : /run/ddclient-cache/ddclient.cache
ddclient  | globals{daemon}                      : 1200
ddclient  | globals{debug}                       : 1
ddclient  | globals{file}                        : /config/ddclient.conf
ddclient  | globals{foreground}                  : 1
ddclient  | globals{pid}                         : /var/run/ddclient/ddclient.pid
ddclient  | globals{quiet}                       : 0
ddclient  | globals{ssl}                         : 1
ddclient  | globals{syslog}                      : 1
ddclient  | globals{use}                         : web
ddclient  | globals{verbose}                     : 1
ddclient  | globals{web}                         : https://myip.dnsomatic.com
ddclient  | === config ====
ddclient  | config{all.dnsomatic.com}{daemon}    : 1200
ddclient  | config{all.dnsomatic.com}{debug}     : 1
ddclient  | config{all.dnsomatic.com}{host}      : all.dnsomatic.com
ddclient  | config{all.dnsomatic.com}{login}     : &amp;lt;redacted&amp;gt;
ddclient  | config{all.dnsomatic.com}{password}  : &amp;lt;redacted&amp;gt;
ddclient  | config{all.dnsomatic.com}{pid}       : /var/run/ddclient/ddclient.pid
ddclient  | config{all.dnsomatic.com}{protocol}  : dyndns2
ddclient  | config{all.dnsomatic.com}{quiet}     : 0
ddclient  | config{all.dnsomatic.com}{server}    : updates.dnsomatic.com:443
ddclient  | config{all.dnsomatic.com}{ssl}       : 1
ddclient  | config{all.dnsomatic.com}{syslog}    : 1
ddclient  | config{all.dnsomatic.com}{use}       : web
ddclient  | config{all.dnsomatic.com}{verbose}   : 1
ddclient  | config{all.dnsomatic.com}{web}       : https://myip.dnsomatic.com
ddclient  | === recap ====
ddclient  | recap{all.dnsomatic.com}{atime}      : 1772398263
ddclient  | recap{all.dnsomatic.com}{backupmx}   : 0
ddclient  | recap{all.dnsomatic.com}{host}       : all.dnsomatic.com
ddclient  | recap{all.dnsomatic.com}{ipv4}       : 24.183.35.241
ddclient  | recap{all.dnsomatic.com}{mtime}      : 1772398263
ddclient  | recap{all.dnsomatic.com}{status-ipv4} : good
ddclient  | recap{all.dnsomatic.com}{wildcard}   : 0
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]&amp;gt; reply:
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  HTTP/1.1 200 OK
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Server: nginx
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Date: Mon, 02 Mar 2026 17:51:25 GMT
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Content-Type: text/plain; charset=utf-8
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Content-Length: 13
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Connection: keep-alive
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Strict-Transport-Security: max-age=15768000; includeSubDomains
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  X-Frame-Options: deny
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  X-XSS-Protection: 1; mode=block
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  X-Content-Type-Options: nosniff
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  24.183.35.241
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com]&amp;gt; found IP address: 24.183.35.241
ddclient  | SUCCESS: [all.dnsomatic.com]&amp;gt; skipped update because IPv4 address is already set to 24.183.35.241
ddclient  | DEBUG:   &amp;gt; sleep 1200
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; proxy    = &amp;lt;undefined&amp;gt;
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; protocol = https
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; server   = myip.dnsomatic.com
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; url      = 
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]&amp;gt; curl config:
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  silent
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  include
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  user-agent="ddclient/4.0.0"
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  connect-timeout=120
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  max-time=120
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  request=GET
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  url="https://myip.dnsomatic.com/"
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; CURL: curl
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; CURL Tempfile: /tmp/ddclient_7R1vdd8Yvl
ddclient  | === opt ====
ddclient  | opt{cache}                           : /run/ddclient-cache/ddclient.cache
ddclient  | opt{file}                            : /config/ddclient.conf
ddclient  | opt{foreground}                      : 1
ddclient  | opt{fw-banlocal}                     : CODE(0x7fff31875b30)
ddclient  | opt{help}                            : CODE(0x7fff31411f50)
ddclient  | opt{if-skip}                         : CODE(0x7fff31875b30)
ddclient  | opt{list-devices}                    : CODE(0x7fff31875c38)
ddclient  | opt{list-protocols}                  : CODE(0x7fff31875d40)
ddclient  | opt{list-web-services}               : CODE(0x7fff31875e18)
ddclient  | opt{quiet}                           : 0
ddclient  | opt{version}                         : CODE(0x7fff31875f68)
ddclient  | === globals ====
ddclient  | globals{cache}                       : /run/ddclient-cache/ddclient.cache
ddclient  | globals{daemon}                      : 1200
ddclient  | globals{debug}                       : 1
ddclient  | globals{file}                        : /config/ddclient.conf
ddclient  | globals{foreground}                  : 1
ddclient  | globals{pid}                         : /var/run/ddclient/ddclient.pid
ddclient  | globals{quiet}                       : 0
ddclient  | globals{ssl}                         : 1
ddclient  | globals{syslog}                      : 1
ddclient  | globals{use}                         : web
ddclient  | globals{verbose}                     : 1
ddclient  | globals{web}                         : https://myip.dnsomatic.com
ddclient  | === config ====
ddclient  | config{all.dnsomatic.com}{daemon}    : 1200
ddclient  | config{all.dnsomatic.com}{debug}     : 1
ddclient  | config{all.dnsomatic.com}{host}      : all.dnsomatic.com
ddclient  | config{all.dnsomatic.com}{login}     : &amp;lt;redacted&amp;gt;
ddclient  | config{all.dnsomatic.com}{password}  : &amp;lt;redacted&amp;gt;
ddclient  | config{all.dnsomatic.com}{pid}       : /var/run/ddclient/ddclient.pid
ddclient  | config{all.dnsomatic.com}{protocol}  : dyndns2
ddclient  | config{all.dnsomatic.com}{quiet}     : 0
ddclient  | config{all.dnsomatic.com}{server}    : updates.dnsomatic.com:443
ddclient  | config{all.dnsomatic.com}{ssl}       : 1
ddclient  | config{all.dnsomatic.com}{syslog}    : 1
ddclient  | config{all.dnsomatic.com}{use}       : web
ddclient  | config{all.dnsomatic.com}{verbose}   : 1
ddclient  | config{all.dnsomatic.com}{web}       : https://myip.dnsomatic.com
ddclient  | === recap ====
ddclient  | recap{all.dnsomatic.com}{atime}      : 1772398263
ddclient  | recap{all.dnsomatic.com}{backupmx}   : 0
ddclient  | recap{all.dnsomatic.com}{host}       : all.dnsomatic.com
ddclient  | recap{all.dnsomatic.com}{ipv4}       : 24.183.35.241
ddclient  | recap{all.dnsomatic.com}{mtime}      : 1772398263
ddclient  | recap{all.dnsomatic.com}{status-ipv4} : good
ddclient  | recap{all.dnsomatic.com}{wildcard}   : 0
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]&amp;gt; reply:
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  HTTP/1.1 200 OK
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Server: nginx
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Date: Mon, 02 Mar 2026 18:11:25 GMT
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Content-Type: text/plain; charset=utf-8
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Content-Length: 13
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Connection: keep-alive
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Strict-Transport-Security: max-age=15768000; includeSubDomains
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  X-Frame-Options: deny
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  X-XSS-Protection: 1; mode=block
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  X-Content-Type-Options: nosniff
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  24.183.35.241
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com]&amp;gt; found IP address: 24.183.35.241
ddclient  | SUCCESS: [all.dnsomatic.com]&amp;gt; skipped update because IPv4 address is already set to 24.183.35.241
ddclient  | DEBUG:   &amp;gt; sleep 1200
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; proxy    = &amp;lt;undefined&amp;gt;
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; protocol = https
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; server   = myip.dnsomatic.com
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; url      = 
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]&amp;gt; curl config:
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  silent
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  include
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  user-agent="ddclient/4.0.0"
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  connect-timeout=120
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  max-time=120
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  request=GET
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][REQUEST]  url="https://myip.dnsomatic.com/"
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; CURL: curl
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request]&amp;gt; CURL Tempfile: /tmp/ddclient_Ce2iEJ_1_d
ddclient  | === opt ====
ddclient  | opt{cache}                           : /run/ddclient-cache/ddclient.cache
ddclient  | opt{file}                            : /config/ddclient.conf
ddclient  | opt{foreground}                      : 1
ddclient  | opt{fw-banlocal}                     : CODE(0x7fff31875b30)
ddclient  | opt{help}                            : CODE(0x7fff31411f50)
ddclient  | opt{if-skip}                         : CODE(0x7fff31875b30)
ddclient  | opt{list-devices}                    : CODE(0x7fff31875c38)
ddclient  | opt{list-protocols}                  : CODE(0x7fff31875d40)
ddclient  | opt{list-web-services}               : CODE(0x7fff31875e18)
ddclient  | opt{quiet}                           : 0
ddclient  | opt{version}                         : CODE(0x7fff31875f68)
ddclient  | === globals ====
ddclient  | globals{cache}                       : /run/ddclient-cache/ddclient.cache
ddclient  | globals{daemon}                      : 1200
ddclient  | globals{debug}                       : 1
ddclient  | globals{file}                        : /config/ddclient.conf
ddclient  | globals{foreground}                  : 1
ddclient  | globals{pid}                         : /var/run/ddclient/ddclient.pid
ddclient  | globals{quiet}                       : 0
ddclient  | globals{ssl}                         : 1
ddclient  | globals{syslog}                      : 1
ddclient  | globals{use}                         : web
ddclient  | globals{verbose}                     : 1
ddclient  | globals{web}                         : https://myip.dnsomatic.com
ddclient  | === config ====
ddclient  | config{all.dnsomatic.com}{daemon}    : 1200
ddclient  | config{all.dnsomatic.com}{debug}     : 1
ddclient  | config{all.dnsomatic.com}{host}      : all.dnsomatic.com
ddclient  | config{all.dnsomatic.com}{login}     : &amp;lt;redacted&amp;gt;
ddclient  | config{all.dnsomatic.com}{password}  : &amp;lt;redacted&amp;gt;
ddclient  | config{all.dnsomatic.com}{pid}       : /var/run/ddclient/ddclient.pid
ddclient  | config{all.dnsomatic.com}{protocol}  : dyndns2
ddclient  | config{all.dnsomatic.com}{quiet}     : 0
ddclient  | config{all.dnsomatic.com}{server}    : updates.dnsomatic.com:443
ddclient  | config{all.dnsomatic.com}{ssl}       : 1
ddclient  | config{all.dnsomatic.com}{syslog}    : 1
ddclient  | config{all.dnsomatic.com}{use}       : web
ddclient  | config{all.dnsomatic.com}{verbose}   : 1
ddclient  | config{all.dnsomatic.com}{web}       : https://myip.dnsomatic.com
ddclient  | === recap ====
ddclient  | recap{all.dnsomatic.com}{atime}      : 1772398263
ddclient  | recap{all.dnsomatic.com}{backupmx}   : 0
ddclient  | recap{all.dnsomatic.com}{host}       : all.dnsomatic.com
ddclient  | recap{all.dnsomatic.com}{ipv4}       : 24.183.35.241
ddclient  | recap{all.dnsomatic.com}{mtime}      : 1772398263
ddclient  | recap{all.dnsomatic.com}{status-ipv4} : good
ddclient  | recap{all.dnsomatic.com}{wildcard}   : 0
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]&amp;gt; reply:
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  HTTP/1.1 429 Too Many Requests
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Server: nginx
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Date: Mon, 02 Mar 2026 18:31:25 GMT
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Content-Type: text/html
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Content-Length: 162
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Connection: keep-alive
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  Strict-Transport-Security: max-age=15768000; includeSubDomains
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  &amp;lt;html&amp;gt;
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  &amp;lt;head&amp;gt;&amp;lt;title&amp;gt;429 Too Many Requests&amp;lt;/title&amp;gt;&amp;lt;/head&amp;gt;
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  &amp;lt;body&amp;gt;
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  &amp;lt;center&amp;gt;&amp;lt;h1&amp;gt;429 Too Many Requests&amp;lt;/h1&amp;gt;&amp;lt;/center&amp;gt;
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  &amp;lt;hr&amp;gt;&amp;lt;center&amp;gt;nginx&amp;lt;/center&amp;gt;
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  &amp;lt;/body&amp;gt;
ddclient  | DEBUG:   [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com][HTTP request][RESPONSE]  &amp;lt;/html&amp;gt;
ddclient  | WARNING: [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com]&amp;gt; 429 Too Many Requests
ddclient  | WARNING: [all.dnsomatic.com][use=web web=https://myip.dnsomatic.com]&amp;gt; did not find an IPv4 or IPv6 address
ddclient  | WARNING: [all.dnsomatic.com]&amp;gt; unable to determine IP address with strategy '--use=web'
ddclient  | WARNING: [all.dnsomatic.com]&amp;gt; unable to determine IP address
ddclient  | DEBUG:   &amp;gt; sleep 1200&lt;/PRE&gt;</description>
      <pubDate>Mon, 02 Mar 2026 20:02:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5373927#M18779</guid>
      <dc:creator>geoperkins</dc:creator>
      <dc:date>2026-03-02T20:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: ddclient sleep 1200 but getting HTTP / 1.1 429 Too Many Requests e</title>
      <link>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5373981#M18780</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;First try flushing your browsers cache and then try again.&lt;/P&gt;
&lt;P&gt;If that fails try increasing the sleep interval.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In addition, this site (&lt;A href="https://www.geeksforgeeks.org/websites-apps/429-error-causes-and-solutions/" target="_blank"&gt;https://www.geeksforgeeks.org/websites-apps/429-error-causes-and-solutions/&lt;/A&gt;) offers many different methods to troubleshoot this problem.&lt;/P&gt;
&lt;P&gt;If you have any questions please feel free to ask.&lt;/P&gt;
&lt;P&gt;Best regards,&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 00:26:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5373981#M18780</guid>
      <dc:creator>reham1</dc:creator>
      <dc:date>2026-03-03T00:26:50Z</dc:date>
    </item>
    <item>
      <title>Re: ddclient sleep 1200 but getting HTTP / 1.1 429 Too Many Requests e</title>
      <link>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5373990#M18781</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1753207"&gt;@reham1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not sure you understand the situation. Please, I apologize in advance if the following sounds patronizing, but your response makes me wonder if there is a misunderstanding: I'm posting this question on the OpenDNS forum for a Cisco-owned service, DNS-O-Matic which is part of the OpenDNS (public, free) version of the Cisco business product known as Umbrella.&lt;/P&gt;&lt;P&gt;OpenDNS hosts the DNS-O-Matic servers which echo the remote client's IP address which is then used by the ddclient service to associate the client's public IP address to the client's security filter settings in OpenDNS (by logging in and updating the public IP for&amp;nbsp; the client's network) Then, all of the systems behind that public IP use OpenDNS name servers for their DNS queries, which filter according to the client's profile (just like Cisco Umbrella, it is the same technology).&lt;/P&gt;&lt;P&gt;The app I'm using (ddclient) is an open source and popular dynamic IP management client that uses CURL on the client side of the DNS-O-Matic server application to perform the public IP query.&amp;nbsp;The ddclient is not a web browser and consequently I can't "clear the cache".&amp;nbsp; In fact, according to the documentation at&amp;nbsp;&lt;A href="https://ddclient.net/" target="_self"&gt;https://ddclient.net/&lt;/A&gt;&amp;nbsp;there is no cache or flush or similar option. You can see the HTTP result in the debug log I provided. It is not a cache problem. The IP address did not change, but the DNS-O-Matic server stopped responding because another query from my end after sleeping 1200 seconds seems to be flooding the server. Perhaps the problem is that my query, added to the thousands of queries from other customers, is what is flooding the DNS-O-Matic server. Which is why I'm reaching out to Cisco to look into the matter.&lt;/P&gt;&lt;P&gt;I'm hoping a Cisco OpenDNS employee can answer my questions or re-direct me to the correct OpenDNS forum (if this particular forum is not correct).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 01:34:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5373990#M18781</guid>
      <dc:creator>geoperkins</dc:creator>
      <dc:date>2026-03-03T01:34:33Z</dc:date>
    </item>
    <item>
      <title>Re: ddclient sleep 1200 but getting HTTP / 1.1 429 Too Many Requests e</title>
      <link>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5373992#M18782</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;DIV class="Y3BBE" data-processed="true" data-hveid="CAEQAA" data-sfc-cb="" data-sfc-cp=""&gt;The "too many requests" error on DNS-O-Matic (often error 429)&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;MARK class="HxTRcb" data-processed="true" data-sfc-cb=""&gt;usually means you have exceeded 1200 requests per 300 seconds per IP, often caused by excessive, frequent updates&lt;/MARK&gt;. To fix this, stop updating for at least 30-60 minutes, increase your device's update interval (e.g., to once a day), and check for misconfigured scripts.&lt;SPAN class="uJ19be notranslate" data-processed="true" data-sfc-cb="" data-wiz-uids="P5h0If_c,P5h0If_d"&gt;&lt;SPAN class="vKEkVd" data-processed="true" data-wiz-attrbind="class=P5h0If_b/TKHnVd" data-animation-atomic=""&gt;&lt;SPAN data-processed="true" aria-hidden="true"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BUTTON class="rBl3me IWyTpf pjvauc" tabindex="0" data-processed="true" data-hveid="CAEQAg" data-ved="2ahUKEwiSp7y8z4KTAxVyyOYEHYeSLicQye0OegQIARAC" data-wiz-attrbind="disabled=P5h0If_b/C5gNJc;aria-label=P5h0If_b/bOjMyf;class=P5h0If_b/UpSNec" aria-label="Cloudflare Community (+3) - View related links" data-icl-uuid="81edae93-1f96-450e-9c52-1435779f2e06" data-amic="true"&gt;&lt;/BUTTON&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
&lt;DIV class="Fwa2Od" data-processed="true" data-ved="2ahUKEwiSp7y8z4KTAxVyyOYEHYeSLicQ3s0SegQIARAD" data-sfc-cb="" data-animation-skip=""&gt;
&lt;DIV id="tinyMceEditor_bd0ecba169d10reham1_0" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="Y3BBE" data-processed="true" data-hveid="CAIQAA" data-sfc-cb="" data-sfc-cp=""&gt;&lt;STRONG class="Yjhzub" data-processed="true" data-sfc-cb=""&gt;Key Troubleshooting Steps:&lt;/STRONG&gt;&lt;BUTTON class="rBl3me" tabindex="0" data-processed="true" data-hveid="CAIQAQ" data-ved="2ahUKEwiSp7y8z4KTAxVyyOYEHYeSLicQye0OegQIAhAB" data-wiz-attrbind="disabled=P5h0If_k/C5gNJc;aria-label=P5h0If_k/bOjMyf;class=P5h0If_k/UpSNec" aria-label="View related links" data-icl-uuid="c814f6fd-65d1-4774-a511-5f8e43d26043" data-amic="true"&gt;&lt;/BUTTON&gt;&lt;/DIV&gt;
&lt;UL class="KsbFXc U6u95" data-processed="true" data-sfc-cb=""&gt;
&lt;LI class="dF3vjf" data-processed="true" data-hveid="CAMQAA" data-sfc-cb=""&gt;&lt;SPAN class="T286Pc" data-processed="true" data-sfc-cb="" data-sfc-cp=""&gt;&lt;STRONG class="Yjhzub" data-processed="true" data-sfc-cb=""&gt;Wait:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Stop your DDNS client/router from sending updates for 30–60 minutes to allow the rate limit to reset.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI class="dF3vjf" data-processed="true" data-hveid="CAMQAQ" data-sfc-cb=""&gt;&lt;SPAN class="T286Pc" data-processed="true" data-sfc-cb="" data-sfc-cp=""&gt;&lt;STRONG class="Yjhzub" data-processed="true" data-sfc-cb=""&gt;Reduce Update Frequency:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Configure your router or client (e.g., dd-wrt, ddclient) to check for IP changes less often. An update interval of once a day is generally sufficient.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI class="dF3vjf" data-processed="true" data-hveid="CAMQAg" data-sfc-cb=""&gt;&lt;SPAN class="T286Pc" data-processed="true" data-sfc-cb="" data-sfc-cp=""&gt;&lt;STRONG class="Yjhzub" data-processed="true" data-sfc-cb=""&gt;Check for Misconfiguration:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Ensure your device is only sending updates when the IP actually changes, rather than on a fast, repetitive timer.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI class="dF3vjf" data-processed="true" data-hveid="CAMQAw" data-sfc-cb=""&gt;&lt;SPAN class="T286Pc" data-processed="true" data-sfc-cb="" data-sfc-cp=""&gt;&lt;STRONG class="Yjhzub" data-processed="true" data-sfc-cb=""&gt;Review&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="o8j0Mc" dir="ltr" data-processed="true" data-sfc-cb=""&gt;ddclient&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Settings:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If using&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="o8j0Mc" dir="ltr" data-processed="true" data-sfc-cb=""&gt;ddclient&lt;/CODE&gt;, ensure the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="o8j0Mc" dir="ltr" data-processed="true" data-sfc-cb=""&gt;use=...&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;setting is correct and not constantly triggering updates.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI class="dF3vjf" data-processed="true" data-hveid="CAMQBA" data-sfc-cb=""&gt;&lt;SPAN class="T286Pc" data-processed="true" data-sfc-cb="" data-sfc-cp=""&gt;&lt;STRONG class="Yjhzub" data-processed="true" data-sfc-cb=""&gt;Check Logs:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Look for "DNS request timed out" or similar errors in your router's log to identify the frequency of the failed attempts.&lt;/SPAN&gt;&lt;SPAN class="uJ19be notranslate" data-processed="true" data-sfc-cb="" data-wiz-uids="P5h0If_17,P5h0If_18"&gt;&lt;SPAN class="vKEkVd" data-processed="true" data-wiz-attrbind="class=P5h0If_16/TKHnVd" data-animation-atomic=""&gt;&lt;SPAN data-processed="true" aria-hidden="true"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BUTTON class="rBl3me IWyTpf pjvauc" tabindex="0" data-processed="true" data-hveid="CAMQBQ" data-ved="2ahUKEwiSp7y8z4KTAxVyyOYEHYeSLicQye0OegQIAxAF" data-wiz-attrbind="disabled=P5h0If_16/C5gNJc;aria-label=P5h0If_16/bOjMyf;class=P5h0If_16/UpSNec" aria-label="Cloudflare Community (+4) - View related links" data-icl-uuid="5bfbd863-d895-472a-95c0-8173e18407e1" data-amic="true"&gt;&lt;/BUTTON&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN class="uJ19be notranslate" data-processed="true" data-sfc-cb="" data-wiz-uids="P5h0If_17,P5h0If_18"&gt;&lt;SPAN class="vKEkVd" data-processed="true" data-wiz-attrbind="class=P5h0If_16/TKHnVd" data-animation-atomic=""&gt;&lt;SPAN data-processed="true" aria-hidden="true"&gt;In addition which port are you using? If you are using port 443 try switching to port 80.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="uJ19be notranslate" data-processed="true" data-sfc-cb="" data-wiz-uids="P5h0If_17,P5h0If_18"&gt;&lt;SPAN class="vKEkVd" data-processed="true" data-wiz-attrbind="class=P5h0If_16/TKHnVd" data-animation-atomic=""&gt;&lt;SPAN data-processed="true" aria-hidden="true"&gt;Best regards, &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 02:03:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5373992#M18782</guid>
      <dc:creator>reham1</dc:creator>
      <dc:date>2026-03-03T02:03:47Z</dc:date>
    </item>
    <item>
      <title>Re: ddclient sleep 1200 but getting HTTP / 1.1 429 Too Many Requests e</title>
      <link>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5374221#M18783</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1753207"&gt;@reham1&lt;/a&gt;&amp;nbsp;Thank you for the reply. As I indicated in my detailed posting I have already considered all of those suggestions. You are not directly answering my specific questions, but that is partly my fault because I was not clear on each point. Let me restate the questions:&lt;/P&gt;&lt;P&gt;1. If not 1200 seconds, what Dynamic IP update interval should I configure? [Background: Default dynamic DNS timer should be more than 5 minutes (it takes up to 3-5 minutes for DNS updates to propagate across the OpenDNS (Umbrella) name server infrastructure). You suggest once per day. If my ISP changes my IP, on average, my network would be vulnerable for, on average, 12 hours. This seems risky.]&lt;/P&gt;&lt;P&gt;2. Is the&amp;nbsp;429 Too Many Requests error unique to my session, or is it reflective of all sessions for all clients? [Background: if it only represents my client's session, this is not seen in my logs; can you respond with the contents of the DNS-O-Matic log showing the connection refusal cause? If this error is due to ALL traffic from ALL clients, I respectfully submit that the DNS-O-Matic infrastructure is under-sized and needs additional resources to handle your combined free OpenDNS and business Umbrella customer base. Can you check with technical support?]&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 19:25:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5374221#M18783</guid>
      <dc:creator>geoperkins</dc:creator>
      <dc:date>2026-03-03T19:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: ddclient sleep 1200 but getting HTTP / 1.1 429 Too Many Requests e</title>
      <link>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5374275#M18784</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;OpenDNS no longer offers support for DNS-O-Matic.&lt;/P&gt;
&lt;P&gt;However, after reviewing similar issues to yours I found the following:&lt;/P&gt;
&lt;P&gt;Based on the logs provided in the file &lt;STRONG&gt;DNS-O-Matic too many requests.pdf&lt;/STRONG&gt;, here is an analysis of the issue and the steps to resolve it.&lt;/P&gt;
&lt;H3&gt;Analysis of the Problem&lt;/H3&gt;
&lt;P&gt;The logs show that &lt;CODE&gt;ddclient&lt;/CODE&gt; is performing an IP address check every &lt;STRONG&gt;1200 seconds (20 minutes)&lt;/STRONG&gt;.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;STRONG&gt;17:51:25 GMT&lt;/STRONG&gt;: Successful check (HTTP 200).&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;18:11:25 GMT&lt;/STRONG&gt;: Successful check (HTTP 200).&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;18:31:25 GMT&lt;/STRONG&gt;: Failed check (&lt;STRONG&gt;HTTP 429 Too Many Requests&lt;/STRONG&gt;).&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;The service &lt;CODE&gt;myip.dnsomatic.com&lt;/CODE&gt; has flagged the frequency of your requests as abusive or exceeding their rate limit. Even though 20 minutes seems reasonable, public IP check services often require longer intervals (typically 30 to 60 minutes) or prefer that you use local interface detection to reduce server load.&lt;/P&gt;
&lt;HR /&gt;
&lt;H3&gt;Recommended Solutions&lt;/H3&gt;
&lt;H4&gt;1. Increase the Check Interval (Daemon Delay)&lt;/H4&gt;
&lt;P&gt;The most direct fix is to increase the time between checks. DNS-O-Matic and OpenDNS generally recommend a check interval of at least 1 hour (3600 seconds) to avoid rate limiting.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Action&lt;/STRONG&gt;: Edit your&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;ddclient.conf&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;file.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Change&lt;/STRONG&gt;:
&lt;DIV class="snippet-header atm-flex atm-justify-between atm-items-center"&gt;&lt;SPAN class="code-text"&gt;conf&lt;/SPAN&gt;
&lt;DIV class="copy-code-block atm-flex atm-items-center"&gt;
&lt;DIV class="hbr_css--icon"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;SPAN class="code-text"&gt;Copy Code&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;PRE class="language-conf" tabindex="0"&gt;&lt;CODE&gt;daemon=3600
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;EM&gt;(Change from 1200 to 3600)&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;H4&gt;2. Use a Local Interface (If Not Behind NAT)&lt;/H4&gt;
&lt;P&gt;If your device has the public IP address assigned directly to its network interface (e.g., a WAN interface on a router), you should stop using the "web" method entirely. This eliminates the need to query an external server to find your IP.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Action&lt;/STRONG&gt;: Change the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;use&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;strategy in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;ddclient.conf&lt;/CODE&gt;.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Change&lt;/STRONG&gt;:
&lt;DIV class="snippet-header atm-flex atm-justify-between atm-items-center"&gt;&lt;SPAN class="code-text"&gt;conf&lt;/SPAN&gt;
&lt;DIV class="copy-code-block atm-flex atm-items-center"&gt;
&lt;DIV class="hbr_css--icon"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;SPAN class="code-text"&gt;Copy Code&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;PRE class="language-conf" tabindex="0"&gt;&lt;CODE&gt;use=if, if=eth0 
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;EM&gt;(Replace&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;eth0&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;with your actual WAN interface name)&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;H4&gt;3. Switch the Web IP Detection Service&lt;/H4&gt;
&lt;P&gt;If you must use a web-based check because you are behind a NAT/router, try using a different service that might have less restrictive limits, or rotate them. However, DNS-O-Matic prefers its own headers.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Action&lt;/STRONG&gt;: Update the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;web&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;parameter.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Example&lt;/STRONG&gt;:
&lt;DIV class="snippet-header atm-flex atm-justify-between atm-items-center"&gt;&lt;SPAN class="code-text"&gt;conf&lt;/SPAN&gt;
&lt;DIV class="copy-code-block atm-flex atm-items-center"&gt;
&lt;DIV class="hbr_css--icon"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;SPAN class="code-text"&gt;Copy Code&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;PRE class="language-conf" tabindex="0"&gt;&lt;CODE&gt;use=web, web=https://checkip.amazonaws.com/
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H4&gt;4. Ensure Only One Instance is Running&lt;/H4&gt;
&lt;P&gt;Sometimes a "Too Many Requests" error occurs because multiple instances of &lt;CODE&gt;ddclient&lt;/CODE&gt; are running accidentally, or another device on your network is hitting the same service.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Action&lt;/STRONG&gt;: Check for multiple processes:
&lt;DIV class="snippet-header atm-flex atm-justify-between atm-items-center"&gt;&lt;SPAN class="code-text"&gt;bash&lt;/SPAN&gt;
&lt;DIV class="copy-code-block atm-flex atm-items-center"&gt;
&lt;DIV class="hbr_css--icon"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;SPAN class="code-text"&gt;Copy Code&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;PRE class="language-bash" tabindex="0"&gt;&lt;CODE&gt;ps aux | grep ddclient
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;Summary of Configuration Changes&lt;/H3&gt;
&lt;P&gt;To resolve this specifically for the error shown in your logs, update your &lt;CODE&gt;/config/ddclient.conf&lt;/CODE&gt; as follows:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Set&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;daemon=3600&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(or higher).&lt;/LI&gt;
&lt;LI&gt;Ensure&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;syslog=yes&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;is set so you can monitor if the 429 error persists.&lt;/LI&gt;
&lt;LI&gt;Restart the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;ddclient&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;service after making changes.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;If you continue to receive the 429 error even after increasing the interval, you may need to wait 24 hours for your IP to be cleared from the DNS-O-Matic rate-limit blacklist.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope this helps&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2026 02:11:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5374275#M18784</guid>
      <dc:creator>reham1</dc:creator>
      <dc:date>2026-03-04T02:11:30Z</dc:date>
    </item>
    <item>
      <title>Re: ddclient sleep 1200 but getting HTTP / 1.1 429 Too Many Requests e</title>
      <link>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5374282#M18785</link>
      <description>&lt;P&gt;Thank you again for such prompt support reply!&lt;/P&gt;&lt;P&gt;I will increase the sleep timer from 20 minutes to 1 hour (conf option is daemon=3600) to see if this helps resolve the 429 error I will&amp;nbsp;report back with my results.&lt;/P&gt;&lt;P&gt;You still did not answer my two enumerated questions. Your analysis covers question 1 only. Question 2 remains (Is the 429 error due to my client's session or a result of all clients worldwide sessions?)&lt;/P&gt;&lt;P&gt;Finally, I want to correct an assumption you've made. You state that OpenDNS no longer supports DNS-O-Matic. This is not accurate. What was de-supported was the separate login credential unique to DNS-O-Matic. OpenDNS login creditial is being used. The DNS-O-Matic URL is merely an old fully qualified name that OpenDNS still manages on its infrastructure. See below.&lt;/P&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;A href="https://www.whois.com/whois/dnsomatic.com" target="_blank" rel="noopener"&gt;https://www.whois.com/whois/dnsomatic.com&lt;/A&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Wed, 04 Mar 2026 02:43:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5374282#M18785</guid>
      <dc:creator>geoperkins</dc:creator>
      <dc:date>2026-03-04T02:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: ddclient sleep 1200 but getting HTTP / 1.1 429 Too Many Requests e</title>
      <link>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5374815#M18792</link>
      <description>&lt;P&gt;After increasing the delay/sleep (decreasing the update frequency), waiting 48 hours (48 hourly, ddclient daemon=3600, updates), and then reviewing the log, I see that I received two "429 Too Many Requests" warning messages.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since this is a warning (not a fatal error) and the next update 1 hour later succeeds, I am going to consider this issue resolved with a work-around.&lt;/P&gt;&lt;P&gt;I encourage OpenDNS to review the capacity of their dynamic IP and name server infrastructure to allow a more consistent response capability to avoid "429 Too Many Requests" errors. Asking all customers to reduce their load on the infrastructure will only be a bandaid since some customers will follow the recommendation and others will not. Ideally, to maintain good security service OpenDNS needs to provide consistent dynamic IP update capacity. With these observed results, my network is protected, on average, for 23 hours out of 24. A bit more risk than I'd like. But I'm taking advantage of a free service, so perhaps I shouldn't complain too much.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Mar 2026 17:16:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/opendns/ddclient-sleep-1200-but-getting-http-1-1-429-too-many-requests/m-p/5374815#M18792</guid>
      <dc:creator>geoperkins</dc:creator>
      <dc:date>2026-03-05T17:16:19Z</dc:date>
    </item>
  </channel>
</rss>

