Net Talk Client and DNSSimple task

1

Hi,
DNS Simple has their own lightweight Dynamic DNS (DDNS) implementation, available at ddns.horse.
They provide a Curl example: Here is an example using curl: curl -i “https://ddns.horse/nic/update?hostname=example.com&myip=1.2.3.4&myipv6=2001:db8::8a2e:370:7334” -u “accountid:token”
On capesoft converter I got the conversion:
net.Start()
net.Authorization = net.CreateAuthorizationString (‘accountid’,‘token’, Net:WebBasicAuthentication,true)
net.Get(‘https://ddns.horse/nic/update?hostname=example.com&myip=1.2.3.4&myipv6=2001:db8::8a2e:370:7334’)
I am using my Account ID for the authorization string “accountid” and my OAuthToken for the ‘token’ part of it.

However, I am getting authorization failure.
So, I can’t get past the authorization with my credentials. I did double check my credentials and they are correct.
Any insight on why my credentials might be failing?
Thanks,
Ron

2

I presume you are substituting in your ipv4 address, and i guess leave the ipv6 one out? (Unless you are indeed hosting on ipv6).

Regarding the auth, you can run curl from your command line to make sure it works from there using your account id and auth token.

3

No, and like @Bruce said try to get the Curl command working on windows first before building it into your own program.

But have you thought about running your own recursive DNS server and perform lookups/querys on that?

DNS is free, provided you trust your sources, but you can point to many sources. It will be unlikely your DNS server becomes an authoritative DNS server, except when managing your own domains and the ip address(es) they point to.

This offers you a level of privacy, if you pull all the domains down you can find, maybe you are looking for a domain name thats available.
Maybe you want to improve your security, or just monitor the movement of domains and ip addresses.

This blocks rogue domain names, dont know if the US or what ever country you live in does similar.

This (Bind9) is what ships on many open source Firewall/Routing setups and is considered by many to be the defacto DNS for the internet. Certainly the longest serving.

Small and Basic Deployments

  • RAM: 512 MB to 1 GB
  • CPU: 1 core (1.5+ GHz)
  • Use Case: Small internal networks, local caching, or serving a handful of static zone files with under 100 clients

It can scale to eat even the largest of rack server’s, consuming all available ram.

Havent tried the ODBC driver but it could provide an alternative way to lookup domains using Clarion.

But it really depends on what you want from your DNS lookups, how frequently and what other info you want out of the DNS system. Just the odd lookup to validate an email address domain, getting more info where possible, I’d probably stick with Curl. Need to do lots of lookups and I’d start to consider a local DNS server.

This is another DNS system, havent tried it but it might be suitable, multiple platform.

This offer’s the ability to use block lists (Response Policy Zones (RPZ)), in a similar way to ad blockers.

Some Adblocker lists are malicious in clever ways, without going into details. Its all down to Trust.

Edit. Once you go beyond your country’s border, the internet can become more like a work of fiction.