|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by cajx in Windows Networking
Windows 2003 network. Our DNS primary zone disappears after a server reboot. The crazy thing is this server is set up exactly like another, but has this problem. It's a brand new server, so I don't suspect hardware problems (but shouldn't rule them out). Tried installing SP2 to see if that'd fix it, no luck, so we should be 99% up to date on patches.
The reboot I'm doing is a cmd line forced reboot, so maybe that is somehow related. We tried rebooting at 4:01AM and then 2:01AM with the same results. Could there be some goofy DNS process that starts exactly at 1 minute after the hour?
20090824-EE-VQP-74 - Hierarchy / EE_QW_3_20080625
