Split DNS configuration

Started by LynK, January 12, 2016, 08:34:23 AM

Previous topic - Next topic

LynK

Hey guys,

So we have officially released our PBR solution for our sites in an alpha stage. But we have a small problem. The internal hosts that access internal resources do so with the internal routes, but their traffic that matches external IPs go out our secondary connection. The problem is... is that they access the internet unfiltered. the DNS lookup goes to our internal DNS then it routes outside and bypass all of our content filtering onsite, and on the cloud.


So this is what I am thinking. Is it possible to convert the local routers to run split-DNS and have internal queries go to our internal forwarders, and external queries go to our cloud filters, so this way they cannot bypass the filters.

EDIT:

After doing some research I think I found the answer


ip dns view INTERNAL
domain name-server  10.x.x.x
domain name-server  172.x.x.x
dns forwarding source-interface FastEthernet0/0
!
ip dns view EXTERNAL
domain name-server  208.x.x.22
domain name-server  208.x.x.2
dns forwarding source-interface FastEthernet0/0
!
ip dns view-list DNS
view INTERNAL 10
  restrict source access-group INTERNAL_NETWORKS
view EXTERNAL 100
!
ip dns server view-group DNS
ip dns server
Sys Admin: "You have a stuck route"
            Me: "You have an incorrect Default Gateway"


LynK

yes I did ... I must have missed something, I am going to work with TAC and see what we can come up with.
Sys Admin: "You have a stuck route"
            Me: "You have an incorrect Default Gateway"