-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config Option for default Values of TTL,... #53
Comments
That seems to be a good idea. For primary and mail default it I would have to check if it is easily possible to make this setting optional, so that you are still able to use it without default. Do you think with implementing templates the requirement for email and primary is gone, as you would copy that from the template? |
I think that would depend on the person using it. For me.. yes.. I would think that templates would mostly focus on default user records. But if you could squeeze in there the SOA record as well then yes. Some people are not going to want a default eMail address (I think?). I suppose that could be worked around in the default SOA record by simply using a "." period in place of the eMail address causing it to come up blank. |
The SOA would definitely be in the template as well. |
Back to the title, at lease please implement setting TTL and other default settings on config. Template is a nice to have, but we can create other ticket for this. |
That would be great yeah. 86400 is fine for the SOA but I don't think anyone is using such high values for the actual records. We'd default to 3600 or 900 if we had such an option. |
Could we please move the default values for things like "zone-ttl" in the config file? Right now it is hard coded in the .php files.
I am editing them in the add-domain.php fully aware that when you update that my changes will be lost and have to be redone. Also.. to be clear.. Would love to set the default "Primary" and default "eMail" as those are almost always the same for me.
And the same for Add Record.
The text was updated successfully, but these errors were encountered: