2008 DNS MMC in fails to load with error: Access was denied

[guest]

I very unwisely removed and readded the DNS role on my 2008 r2 PDC and cannot get it reconfigured again.

Attempting to access the DNS role from the MMC snap in directly on the server results in error

The server SERVER could not be contacted.
The error was:
Access was denied.
Would you like to add it anyway?
Yes/No

If is choose yes, the server Name is added to the DNS node but I am unable to select "Actions,Configure a DNS Server..." (greyed out)

Any suggestions would be appreciated.

[guest]

I have the same problem, only my problem occurred when I was trying to join FreeNas in domain. The DNS service is started and works properly. In DNS events summary I have error 4000:



Log Name: DNS Server

Source: Microsoft-Windows-DNS-Server-Service

Date: 03.06.2011 13:54:01

Event ID: 4000

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: xxx.xxx.local

Description:

The DNS server was unable to open Active Directory. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code.

For now, AD works fine, I can add or delete user or groups and probably other things, except joining other computers, servers or adding additional DCs, which I have tried as last resort to save my DNS.

[guest]

I’m not quite sure why do you need this information? I’m certain that I have done everything ok in my TCP/IP configurations; anyway, there is it the configuration from the DC/DNS:



C:\>ipconfig -all



Windows IP Configuration



Host Name . . . . . . . . . . . . : XXX

Primary Dns Suffix . . . . . . . : xxx.local

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : xxx.local


Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection

Physical Address. . . . . . . . . : 00-0C-29-DB-F8-C8

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 192.168.236.201(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.236.254

DNS Servers . . . . . . . . . . . : 127.0.0.1

NetBIOS over Tcpip. . . . . . . . : Enabled



Tunnel adapter isatap.{2DA5C272-44E5-4D48-989A-44B45C2A7286}:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes



Tunnel adapter Local Area Connection* 9:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes


In this moment I can’t give you ipconfig from the client, but it was in same IP class, same subnet and DNS was pointed to 192.168.236.201.

The real problem in my situation is that that DNS doesn’t work.

[guest]

I have the EXACT same problem. Happened to me yesterday. Don't know why. But, just out of the blue, the DNS has gone all haywire. I can't configure it. Can't do anything.



I tried "net start DNS" and it says it's already been started.



My ipconfig/all is :


Windows IP Configuration



Host Name . . . . . . . . . . . . : MES-SERVER

Primary Dns Suffix . . . . . . . : meswitchgear.com

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : meswitchgear.com



Ethernet adapter Local Area Connection # 2:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : D-Link DFE-520TX PCI Fast Ethernet Adap

Physical Address. . . . . . . . . : 00-1C-F0-8D-77-D5

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::1450:5db8:60fd:4358%12(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.2.1(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.100

DHCPv6 IAID . . . . . . . . . . . : 301997296

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-AE-A1-95-00-11-95-C1-76-

DNS Servers . . . . . . . . . . . : 192.168.2.100

192.168.2.1

127.0.0.1

NetBIOS over Tcpip. . . . . . . . : Enabled



Tunnel adapter isatap.{6C97421B-7093-4514-8903-96F61FC168EA}:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes



Tunnel adapter Teredo Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1c48:19cd:265a:1eda(Pr

Link-local IPv6 Address . . . . . : fe80::1c48:19cd:265a:1eda%16(Preferred)

Default Gateway . . . . . . . . . : ::

NetBIOS over Tcpip. . . . . . . . : Disabled




I'm looking for a solution too. Will let you know if I get one, but sine I'm no IT engineer, I'm guessing one of you will probably beat me to it.

[guest]

do NOT user the router as DNS server in a domain, remove this one and use ONLY the domain DNS server. After the change run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service.

If you have made this configuration to have internet access either use the root hints from the DNS server or configure the FORWARDERS to your ISPs DNS server in the DNS management console under the server properties.


--------------------------------------------------------------------------------