Per-record TTL

colorian

Verified User
Joined
Oct 19, 2018
Messages
9
Greetings,

Didn't DirectAdmin now include per-record TTL for DNS? I enabled it with:

Code:
default_ttl=3600
dns_ttl=1

But I don't get the additional options for per-record TTL that you'd expect in the DNS Management (not from any logon level).

Am I missing something?

Greetings
Kenneth
 
Hello,

Do you use a default enhanced skin? Or different?

dns_ttl.png


I have it on my end. Check the image.
 
ok, make sure you've got an empty line, or line break after:

Code:
dns_ttl=1

restart directadmin and control with

Code:
/usr/local/directadmin/directadin c | grep tls
 
Hello,

Thanks for your input. There was no empty line behind
Code:
dns_ttl=1
, so I did that and restarted but unfortunately that didn't help...

Running your command gives me:
Code:
dns_tlsa=0

Greetings,
Kenneth
 
Actually, never mind. It seems I just didn't wait long enough for DirectAdmin to restart. Now I see the options the way I would expect it to be!

Just to verify: if I have set a custom TTL for a domain name, it is expected behaviour that I can't edit the TTL values unless I put the general setting for that domain to "default", correct?

Thanks.
Kenneth
 
Please clarify your thoughts, I'm not too sure that I understand you correct.
 
I just noticed that, when setting a custom TTL using the "Override TTL" button, this means that per-record TTL can no longer be set. Basically I have to set the TTL back to the "default" one before I can edit per-record TTL values.

I'm just wondering if this is expected behaviour.

Cheers
Kenneth
 
Back
Top