diff --git a/content/blog/scaling_coredns_in_k8s.md b/content/blog/scaling_coredns_in_k8s.md
index f7a2223..1aff224 100644
--- a/content/blog/scaling_coredns_in_k8s.md
+++ b/content/blog/scaling_coredns_in_k8s.md
@@ -1,4 +1,4 @@
-+++ title = "Scaling CoreDNS in Kubernetes Clusters" description = "A guide for tuning CoreDNS resources/requirements in Kubernetes clusters" tags = ["Kubernetes", "Service", "Discovery", "DNS", "Documentation", "Deployment"] date = "2018-11-06T11:12:13-00:00" author = "chris" +++
++++ title = "Scaling CoreDNS in Kubernetes Clusters" description = "A guide for tuning CoreDNS resources/requirements in Kubernetes clusters" tags = ["Kubernetes", "Service", "Discovery", "DNS", "Documentation", "Deployment"] date = "2018-11-15T00:00:00-00:00" author = "chris" +++
 
 I'm sharing the results of some tests I ran with CoreDNS (1.2.5) in Kubernetes (1.12) to provide some reference points for tuning CoreDNS to your cluster.
 In addition to testing CoreDNS in its default configuration, I tested CoreDNS with the optional *autopath* plugin enabled.