matt1 / gandi-ddns Goto Github PK

https://www.gandi.net/news/en/2015-12-29/6536-livedns_beta_first_glimpse_into_our_new_dns_platform/

On line 118, you should add an indent to have
return None
instead of
return None

Otherwise, the function read_config will always return None ...

ddnsc is a similar project, however it supports multiple dns providers. I think it would make sense to merge this project with ddnsc so there can be one package that supports many providers, especially since they are both already written in python.

Here's what I got from GANDI

Dear Customer,

We contact you today because you are identified as an active user of our
public production API.

We would like to inform you that an EMERGENCY patch for our public API
has been deployed today [02/08/2017 Paris time] on our producton
platform, in order to counter an incident[1] that impacted all of our
customers.

This corrective action has resulted in significant changes in our public
API.

It is therefore necessary that you check your code, and more precisely
the use of the following method: "gandi.api.domains.zone.record::list"

If this is your case, please note that the use of that method has been
updated, particularly the 'id' field type returned by that fuction. Your
code now needs to accept the fact that the 'id' type is a string of
characters, and no longer an integer (i4 in xmlrpc).

The two functions which use this 'id' as an entry are:

• gandi.api.domains.zone.record::update
• gandi.api.domains.zone.record::list (filtre sur l'id)

In order to ensure optimal backward compatibility, those two functions
still accept an "integer" type as entry for the 'id' field, in addition
to the "string of characters" type. It is strongly recommended, however,
to use the "string" type.

Our online public API documentation[2] has been updated as a result of
these changes.

Given the urgency and consequences of this incident, we had no choice
but to deploy this patch without prior notification and we apologize for
any inconvenience.

Our customer service is of course at your disposal to assist you if you
encounter difficulties in the implementation of the modifications.

We thank you for your confidence in Gandi.

Gandi.net

[1] http://status.gandi.net/timeline/events/957
[2] http://doc.rpc.gandi.net/domain/reference.html?zone.record.list#ZoneRecordReturn
& http://doc.rpc.gandi.net/domain/reference.html#RecordUpdateOptions

Hello,
If I understand it correctly, the provider changes the prefix of private IPv6 addresses, so ddns is also needed for IPv6.
The API used to determine the IPv4 address, also works for IPv6: https://api6.ipify.org (only works if you have an IPv6 address)
In case you are interested, I can offer to implement this.

It seems that http://ipv4.myexternalip.com/raw not working anymore with urllib (but also with curl) so I have replaced this line

Hi there, this is not a technical issue but more a question about the technique:
How fast do the changes pushed onto gandi take to propagate?