We recently went the other way. Primarily because while firewalling off things like AD and fileservers worked, the client behavior if they also can't look up the name is improved. The simplest solution to give the guest network an "outside" view of DNS was just to point them outside. Our existing external servers don't do any resolving, so otherwise we'd need to track a special config (and/or set of servers) for the guest network.
On Thu, Jul 21, 2016 at 7:55 AM, Alexandre Adao <[email protected]> wrote: > I would like to know if anyone has opted to use their own local/internal > DNS for Guest Wireless or Eduroam instead public DNS (e.g.Google, OpenDNS, > etc). What would be the reasons? Ex: Audit trails? and What would the risk > if any? Any feedback, I appreciate. > > Thanks, > > --Alex Adao > > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/. > > -- Jeremy Mooney ITS - Bethel University ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
