Using with Netlify / setting a TTL of 86400

Totally missed your first post there, @Jocphone , where you answer my question :man_facepalming:

Just got that TTL updated:

$ dig -t ns

; <<>> DiG 9.10.6 <<>> -t ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 666
;; flags: qr aa rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

; EDNS: version: 0, flags:; udp: 4096
;				IN	NS

;; ANSWER SECTION:			86401	IN	NS			86401	IN	NS			86401	IN	NS			86401	IN	NS

Thanks erm… @fool ?

Have added the nameservers at ISNIC again and the request is waiting in their queue.

It still says 3600 for the TTL settings on my Netlify dashboard but I assume that these things take time to update?

Thanks for your help,


Not sure where you’re looking, but I don’t see any mention of TTL records for your NS records in our dashboard. They are only shown in the UI for our DNS hosting provider as far as I know :slight_smile:

The individual HOST records shown in the dashboard will be under 1 day TTL, but the icelandic nic does not seem to care about those :slight_smile:

OK thanks. That had me confused.

I would appreciate the TTL update on


Hi, @macaroni, the TTLs for NS records for have been updated on our DNS service now. :+1:

1 Like

Could you update the TTL for as well?


Hi, @davidarnarsson. Done! :smiley:

1 Like

hey @cmiller , we have updated that TTL for you now. You should be good to go.

1 Like

took care of that for you, @drcongo.

1 Like

I have the same problem when is validating my domain It requires minimum TTL of 86400 sec. Is there any way to changes this through my dashboard dns settings?

Could you update TTL=86400 for ?

Just got that fixed for as well as, folks.

1 Like

Can you update the TTL for Thank you in advance!

hi there, we took care of that for you!

Hi, can you update the TTL for many thanks in advance!

we took care of that for you @bramsmulders!

1 Like

Hi, I am having the same problem with

we took care of that for you, @SveinnB!

Thank you @perry. Can you do the same for, and ? :slight_smile: