From b0865b7ac8daebd404971c21dcd4ae3eeaea3a46 Mon Sep 17 00:00:00 2001
From: andran777 <86196800+andran777@users.noreply.github.com>
Date: Thu, 18 Aug 2022 04:11:42 +0530
Subject: [PATCH] Add dig command resources
---
.../101-live-in-terminal/119-dig.md | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/content/roadmaps/102-devops/content/102-managing-servers/101-live-in-terminal/119-dig.md b/content/roadmaps/102-devops/content/102-managing-servers/101-live-in-terminal/119-dig.md
index 2ab4db640..89ecb0fb2 100644
--- a/content/roadmaps/102-devops/content/102-managing-servers/101-live-in-terminal/119-dig.md
+++ b/content/roadmaps/102-devops/content/102-managing-servers/101-live-in-terminal/119-dig.md
@@ -1 +1,12 @@
-# Dig
\ No newline at end of file
+# dig
+
+`dig` command stands for **D**omain **I**nformation **G**roper. It is used for retrieving information about DNS name servers. It is mostly used by network administrators for verifying and troubleshooting DNS problems and to perform DNS lookups. It replaces older tools such as `nslookup` and the `host`.
+
+It has the following syntax: `$ dig [server] [name] [type]` e.g. `$ dig roadmap.sh`
+
+Free Content
+What is dig command?
+More on dig
+What is host command?
+What is nslookup command?
+What is DNS?
\ No newline at end of file