I've been reading a bit tonight on how to best set up our school network for Internet connectivity. It works as it is, but there are hiccups in client/server access to the Internet from time to time. (note: the Sonicwall always sees the Internet)
My set up as is:
Internet---Sonicwall---Managed Switch---Win 2k8 r2 Server | Clients & Printers
- LAN zone with an IP in our IP range
- WAN zone with static ISP assigned IP and DNS set to Google DNS and ISP's DNS as backup
The Windows Server (just an internal file server)
- Active Directory
- DNS (set to 127.0.0.1)
- DHCP dynamically for a small guest range (phones),
- DHCP statically for devices and student & teacher clients (for filtering purposes)
- Gateway set to Sonicwall IP
- DNS set to Server IP (on some Win8 systems I've had to set an alternate DNS to 184.108.40.206 for Internet connectivity.
So, to questions:
From what I read tonight it seems I should have:
- The Sonicwall WAN looking inward to the Server IP for DNS
- The Server set to have forwarding to look outward to Google/ISP DNS
- The clients DNS set to Server IP and Gateway to Sonicwall IP
Can anyone verify this? I am confused. If the Sonicwall looks to the Server for Internet DNS wont my clients A) bog the Server down and B) have no Internet when the Server is off?
If this isn't best practice, then what is? Am I already doing it right? Should the client DNS look to the Server AND the ISP?