?
Solved

DNS Windos 2008 Problem

Posted on 2014-01-16
13
Medium Priority
?
229 Views
Last Modified: 2014-08-30
Hello

Here my environment

Single site, single domain, 2 DC
Server 1: Windows 2008 R2 DC, AD, DNS
Server 2: Windows 2008 SP2 DC, AD, DNS, DHCP

Since 4 days, and without any reason, I have the following problem. On server 1 I cannot start normaly DNS. While trying to start DNS it start asking me if the DNS is on this computer or another computer, and when I want to continue DNS start with in RED and nothing appears. There is obviously a DNS problem

I stopped and restarted the DNS services many times (it start normally no error message) but no help the DNS service does start but the DNS application does not start

Of course all DNS related applications and AD does not start. I cannot start AD, sites and services AD, ect...

I can start AD from the second DC since I have no problem from the second DC, DNS is working OK and AD also

I did not rebooted the server 1 yet but I was wondering If there is something else to do before trying a reboot

Thank you
0
Comment
Question by:gadsad
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 3
  • 2
  • +1
13 Comments
 
LVL 18

Expert Comment

by:Emmanuel Adebayo
ID: 39785955
Is there any error in the event logs?

Regards
0
 

Author Comment

by:gadsad
ID: 39785983
Yes many errors regarding DNS and AD telling me that a server cannot be found and that DNS found a critical error from AD

Everything started on the 12/01/14. Before that date the event log was 100% clear

Regards
0
 
LVL 18

Expert Comment

by:Emmanuel Adebayo
ID: 39786024
Please run the command below from the server and paste the result here.

netdiag
0
Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

 
LVL 37

Expert Comment

by:Mahesh
ID: 39786237
There could be lot of reasons for that
Have you multiple NICs (Multihomed) enabled and disconnected on server ?

Does your DNS server points to 127.0.0.1 IP in primary DNS entry in tcp/ip settings? and don't have alternate DNS server set ?

You can do below workaround on affected DC and just reboot and check.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
Value name:  Repl Perform Initial Synchronizations
Value type:  REG_DWORD
Value data: 0

This configuration change is not recommended for use in production environments or in any environment on an ongoing basis. The use of Repl Perform Initial Synchronizations should be used only in critical situations to resolve temporary and specific problems. The default setting should be restored after such problems are resolved.

Check below article for original information source, and possible reasons
http://support.microsoft.com/kb/2001093

Mahesh
0
 
LVL 11

Expert Comment

by:g000se
ID: 39786261
0
 

Author Comment

by:gadsad
ID: 39786275
Netdiag is not a recognized command
DCdiag returns an error and dos not display anything

(DCdiag runs fine without error on the other DC)

Primary DNS = 10.0.0.6 (the IP of the server itself)
Secondary DNS = 10.0.0.3 (the IP of the other DC in the domain)

Should I remove secondary DNS ?

Thanks
0
 
LVL 11

Assisted Solution

by:g000se
g000se earned 2000 total points
ID: 39786293
You may need to restart the server especially if you cannot run dcdiag.  

http://technet.microsoft.com/en-us/library/cc731968.aspx

Can you ping Server 1 from Server 2 by name?
0
 

Author Comment

by:gadsad
ID: 39786301
yes I can

also server 2 from server 1 I can
0
 

Author Comment

by:gadsad
ID: 39786308
Server has not been rebooted from 531 days
Maybe just rebooting will help
0
 
LVL 11

Accepted Solution

by:
g000se earned 2000 total points
ID: 39788457
I concur- I think a reboot will help since it was working before.
0
 

Author Comment

by:gadsad
ID: 39788487
I will reboot the server this sunday and keep you informed
Thanks
0
 

Author Comment

by:gadsad
ID: 39799139
Sorry I forgot to tell you the end of the story

I rebooted the server and the problem was solved

Thank you for all
0
 

Author Closing Comment

by:gadsad
ID: 40294517
thanks
0

Featured Post

Four New Appliances. Same Industry-leading Speeds.

But don't take it from us.  The Firebox M370 is Miercom tested and Miercom approved, outperforming its competitors for stateless and stateful traffic throughput scenarios.  Learn more about the M370, M470, M570 and M670 and find the right solution for your organization today!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Here's a look at newsworthy articles and community happenings during the last month.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses
Course of the Month10 days, 17 hours left to enroll

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question