I just noticed that the TTLs reset to 7200 on the "A" records that I updated via the Dynamic DNS REST API tool.
https://public-api.sonic.net/dyndns/
Obviously you don't want a long TTL for a host that is dynamic. I can live with 7200 but I was trying for 1800, which does not seem excessively low. I did try to at &ttl=1800. It took it without giving an error but it did not set the TTL.
So, not to seem ungrateful for the great tool, I really do love it and will use it as is; but it would be great to add a switch to set our own TTL, or to simply not revert the TTL during updates. If we can't get it then I just have to make sure to go in and lower my TTLs after each dyn dns update (That is a reminder for others that might use this tool.)
P.S. Also noted that the zone SOA does not increment when using the API. The Sonic name servers do pick up the changes so I don't see that as an issue; just something that would make it more "clean" if added.
https://public-api.sonic.net/dyndns/
Obviously you don't want a long TTL for a host that is dynamic. I can live with 7200 but I was trying for 1800, which does not seem excessively low. I did try to at &ttl=1800. It took it without giving an error but it did not set the TTL.
So, not to seem ungrateful for the great tool, I really do love it and will use it as is; but it would be great to add a switch to set our own TTL, or to simply not revert the TTL during updates. If we can't get it then I just have to make sure to go in and lower my TTLs after each dyn dns update (That is a reminder for others that might use this tool.)
P.S. Also noted that the zone SOA does not increment when using the API. The Sonic name servers do pick up the changes so I don't see that as an issue; just something that would make it more "clean" if added.