11-02-2017 02:40 PM
11-02-2017 04:59 PM
Dns views in very simple terms can be described as different dns servers within the same bind. Imagine a senario where this bind instance is down, either administratively or some other reasons.the alternative server helps.
Hope this helps
11-06-2017 02:12 AM
I have done this - normally it is because you want the zone to have different content based on where the client queries are coming from.
If queries are coming from the Internet, you will want to put all your publically accessible IP's in an "external" view on the DNS servers deployed for handling external inbound queries (eg in a DMZ).
However clients "inside" the network might want to reach the same services using internal IP addresses, so they don't go out the firewall to the external IPs - so you deploy another "view" containing all your internal IP's to the internal DNS servers.
I also had a customer who deployed a third copy of the same zone, this time for 3rd party partners, who came in via a different method and via a different firewall using different destination NAT addresses than the internal/external IPs, so we had yet another view for them.
Having different views can get confusing, but it is a really powerful feature if done right.
PCN (UK) Ltd
All opinions expressed are my own and not representative of PCN Inc./PCN (UK) Ltd. E&OE