Forum

When I try to set a sub domain using the set_dns command, it wipes out all my sub domain records.

This is the url I've been using to try this:
https://api.dynadot.com/api3.html?key=MY_KEY&command=set_dns&domain=MY_DOMAIN&main_record_type=a&main_record=IP_ADDRESS&sub_record_type0=a&sub_record0=SUB_IP_ADDRESS

Just found this thread after trying to add one record and ALL my other records are now gone :-(
Please, please change this or add at least another option for "update_dns_record".

It's 2022 now, 9 years past and it is still an issue. If `set_dns` or `set_dns2` is designed to work this way. Could you provide a new API, namely `update_dns_record`, supports updating/adding a single DNS record under a specific domain?

This issue raises in 2013, and i can't believe Dynadot Architect and Engineers are still not improving their API.  Is 2021, fast forward 7 years, the same issue happens to me.  I just signed up recently and I was shocked to see the same issue.  it DOESN'T MAKE SENSE to wipe out all the records by just needed to add 1 record.   The solution given to me is that when adding 1 record, i need to make sure i include all the previous records.  If i have 40 records, wanted to add 1, i have to submit my payload with total of 41 records.  How on earth i get the previous 40 records in the first place ?  This is definitely a design issue.  go-acme/lego has rejected to add dynadot as their provider when I was talking to them https://github.com/go-acme/lego

I need a solution from Dynadot for this and stop using XML for API please.  Please make a new version 4 that support JSON

Thank you for the feedback, we appreciate your thoughts and are always working towards improving our products and services.

I realize this thread is really old just found it through googling. The fact that I have to submit ALL of the information again rather than just say change sub_record_type9=whatever is kind of ridiculous.

try