> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/solutions/coredns-configuration-not-re-generated-after-reboot.md).

# CoreDNS Configuration Not Re-Generated After Reboot

## Problem

We have observed that changes made to CoreDNS template *coredns.yaml* in */opt/pf9/pf9-kube/conf/addons/dns* are not reflected after the reboot of node. However, restarting ***pf9-kube*** service regenerates the *coredns.yaml* file from template.

## Environment

* Platform9 Managed Kubernetes - All Versions

## Cause

* This is by design to prevent a full restart of the ***pf9-kube*** chain and a status check is run before triggering stop and start of ***pf9-kube*** when the ***nodelet*** service starts. This allows us to avoid tasks like certificate generation, Docker restart every time ***nodelet*** is restarted.
* Explicit restart of the ***pf9-kube*** service performs a complete stop and start of the kube chain and therefore those files are re-generated.

## Resolution

* If there is a requirement to regenerate the *coredns.yaml* file post reboot partial restarts can be disabled, and an override file can be created in */etc/pf9/nodelet* with the following contents.

{% tabs %}
{% tab title="None" %}

```none
$ cat /etc/pf9/nodelet/override.yaml
---
FULL_RETRY_COUNT: "1"
```

{% endtab %}
{% endtabs %}

* Once this file is created, restart the ***pf9-nodeleted*** service:

{% tabs %}
{% tab title="None" %}

```none
~# systemctl restart pf9-nodeleted
```

{% endtab %}
{% endtabs %}

## Additional Information

* Note that disabling the partial restarts feature will restart the entire stack which will take longer than usual for the node.
* To persist the changes made to coredns.yaml refer to [this article](https://support.platform9.com/knowledge/articles/360056449414/en-us?brand_id=227678).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmk/solutions/coredns-configuration-not-re-generated-after-reboot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.