Birmingham mumbai

[
 292 
]
To further test our DNS server, we can use the 
dig
 command, as we did before while 
we were experimenting with caching. Try 
dig
 against a local server on your LAN, as 
well as a DNS address that's not located on your LAN (change the first domain to an 
actual domain on your LAN):
dig webserv.local.lan 
dig www.packtpub.com 
You should see a response similar to the following:
;; Query time: 1 msec 
;; SERVER: 127.0.0.53#53(127.0.0.53) 
;; WHEN: Sat Feb 10 10:00:59 EST 2020 
;; MSG SIZE  rcvd: 83 
What you're looking for here is for both local resources and external websites to 
be resolvable now. You'll probably notice that the DNS server used in the output 
will most likely show up as a localhost address, as it did in my output, and not 
the address of the DNS server we just set up. Actually, you can ignore this. Most 
distributions of Linux nowadays use local resolvers, which essentially cache DNS 
lookup results on your local computer. Your computer is still using the DNS server 
we set up, but there's just an additional layer in between your computer and the 
DNS server. You can verify this with the following command:
systemd-resolve --status | grep "DNS Servers"
The output will show you the IP address of the actual server that's responding to 
your DNS lookups.
Next, let's take a look at the process of setting up an internet gateway, which is an 
option to consider if you don't already have a router or firewall on your network 
that acts as a device between your internet connection and your internal network.