Yes it is AD, i just wanted to be reassured when i tell the client, "train or replace" the developer- thanks
Jean-Paul Natola > Date: Thu, 1 Aug 2013 16:11:18 -0700 > Subject: Re: [NTSysADM] Access to website- UPDATE > From: [email protected] > To: [email protected] > > On Thu, Aug 1, 2013 at 3:54 PM, J- P <[email protected]> wrote: > > So i know this question will come from the client- > > > > What are the ramifications of placing an entry of domain.com in the host > > file of every pc? > > Is the client running Active Directory? If so, don't do it. Ever. > Never, ever, never ever. Shall I say it more often? Don't. Just. Dont. > > Is the client *not* running AD? See the above - it's the same story. > > > My guess (only a guess) is that it will cause authentication or some type > > unexpected problems , > > Not necessarily, and not immediately, but when you modify/upgrade your > environment (including renumbering your servers, implementing a new DC > and demoting the old one, or any of a number of other events), you're > screwed, until you find and change the host file on every machine > again. > > This is the reason for which DNS and DHCP were invented - because > managing host files is evil, and stupid, and non-scalable. > > > my thought is , if the PC is looking for domain.com and rather than finding > > a DC within the network, the host file will say "hey domain.com is not here, > > its over the web host in never never land" is this a correct assumption? > > That's one pitfall, certainly. > > As I said, that web developer needs fired or trained. Client's pick on that > one. > > Kurt > >
