Hello Mohammed,
Both will forward request to DNS server but with DNS view configuration setup, that setup is normally used in split dns design with forwarding traffic to internal and external world.
For example :-
ip dns view internal
domain name ganesh.com
domain name-server 8.8.8.8
domain name-server 8.8.4.4
The command above creates the DNS view named "internal", sets the domain name to "ganesh.com" and sets up DNS forwarding to a pair of Google's DNS servers.
Now, Create private internal DNS namespace within that view.
ip host view internal server1 192.168.1.111
ip host view internal server2 192.168.1.112
ip host view internal server3 192.168.1.112
ip host view internal server4 192.168.1.114
ip host view internal server5 192.168.1.115
Next step is to assign the view to a ‘view list’. A view list is an ordered list of view where you can put additional restrictions.
ip dns view-list internallist
view internal 1
Now, I assign the view list to a subinterface/VLAN.
interface FastEthernet0/1.1
description data vlan
encapsulation dot1Q 1 native
ip address 192.168.1.1 255.255.255.0
ip dns view-group internallist
ip nat inside
Now, this VLAN has visibility to the “internal” DNS namespace above and utilizes DNS forwarding to Google’s DNS servers.
With ip name-server 1.1.1.1 2.2.2.2 everything gets forwarded to these servers.
Hope it Helps..
-GI
Rate if it Helpss
