Dynamic DNS REST API

Advanced feature discussion, beta programs and unsupported "Labs" features.
16 posts Page 2 of 2
by augie » Mon Feb 25, 2013 4:05 pm
Not in my tests.
by klui » Mon Feb 25, 2013 9:30 pm
So I tested it some more and it appears I really can't make use of it if I don't have a domain registered with Sonic. Is this the correct assessment? While I can get my IP, I can also issue curl ifconfig.me and it will do the same thing. I can't associate a domain with my connection which will allow me to use list_api_keys so I can access my connection while I'm away from home which services from DynDNS and No-IP allows.

As an aside, is DynDNS a trademark of dyn.com? If you have no affiliation with dyn.com, you may want to consider using the generic term ddns.
by kgc » Mon Feb 25, 2013 9:37 pm
If you don't have a domain, you can always get one - free for the first year as part of the 'personal hosting' service and also includes free domain based web hosting.
Kelsey Cummings
System Architect, Sonic.net, Inc.
by trillian » Wed Mar 18, 2015 3:19 pm
Has anyone done any work with this lately?

The dyn/noip guys seem to be getting very greedy and this is much cleaner anyway!

It does look like the back end interface is still in place at Sonic.
by kgc » Wed Mar 18, 2015 3:35 pm
You're certainly welcome to use it.
Kelsey Cummings
System Architect, Sonic.net, Inc.
by trillian » Sat Mar 21, 2015 12:30 pm
Perl not really my thing so this may be an idiot question ... I'm a hardware guy and only use it for text file filtering!
Looking at the perl

The call in line 15 of the git checkin

my $address = Net::Address::IP::Local->public;

Returns an IPV6 address ... so I thought I'd try this ...

my $address = Net::Address::IP::Local->public_ipv4

this fails.

However this works ... returning the same IPV6 address.

my $address = Net::Address::IP::Local->public_ipv6

I'm certain I have an IPV4 connection as I can see line 36 returning and IPV4 address.

$response = $ua->get('https://public-api.sonic.net/dyndns/ip')

Am I doing something silly or is this expected behaviour with Net::Address::IP::Local ?
Looking under the hood it looks like it uses a.root-servers.net at 198.41.0.4 ... I'm sure I can ping that.
16 posts Page 2 of 2