8 results found
I have a fair few lebs about the place...
I would love to have the option of serving googlebot and other spiders only ipv6's and normal peeps ipv4's.
This would be great for SEO ;)2 votes
When you click to clone a record, it would go directly to the edit popup rather than refreshing the page.1 vote
The ability to Backup and Restore zones. It was mentioned in a previous request and accepted for a previous build so it must have fallen in the cracks.
Really needed for people who use the API and Geo Regions (and since the API dosent yet support Geo Regions it cant be implemented on our end).1 vote
Our API supports GeoDNS so backup/restore should be implemented on customer side. Beside that there is possibility of dumping the zone file.
So you can for example make one record for "US Central" and another for "US West" and don't need to re-type the record 10 times.1 vote
Use appropriate http verbs: GET for queries, POST for changes. Remember that GET requests can be cached by proxies.
Remove the username from auth. The api key is sufficient to uniquely identify the user (just make sure it will never repeat, but probably you already did that)
And why? Because I'm not very fond of leaving my e-mail address in scripts i wrote for maintenance... Think about it. Just the (large and anonymous) key it is sufficient.1 vote
Current version of API is in wide use so it’s not possible to modify it. Right now we are not planning any API changes beside adding new methods (probably together with next major release).
Today is already possible to do this via "update record" API. But support to RFC 2136 would be great for use with existing appliances (e.g. routers)1 vote
We are not planning to add support for dynamic DNS in near future.
Maybe it's just me being overzealous...1 vote
By default we are providing two nameservers but users can add additional third party slaves if necessary.
- Don't see your idea?