-
Notifications
You must be signed in to change notification settings - Fork 8
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
TTL value owerwritten #10
Comments
The DDNS sets the TTL value to 0. I agree with you that it should use the default TTL value. Im going to add an environment variable to set it manually. If not set, it uses the default value of Hetzner. Therefore it shouldn't effect the zonefile. What do you think about that? |
This sounds good. If the environment variable with appropriate value is provided, it should set it, if the user does not set the environment variable, the TTL should not be set at all. |
The environment variable is now included in v2.0 |
Nevermind. I got to fix it. I'm going to respond if it's working |
Could you try it again? Just put out version 2.1, which includes a new implementation to read the provided config. Now the TTL value should be factored in. |
@kutzilla I tested it today. Now, if no ttl value provided, the default value will be written into the zone file: It is a working solution. But actually I would expect that it would not set the ttl value, if not provided, and and the result would be like |
After the DDNS update, the TTL value was set to 0, regardless of the default TTL value.
Zonefile entry before DDNS update:
After DDNS update:
The text was updated successfully, but these errors were encountered: