DO Ideas 2

DNS: Configurable setting to raise and lower TTL value

When making changes to records in account DNS area, TTL value is permanently set to 2 hours making testing changes to DNS record difficult.
By adding a control to lower TTL when making changes and raise it again after testing would be a big help.
Maybe go even further to auto lower the TTL when a record is edited in the account center and then auto raise it after a set time??

  • Dominic
  • Sep 11 2018
  • Shipped
  • Sep 11, 2018

    Admin Response

    As of 1/23/17, the ability to customize TTLs for domain records on the control panel has been added. We've also improved the UI/UX for DNS to be consistent with the rest of the control panel. Keep an eye out for more improvements to DNS in the future.
  • Attach files
  • Zachary DuBois commented
    September 11, 2018 19:24

    Trurl McByte: If you need to customize TTL, just open a support ticket and they will do it for you. This thread isn't for the lack of the ability, it is for the ease to do so.

  • Trurl McByte commented
    September 11, 2018 19:24

    For service discovery with external access need or customization of TTL in existing API or possibility to delegate subdomain to custom NS like SkyDNS.

  • Anonymous commented
    September 11, 2018 19:24

    Looks like this request goes back to Jan of 2013 and has close to 600 votes, shouldn't be a difficult add. Why not do it?!
    I love DO, been on the service fora good few years now and frequently recommend you guys to anybody I can. So give your customers who love you another reason to love you!

  • Steve commented
    September 11, 2018 19:24

    Hi DO team,

    please merge votes with https://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/3655172-configurable-soa-record-in-dns to reduce duplicity and speedup implementation of improvements suggested from customers.

    Thank you for your time and cooperation in advance.

  • The Digital Orchard commented
    September 11, 2018 19:24

    The comment below by "Alfonso Gomez-Arzola" is a classic example of probably why DigitalOcean is keeping their DNS zone editor simple... some people don't fully grasp how the DNS service is separate from the droplets. DNS can be hosted anywhere on the internet... it does not need to be bundled in with the web hosting like you find on run-of-the-mill VPS's.

  • The Digital Orchard commented
    September 11, 2018 19:24

    There's a lot of angry demands being put here. Please remember that DigitalOcean is providing DNS hosting for FREE. You're all welcome to use another DNS service that provides the features and functionality that you need. No reason that you *must* use DigitalOcean's.

    That said, having an editable TTL value would be good for two reasons... to set a short TTL prior to make infrastructural changes, and a long TTL when you want to implement stability and leverage the caching of downstream DNS servers around the world. That's just good internet etiquette.

    I think that DO is aiming to keep this simple, but at the same time, it has built a service for *developers*, so it can't be made too simple. :)

  • Mathiesha Samarakoon commented
    September 11, 2018 19:24

    Um... honestly would like these features.... if it is too much would like to know the reasons behind your decisions not to implement it. Because its more than two years and we users are kept in the dark

  • Anonymous commented
    September 11, 2018 19:24

    Still gathering feedback? C'mon!

  • Paulo Freitas commented
    September 11, 2018 19:24

    +2 to get this done soon. :)

  • Anand Sharma commented
    September 11, 2018 19:24

    Three votes added... When is this going to come through?

  • Alex Novikov commented
    September 11, 2018 19:24

    More that two years are left. Do we have any changes with it?

  • Ryan H. commented
    September 11, 2018 19:24

    Very critical to be able to control this when migrating a live site! It would be nice to know what the status of this is besides "GATHERING FEEDBACK" :)

  • Remzi Cavdar commented
    September 11, 2018 19:24

    This is really important, because it's part of the DNS management.
    I really hope that DO will implement this.

  • Anonymous commented
    September 11, 2018 19:24

    Just had the idea to add a dyndns-like A record for my home router that could be updated with the API... Unfortunately this will only work if I could set the TTL for this record to something like 60 seconds.

  • Andrew Selzer commented
    September 11, 2018 19:24

    Any news on this? Being able to adjust TTL would be a useful feature.

  • Anonymous commented
    September 11, 2018 19:24

    Sadly, guess I have to look for another provider since .is require 24 hours TTL

  • Anonymous commented
    September 11, 2018 19:24

    When do you expect to start allowing to change the TTL values? I cannot use Digital Ocean with my .is domain as it requires TTL to be > 86400:

    Test results for "NS1.DIGITALOCEAN.COM":
    Time To Live (TTL) for the NS records must be 86400 seconds (24 hours) or longer (Is now 1800 sec)

  • mjarvis commented
    September 11, 2018 19:24

    This is a crucial issue for anyone wanting to use .is TLD as it has quite strict requirements on the TTL (>24hours): https://www.isnic.is/en/domain/req

    +3

  • Bryan commented
    September 11, 2018 19:24

    This is still an issue for anyone wanting to use a .is TLD. Is there any update?

  • Morthawt commented
    September 11, 2018 19:24

    As soon as TTL can be modified on all records, I will be moving my records back here most likely at least to test the comparisons between here and namecheap.

  • Ben commented
    September 11, 2018 19:24

    Don't forget to make the last parameter of the SOA separately configurable. That used to be used (among other things) for the default TTL, but modern use uses it only for the NXDOMAIN TTL (the time that an NXDOMAIN response in the zone is cached). It is often handy to be able to configure that separately from the default TTL.

  • Anonymous commented
    September 11, 2018 19:24

    The current ttl 1800 is just way too long given how quick the droplets spin up. Please make it adjustable

  • Michael Belt commented
    September 11, 2018 19:24

    +1 for this. It's standard everywhere else.

  • ashley commented
    September 11, 2018 19:24

    +1 for allowing this to be custom-set (API would be a helpful step).
    TTL at 1800 is much better than it was, but still makes testing S L O W !

  • Alfonso Gomez-Arzola commented
    September 11, 2018 19:24

    ISNIC has a strict requirement of 86400 (24 hours). Was looking forward to switching a client’s .is domain to DO, now scrambling to launch their new site as quickly as possible on another host. I was so looking forward to using DO on this project!

  • Anonymous commented
    September 11, 2018 19:24

    +1

  • marlus.saraiva commented
    September 11, 2018 19:24

    Just voted. You guys should at least lower the default value to 5min, like Rackspace. Is crucial for me that the information about new CNAME records propagate as fast as possible. So I'll probably have to wait a bit more before moving from Rackspace.

  • omidse commented
    September 11, 2018 19:24

    I hope that in the future one could choose TTL by default or what you want in control banell on the Digital Ocean

  • Bruno commented
    September 11, 2018 19:24

    will be great that function! with the api

  • Artem commented
    September 11, 2018 19:24

    Wish I could give all 10 votes here. RackSpace has 300 second for the default TTL and I can set it even smaller. 300 seconds is ideal. Current 1800 is better then two hours but still 6 times more then RackSpace. I think 300 is reasonable. I can imagine applications that will require smaller value.

  • Abe commented
    September 11, 2018 19:24

    The Fisher-Price DNS panel and the lack of IPv6 are the main things holding me back from leaving Linode entirely. Looking forward to this being implemented!

    Definitely check out how Linode does DNS config, as that amount of control is nice to have.

  • fufu commented
    September 11, 2018 19:24

    Just voted.

    This could be great (missing it after some DNS based idea we were planning).

  • Anonymous commented
    September 11, 2018 19:24

    Probably the single biggest thing stopping me using DO over Linode for a load of clients.

    Any chance of an update on where you are with this?

  • Reverend Doctor Proxy commented
    September 11, 2018 19:24

    Thanks for the update, Mr. Uretsky. I'm looking forward to having this feature added! Lowering TTL values is critial for certain domains I host as they have several A records for failover. It is a common and extremely useful feature for most. Even if this were added as an API call for now, I as well as others could deal with that.

  • Anonymous commented
    September 11, 2018 19:24

    Hello. It's been many months since the adjustable TTL discussion started and was just curious if there was any progress on this? We're working with a few new clients and before we direct them to DO we wanted to make sure this was an option. If this is not going to be an option, can anyone reccomend a provider you've had a positve experience with that does also offer this option? Thanks

  • Anonymous commented
    September 11, 2018 19:24

    This is an important setting, especially when your use to having it. I would like to see access to this in the near future. Especially when moving domains around and dev work.

  • Ben commented
    September 11, 2018 19:24

    I'd like to see the ability to set each record's TTL separately. This and having DNS changable from the API are two of the things currently keeping me from moving some servers from Linode to DO.

  • Karu commented
    September 11, 2018 19:24

    I agree with TTL's being far too high and non configurable is tough to work with. I can spin up a new server in 7 minutes so would be great to flick my changes over in a timely manner. Please lower the TTL's or make them configurable as soon as possible.

    No other issues everything else is great! :)

  • Moisey Uretsky commented
    September 11, 2018 19:24

    We're going to lower the default this week to 600 (10 mins) this week and then look to add custom TTLs later in the future.

  • Rob Martin commented
    September 11, 2018 19:24

    I can stand up a replacement server in about 300 seconds, or 60 seconds if I have a fresh image. These TTLs are crazy long. But the worst part is being told the wrong information over and over. DO support doesn't understand DNS and resorts to blaming the customer rather than looking into the issue.

    Moisey, the zone file in DO's DNS interface says 7200 seconds, not 1800 seconds. `dig` says 7200 seconds, not 1800 seconds. This is broken at least for some customers and all I'm seeing from DO is how I'm doing it wrong.

  • Chip Castle commented
    September 11, 2018 19:24

    Yes, my zone file is set to 7200 as well. How can this be updated to 1800?

  • Kevin Landreth commented
    September 11, 2018 19:24

    Also, the $TTL in the zone file (according to the labs panel) is 7200. You might want to check with engineering @muretsky

  • Kevin Landreth commented
    September 11, 2018 19:24

    I would use this extensively and it would greatly reduce my admin burden!

  • Moisey Uretsky commented
    September 11, 2018 19:24

    Hi Dominic,

    Currently we set all TTLs to 1800 which is 30 minutes so you shouldn't be seeing a 2 hour TTL unless the entry was DNS cached somewhere in between.

    Your suggest on lowering the value when a new record is created and then having it automatically raised is very interesting, the only issue would be editing an existing record it would still be under the default 1800 seconds and so it would take up 30 minutes for it to expire in various locations.

    For DNS testing we usually just update the records and clear cache locally and then query the nameserver directly to make sure they are valid.

    We have thought about opening up the TTL for customers to set so that could be interesting. If it gets enough votes and discussions we'll move in the direction the customers want. =]

  • Moisey Uretsky commented
    September 11, 2018 19:24

    Hi Dominic,

    Currently we set all TTLs to 1800 which is 30 minutes so you shouldn't be seeing a 2 hour TTL unless the entry was DNS cached somewhere in between.

    Your suggest on lowering the value when a new record is created and then having it automatically raised is very interesting, the only issue would be editing an existing record it would still be under the default 1800 seconds and so it would take up 30 minutes for it to expire in various locations.

    For DNS testing we usually just update the records and clear cache locally and then query the nameserver directly to make sure they are valid.

    We have thought about opening up the TTL for customers to set so that could be interesting. If it gets enough votes and discussions we'll move in the direction the customers want. =]