Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Example config in README for namecheap.com does not work for given aliases #108

Closed
quazar0 opened this issue Sep 8, 2015 · 4 comments
Closed

Example config in README for namecheap.com does not work for given aliases #108

quazar0 opened this issue Sep 8, 2015 · 4 comments

Comments

@quazar0
Copy link

quazar0 commented Sep 8, 2015

When I use the example configuration that is shown in the README file, for namecheap.com, using the full hostname in the alias, the server returns the error "A record not Found;".
But if I only use the sub-domain, not the full hostname, it does the DDNS update successfully.

So, from the README file, if I use: alias alpha.YOURDOMAIN.TLD, the server returns the "A record not Found;" error. But if I use: alias alpha, instead, then it is successful.

Here is the output from my log file (note: there are some updates for no-ip in this log output; they can be ignored):

Mon Sep  7 23:16:02 2015: RESTART command received, restarting.
Mon Sep  7 23:16:02 2015: Inadyn version 1.99.14 -- Dynamic DNS update client.
Mon Sep  7 23:16:02 2015: Resolving hostname alpha.mydomain.com => IP# 76.20.210.11
Mon Sep  7 23:16:02 2015: Cached IP# 76.20.210.11 from previous invocation.
Mon Sep  7 23:16:02 2015: Last update of xxx.sytes.net on Mon Sep  7 22:36:20 2015
Mon Sep  7 23:16:02 2015: Cached IP# 76.20.210.11 from previous invocation.
Mon Sep  7 23:16:02 2015: Last update of xxx0.sytes.net on Mon Sep  7 22:36:20 2015
Mon Sep  7 23:16:02 2015: Cached IP# 76.20.210.11 from previous invocation.
Mon Sep  7 23:16:02 2015: Last update of xxx9.sytes.net on Mon Sep  7 22:36:21 2015
Mon Sep  7 23:16:02 2015: Allocated 60 bytes buffer 0x22adeb0 for temp buffer before encoding.
Mon Sep  7 23:16:02 2015: Checking required size for base64 encoding of user:pass for custom@http_srv_basic_auth ...
Mon Sep  7 23:16:02 2015: Allocating 61 bytes buffer for base64 encoding.
Mon Sep  7 23:16:02 2015: Base64 encoded string: *****some*base64*string*****
Mon Sep  7 23:16:02 2015: Checking required size for base64 encoding of user:pass for default@no-ip.com ...
Mon Sep  7 23:16:02 2015: Allocating 45 bytes buffer for base64 encoding.
Mon Sep  7 23:16:02 2015: Base64 encoded string: *****some*base64*string*****
Mon Sep  7 23:16:02 2015: Freeing temp encoding buffer 0x22adeb0
Mon Sep  7 23:16:02 2015: Checking for IP# change, connecting to checkip.dyndns.org(216.146.43.70:80)
Mon Sep  7 23:16:22 2015: Waiting (20 sec) for three-way handshake to complete ...
Mon Sep  7 23:16:33 2015: Connected.
Mon Sep  7 23:16:33 2015: Querying DDNS checkip server for my public IP#: GET / HTTP/1.0
Host: checkip.dyndns.org
User-Agent: inadyn/1.99.14 https://github.com/troglobit/inadyn/issues

Mon Sep  7 23:16:34 2015: Checked my IP, return code: 0
Mon Sep  7 23:16:34 2015: IP server response:
Mon Sep  7 23:16:34 2015: 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: 104

<html><head><title>Current IP Check</title></head><body>Current IP Address: 76.20.210.11</body></html>
Mon Sep  7 23:16:34 2015: No IP# change detected, still at 76.20.210.11
Mon Sep  7 23:16:34 2015: Update forced for alias alpha.mydomain.com, new IP# 76.20.210.11
Mon Sep  7 23:16:34 2015: Sending IP# update to DDNS server, connecting to dynamicdns.park-your-domain.com(104.219.249.25:443)
Mon Sep  7 23:16:34 2015: Sending IP# update to DDNS server, initiating HTTPS ...
Mon Sep  7 23:16:34 2015: SSL connection using ECDHE-RSA-AES256-SHA384
Mon Sep  7 23:16:34 2015: SSL server cert subject: /OU=GT69052503/OU=See www.geotrust.com/resources/cps (c)15/OU=Domain Control Validated - QuickSSL(R) Premium/CN=dynamicdns.park-your-domain.com
Mon Sep  7 23:16:34 2015: SSL server cert issuer: /C=US/O=GeoTrust Inc./OU=Domain Validated SSL/CN=GeoTrust DV SSL CA - G4
Mon Sep  7 23:16:34 2015: Sending alias table update to DDNS server: GET /update?domain=mydomain.com&password=*****my-password*****&host=alpha.mydomain.com HTTP/1.0
Host: dynamicdns.park-your-domain.com
Authorization: Basic *****some*base64*string*****
User-Agent: inadyn/1.99.14 https://github.com/troglobit/inadyn/issues

Mon Sep  7 23:16:34 2015: Successfully sent DDNS update using HTTPS!
Mon Sep  7 23:16:34 2015: Successfully received DDNS update response (699 bytes) using HTTPS!
Mon Sep  7 23:16:34 2015: DDNS server response: HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 429
Content-Type: text/html
Server: Microsoft-IIS/8.5
Set-Cookie: ASPSESSIONIDQERSQDRT=GBIOHCMCAGJNFHIBKONHJJEA; secure; path=/
X-Powered-By: ASP.NET
Date: Tue, 08 Sep 2015 03:16:34 GMT
Connection: close

<?xml version="1.0"?><interface-response><Command>SETDNSHOST</Command><Language>eng</Language><ErrCount>1</ErrCount><errors><Err1>No Records updated. A record not Found;</Err1></errors><ResponseCount>1</ResponseCount><responses><response><ResponseNumber>380091</ResponseNumber><ResponseString>No updates; A record not Found;</ResponseString></response></responses><Done>true</Done><debug><![CDATA[]]></debug></interface-response>
Mon Sep  7 23:16:34 2015: Successful alias table update for alpha.mydomain.com => new IP# 76.20.210.11
@troglobit
Copy link
Owner

Hi! Unfortunately it differs between various DDNS providers, for some you have to give the fully qualified domain name, and for others it's OK to just supply the sub-domain name ...

I guess we could update the README to mention this fact. Thanks for bringing this to my attention again! 😃

troglobit added a commit that referenced this issue Sep 9, 2015
@troglobit
Fix issue #108: Update README with correct alias syntax for Namecheap
0b77790 
Signed-off-by: Joachim Nilsson <troglobit@gmail.com>
@troglobit
Copy link
Owner

Hopefully the README update in 0b77790 will help other users.

I'm now closing this issue, but if there is anything you feel I've missed in your report, then feel free to reopen!

@quazar0
Copy link
Author

quazar0 commented Sep 29, 2015

Thank you. I figured it was something like that; but I wasn't sure. And since the documentation specifically says that NameCheap is supported, I thought you'd want to make sure that it really does work. Thanks again.

@troglobit
Copy link
Owner

NP, @quazar0 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@troglobit @quazar0