I had a dns forwarder configured that seems to be choking on a particular server name so I switched to using google's dns as a forwarder (8.8.4.4). When I change that setting in Windows DNS (Server 2008 R2) Do i need to restart the dns service for the change to take effect?
I ask because i can do a nslookup on the name using 8.8.4.4 and it resolves but even with 8.8.4.4 in my forwarders list it will not resolve when i run nslookup on my local DNS server.
I have a Windows Server 2003 SP2 machine with IIS and ADAM SP1. Our software vendor is now requiring windows server 2003 R2 for it's next version and I'm wondering if I will have any issues running the R2 upgrade. I see a lot of Microsoft articles referencing upgrading from 2003 or 2003 SP1 but nothing talking about upgrading to R2 from SP2.
I have a SQL 2005 Std edition server with 5 databases in production, 4 db's are used by web-based apps the 5th is a desktop application. My question is should I perform an in-place upgrade or a side-by-side by creating an sql2008 instance on the same box?
The machine is a VM on vmware and I'm planning on taking a snapshot before the upgrade and having a 'blackout' window during the upgrade so that I could roll back to the snapshot if things go really bad.
Any previous experience and advice is appreciated.