Okay...so we are starting our second week with Casper Suite and during this process we provided our network diagram of what we wanted to do and was told it would all work. Well....not so much.
So here's a question for all of you on one of the "hiccups" we are experiencing.
We have 3 JDS's with obviously 1 root (A) and both children (B & C) talking directly to A. We have B & C in a DNS Round Robin which works great, we haven't had any issues with that, but our idea was that A would not serve any clients except as a NetBoot server, but wouldn't actually serve packages. A is really more of a backup repository I guess.
So the question is.... Is there anyway to "block" clients from trying to get packages from JDS A? We only want the clients to get packages from JDS's B & C which are in a round robin (jds.company.com).
I did see that we can use network segments to setup default JDS's that would trickle down to the computer, but we have 60 network segments....also, that wouldn't really solve our problem for our external users. We will be turning up a JSS and JDS in our DMZ in the next couple months and they are set to use the same URL's as internal (ie. jss.company.com & jds.company.com) obviously with just he IP's changed on the external DNS records to go to the DMZ versus internal network.
The whole idea behind this is all the clients would always look for "jss.company.com" for the JSS and "jds.company.com" for the distribution point and whether they are internal or external, they would find it and just use the DNS records to keep traffic internal and external traffic in the DMZ.
Thoughts? Ideas? Hoping somebody has already come across this...
Thank you,
Josh
