![[SJF Logo]](../../images/sjflogo.gif)
I'm in the throes of rebuilding my main Linux box after the motherboard & CPU melted down, and it was the primary nameserver for my network. This means that the Win2000 box that I use as my main workstation has no DNS, so I have to point it to some other system. Though with Win2000 Microsoft has made it so that you don't have to reboot when changing the IP address, you do have to reboot after changing the namserver. This is exceptionally lame.
But it turns out that it's possible to get around this by making the change in Network Properties, then stopping and starting the "DNS Client" service. Once can do this either from the control panel or by going to a command prompt and typing
C> net stop "dns client" C> net start "dns client"
This is unbelievably lame of Microsoft. There are enough areas in Windows that legitimately require a reboot (as in: "inherent in the current design for whatever reason", not "impossible to fix") that they really ought to go out of their way to avoiding requiring reboots when it's not really necessary.
This could be done automatically with a mutex or a Registry Change Event.
Duh.
Posted by Steve at October 25, 2003 09:35 PM | TrackBack:::NEWS FLASH:::
We now have conformation that Unixwiz finds Microsoft Windows lame, as readers around the world are left shocked and befuddled, what news will tommarro bring..stay tuned...
Microsoft being lame is unbelieveable? Ha! I've believed that for years. Welcome to the club. ;-)
Signed,
A Smug Mac OS X User
Posted by: MTS on October 27, 2003 10:21 AMAnd he's a Microsoft MVP too...;-)
Posted by: Techie2000 on October 31, 2003 03:58 PMActually, is there a reason for the DNS client service to be run at all? I have grown a habit of stopping it on any Win2K/XP installation that goes through my hands.
Okay, so I may be a bit biased: there are no Windows machines in any of my networks that are connected directly to the Internet, all of them are parts of LAN's and such, and all of them have a "real" DNS resolving cache available nearby. The Win2K DNS client service may be useful for dial-up, DSL, etc customers with no resolving caches in the immediate vicinity, but other than that, is there a reason to use it?
Posted by: Peter Pentchev on December 14, 2003 11:55 PM