It's all gone wrong 3 times this week. After some log analysis it was tracked down to a problem with DNS. I had to resort to contacting the company that supplied the 3 servers which have a DNS role as, surprise surprise, The Last Guy had not properly documented how these were set up. The theory was that we have 1 server in charge of DNS, a second one to take over if the first one dies, and a 3rd which was retired. In reality we have 1 in charge, a second running, but no computers are set to look to it should the first one break, and a 3rd one that is fully running and not retired at all. So, all our servers and each DNS server itself is now set to look to the main server 1st, then the secondary one second, and the crap 3rd one as a last resort.
The problem seems to get kicked off at around 8:40 ish for no apparent reason. We'll see what happens tomorrow, but it's entirely rubbish when it does go wrong as no one can get on the computers.
Budget concerns seem to be being addressed and it looks like we may have money next year for most of what we want to do.
The New Technician should be returning to work under some strict rules (once bitten, twice shy)
No comments:
Post a Comment