• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

INADYN Issue

Started by nCapture, August 16, 2012, 08:20:41 PM

Previous topic - Next topic

nCapture

I'm using inadyn from dd-wrt and I want to update multiple dyndns A records.  I'm using a username/password of one of my A records, along with the -a option to update another A record.

When I set inadyn to verbose mode (--verbose 5) the log indicates that both A records need updated...

Only the first record is updated.  Both records have the same key.  If I set the second record to a value of 4.5.6.7, and run an update from the web interface, it says nochange, and won't update.

Here are the logs.

Fri Aug 17 00:03:26 2012: INADYN: Started 'INADYN Advanced version 1.96-ADV' - dynamic DNS updater.
Fri Aug 17 00:03:26 2012: The request for IP server:
GET http://checkip.dyndns.org/ HTTP/1.0


Fri Aug 17 00:03:26 2012: DYNDNS: IP server response: HTTP/1.1 200 OK
Content-Type: text/html
Server: DynDNS-CheckIP/1.0
Connection: close
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 106

<html><head><title>Current IP Check</title></head><body>Current IP Address: 1.2.3.4</body></html>

Fri Aug 17 00:03:26 2012: W: DYNDNS: My IP address: 1.2.3.4
Fri Aug 17 00:03:26 2012: I:INADYN: IP address for alias 'server1.example.com' needs update to '1.2.3.4'
Fri Aug 17 00:03:26 2012: I:INADYN: IP address for alias 'server2.example.com' needs update to '1.2.3.4'
Fri Aug 17 00:03:27 2012: DYNDNS my Request:
GET /nic/update?hostname=server1.example.com HTTP/1.0
Authorization: Basic ...==
Host: 184.105.242.3
User-Agent: inadyn advanced/1.96-ADV software@stevehorbachuk.com


Fri Aug 17 00:03:27 2012: I:INADYN: Alias 'server1.example.com' to IP '1.2.3.4' updated successfully.
Fri Aug 17 00:03:27 2012: W:INADYN: DYNDNS Server response:
HTTP/1.0 200 OK
Date: Fri, 17 Aug 2012 03:03:27 GMT
Server: dns.he.net v0.0.1
Email: DNS Administrator <dnsadmin@he.net>
Cache-Control: no-cache, must-revalidate
Expires: Sat, 17 Aug 2013 03:03:27 GMT
Content-Length: 20
Content-Type: text/html

nochg 1.2.3.4
Fri Aug 17 00:03:29 2012: DYNDNS my Request:
GET /nic/update?hostname=server2.example.com HTTP/1.0
Authorization: Basic ...==
Host: 184.105.242.3
User-Agent: inadyn advanced/1.96-ADV software@stevehorbachuk.com


Fri Aug 17 00:03:29 2012: I:INADYN: Alias 'server2.example.com' to IP '1.2.3.4' updated successfully.
Fri Aug 17 00:03:29 2012: W:INADYN: DYNDNS Server response:

kcochran

So no reply on the second one?  Same auth key for both hosts?

Which incidentally, you should change it for both of them.  You left the Basic auth header in here before I edited it, and as such you effectively disclosed the auth key.

nCapture

Ahh, missed the fact that I left the auth key.  I'll change them.

I get a response on the second host, but it never updates.  I set it to 127.0.0.1 (both manually), and let inadyn update them.  Only the first one is updated.

nCapture

Here is a full log file:

Fri Aug 17 09:12:35 2012: INADYN: Started 'INADYN Advanced version 1.96-ADV' - dynamic DNS updater.
Fri Aug 17 09:12:35 2012: The request for IP server:
GET http://checkip.dyndns.org/ HTTP/1.0


Fri Aug 17 09:12:35 2012: DYNDNS: IP server response: HTTP/1.1 200 OK
Content-Type: text/html
Server: DynDNS-CheckIP/1.0
Connection: close
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 106

<html><head><title>Current IP Check</title></head><body>Current IP Address: 1.2.3.4</body></html>

Fri Aug 17 09:12:35 2012: W: DYNDNS: My IP address: 1.2.3.4
Fri Aug 17 09:12:35 2012: I:INADYN: IP address for alias 'gw.city.example.com' needs update to '1.2.3.4'
Fri Aug 17 09:12:35 2012: I:INADYN: IP address for alias 'www.example.com' needs update to '1.2.3.4'
Fri Aug 17 09:12:36 2012: DYNDNS my Request:
GET /nic/update?hostname=gw.city.example.com HTTP/1.0
Authorization: Basic gw.city.example.com:secretpassword==
Host: 184.105.242.3
User-Agent: inadyn advanced/1.96-ADV software@stevehorbachuk.com


Fri Aug 17 09:12:36 2012: I:INADYN: Alias 'gw.city.example.com' to IP '1.2.3.4' updated successfully.
Fri Aug 17 09:12:36 2012: W:INADYN: DYNDNS Server response:
HTTP/1.0 200 OK
Date: Fri, 17 Aug 2012 12:12:36 GMT
Server: dns.he.net v0.0.1
Email: DNS Administrator <dnsadmin@he.net>
Cache-Control: no-cache, must-revalidate
Expires: Sat, 17 Aug 2013 12:12:36 GMT
Content-Length: 20
Content-Type: text/html

nochg 1.2.3.4
Fri Aug 17 09:12:38 2012: DYNDNS my Request:
GET /nic/update?hostname=www.example.com HTTP/1.0
Authorization: Basic gw.city.example.com:secretpassword==
Host: 184.105.242.3
User-Agent: inadyn advanced/1.96-ADV software@stevehorbachuk.com


Fri Aug 17 09:12:38 2012: I:INADYN: Alias 'www.example.com' to IP '1.2.3.4' updated successfully.
Fri Aug 17 09:12:38 2012: W:INADYN: DYNDNS Server response:
HTTP/1.0 200 OK
Date: Fri, 17 Aug 2012 12:12:38 GMT
Server: dns.he.net v0.0.1
Email: DNS Administrator <dnsadmin@he.net>
Cache-Control: no-cache, must-revalidate
Expires: Sat, 17 Aug 2013 12:12:38 GMT
Content-Length: 20
Content-Type: text/html

nochg 1.2.3.4


kcochran

Aha.  Using the same username in both requests for authentication.  The authentication parameters for the dyn updates are username = hostname to update = hostname argument on URL, password = api key.