How To
Configure Cisco Router to work as an DNS Server..
DNS Server
DNS Server
Name --> to
Ip address resolution
Ip assress -->to Name
The DNS protocol is used to resolve FQDN (Fully Qualified Domain Names) to IP addresses around the world. This allows us to successfully find and connect to Internet websites and services no matter where they are. Its usefulness, however, doesn't stop there: local company and private networks also rely on DNS to operate efficiently and correctly.
In many cases, where a local DNS server is not available, we are forced to either use our ISP's DNS servers or some public DNS server, however, this can sometimes prove troublesome. Today, small low-end routers have the ability to integrate DNS functionality, making life easier, but so do Cisco routers - they simply have to be setup and you're done.
The DNS protocol is used to resolve FQDN (Fully Qualified Domain Names) to IP addresses around the world. This allows us to successfully find and connect to Internet websites and services no matter where they are. Its usefulness, however, doesn't stop there: local company and private networks also rely on DNS to operate efficiently and correctly.
In many cases, where a local DNS server is not available, we are forced to either use our ISP's DNS servers or some public DNS server, however, this can sometimes prove troublesome. Today, small low-end routers have the ability to integrate DNS functionality, making life easier, but so do Cisco routers - they simply have to be setup and you're done.
Let’s discuss how to
configure your Cisco router to provide DNS services to your network, and make
all clients use it as a DNS server. Easy to follow step-by-step process ensures
you'll understand the process and have it running within minutes.
Example Scenario
Consider the following network diagram. This is our example network, we'd like to enable the DNS Service so our workstations can properly resolve Internet domains but also local network names.
1) First step is to enable the DNS service and domain lookup on the router:
R1# configure terminal
R1(config)# ip dns server
R1(config)# ip domain-lookup
R1(config)# ip dns server
R1(config)# ip domain-lookup
Next, we need to
configure the router with a public name-server, this will force the router to
perform recursive DNS lookups, in other words, for every request it receives
from our workstations the router will try to find the answer by asking as many
DNS servers it needs, and finally return with an answer:
R1(config)# ip
name-server 4.2.2.5
R1(config)# ip name-server 4.2.2.6
R1(config)# ip name-server 4.2.2.6
The Cisco IOS will allow
you to enter up to 6 different name servers (essentially DNS servers). Usually
you would use your ISP's DNS server to ensure you have quick responses, then
place a few free public DNS servers such as the ones above. This will ensure
that you'll get a DNS response from either your ISP or public DNS servers.
2) Next step is to configure your DNS server
with the host names of your local network, this way when Pavan PC trys to ping
or connect to Venkat, the router will successfully resolve its netbios name to
the appropriate IP address:
R1(config)# ip host Pavan
192.168.1.10
R1(config)# ip host Keerthi 192.168.1.11
R1(config)# ip host Venkat 192.168.1.12
R1(config)# ip host Keerthi 192.168.1.11
R1(config)# ip host Venkat 192.168.1.12
If you now try to ping Venkat directly from your router's CLI
prompt, you should receive an answer:
R1# ping Venkat
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.12, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max =
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.12, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max =
No comments:
Post a Comment