GnuDIP working, but I am confused GnuDIP working, but I am ...

Topic: GnuDIP working, but I am confused

Post GnuDIP working, but I am confused
by dynulsg on Monday, June 3, 2019

I can get my OpenGear devices to register with the Dynu DDNS service, but .... eh

TL;DR:
I can get stuff to work. Slightly clunky, and not as streamlined as I would like it. Would appreciate understanding where I am off.


I have dedicated a subdomain of a domain I control to hold my dynamic hosts. I have delegated the relevant domain to dynu nameservers, and DNS works well. However, something appears lacking with my understanding of both the terminology and the process involved.

1. In the Dynu DDNS control panel
(https://www.dynu.com/en-US/ControlPanel/DDNS) the first column is named 'Domain', although it clearly holds hostnames, not domainnames.
What am I missing?

2.a. In order for my hosts to successfully update A-records, it appears I need to manually configure an entry for that host on the webpage first. It does not appear to be the case that registration is automatic for a new host. Is this correctly understood?

2.b. Can someone suggest a oneliner with curl to register a new host?

3. Also, in order for my hosts to update A-records successfully, I need to configure the client to use a hostname of the form:
dummystring.actualhostname.myddnssubdomain.mydomain.com

I then configure the service on dynu.com to hold a dummy record for actualhostname.myddnssubdomain.mydomain.com

After this, the client can update the A-record successfully. The need for the dummy string appears odd. May this be a bug in the Opengear gnudip implementation?

In short, what I would like being able to do is:
a. set up my own subdomain, which my hosts can autoregister in. (with credentials)
b. .... without prior config on the website.
c. .... with gnudip


Thanks,

Dag B

Reply with quote | Report
Post Re: GnuDIP working, but I am confused
by dynulsg on Monday, June 3, 2019

dynulsg wrote:
3. Also, in order for my hosts to update A-records successfully, I need to configure the client to use a hostname of the form:
dummystring.actualhostname.myddnssubdomain.mydomain.com
This is false, it appears. Disregard.

Reply with quote | Report
Post Re: Re: GnuDIP working, but I am confused
by dynulsg on Wednesday, June 5, 2019

dynulsg wrote:
dynulsg wrote:
3. Also, in order for my hosts to update A-records successfully, I need to configure the client to use a hostname of the form:
dummystring.actualhostname.myddnssubdomain.mydomain.com
This is false, it appears. Disregard.
I *think* I managed to register an update once without a dummy string prefixing the actual hostname. Can't reproduce it now.

Now it appears I need that dummy string. The state of the 'Wildcard IPv4 Alias' setting in the dyny controlpanel does not make any difference. My DDNS client is ez-ipupdate, it does not use the '-w' switch.

Reply with quote | Report
Tuesday, July 16, 2019 11:39 AM