From 7f9bb3b2370c6471527fd4fda1c9f08f73ccf2c9 Mon Sep 17 00:00:00 2001
From: kurokobo <2920259+kurokobo@users.noreply.github.com>
Date: Sun, 29 Aug 2021 12:57:30 -0400
Subject: [PATCH] fix: fix tips for name resolution

---
 tips/expose-hosts.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/tips/expose-hosts.md b/tips/expose-hosts.md
index ce6b721..d78d2cb 100644
--- a/tips/expose-hosts.md
+++ b/tips/expose-hosts.md
@@ -28,7 +28,9 @@ One easy way to do this is to use `dnsmasq`.
 3. Create new `resolv.conf` to use K3s. Note that the IP addresses have to be replaced with your K3s host's one.
 
    ```bash
-   sudo echo "nameserver 192.168.0.100" > /etc/rancher/k3s/resolv.conf
+   sudo tee /etc/rancher/k3s/resolv.conf <<EOF
+   nameserver 192.168.0.100
+   EOF
    ```
 
 4. Add `--resolv-conf /etc/rancher/k3s/resolv.conf` as an argument for `k3s server` command.
@@ -47,6 +49,7 @@ One easy way to do this is to use `dnsmasq`.
 5. Restart K3s and CoreDNS. The K3s service can be safely restarted without affecting the running resources.
 
    ```bash
+   sudo systemctl daemon-reload
    sudo systemctl restart k3s
    kubectl -n kube-system delete pod -l k8s-app=kube-dns
    ```