Rudia Plaga
asked on
Client computer can not connect to server 2012r2 domain
I have a test server running 2012r2. I am using it to learn configurations for my 70-410 certification. It's a clean installation. I can not get client computers to connect to the domain. I get this error:
Make sure client can reach DNS server.
This is what I have configured:
Server configured as domain controller
Active directory role installed
DNS role installed
Domain controller and DNS server have the same IP address 192.168.5.7
DHCP role installed
DHCP scope options 15 & 6
I can ping the domain controller from the client computer
I can ping the domain controller with the machine name from the client computer
When I ping the the domain controller with the -a switch from the client computer, it returns the fully qualified domain name of the server.
When I run nslookup from the client computer, it resolves the FQDN and the IP address of the the DNS server.
https://theitbros.com/install-and-configure-dns-server-on-windows-server-2012/
The above link is a tutorial about installing and configuring DNS.
In this tutorial after the DNS role is installed, only the machine name is visible on the left hand side. He then configures the primary zone, then the forward lookup zone, and then the A record.
On my test server, I installed active directory before the DNS role. When I install the DNS role, it looks like the system is installing the forward lookup zone automatically. Is this normal for the system to configure the forward lookup zone automatically? I’m not sure if the primary zone is being configured at all.
I am just learning all this, but I think some DNS files have not been created.
This is the output of the dcdiag test DNS:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>dcd iag /test:dns
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = photonics-dc01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\PH OTONICS-DC 01
Starting test: Connectivity
An error that is usually temporary occurred during DNS host lookup.
Please try again later.
Got error while checking LDAP and RPC connectivity. Please check your
firewall settings.
......................... PHOTONICS-DC01 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\PH OTONICS-DC 01
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... PHOTONICS-DC01 passed test DNS
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : photonics
Running enterprise tests on : photonics.org
Starting test: DNS
Test results for domain controllers:
DC: photonics-dc01.photonics.o rg
Domain: photonics.org
TEST: Basic (Basc)
Error: No LDAP connectivity
Warning: adapter
[00000010] Broadcom NetXtreme Gigabit Ethernet has invalid
DNS server: 192.168.5.7 (PHOTONICS-DC01)
Error: all DNS servers are invalid
No host records (A or AAAA) were found for this DC
Warning: The Active Directory zone on this DC/DNS server was
not found (probably a misconfiguration)
TEST: Forwarders/Root hints (Forw)
Error: Both root hints and forwarders are not configured or
broken. Please make sure at least one of them works.
TEST: Dynamic update (Dyn)
Warning: Failed to add the test record dcdiag-test-record in z
one photonics.org
TEST: Records registration (RReg)
Error: Record registrations cannot be found for all the network
adapters
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 192.168.5.7 (PHOTONICS-DC01)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.photonics.org. fail
ed on the DNS server 192.168.5.7
DNS server: 2001:500:12::d0d (g.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:500:12::d0d
DNS server: 2001:500:1::53 (h.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:500:1::53
DNS server: 2001:500:200::b (b.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:500:200::b
DNS server: 2001:500:2::c (c.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:500:2::c
DNS server: 2001:500:2d::d (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:500:2d::d
DNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:500:2f::f
DNS server: 2001:500:9f::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:500:9f::42
DNS server: 2001:500:a8::e (e.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:500:a8::e
DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:503:ba3e::2:30
DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:503:c27::2:30
DNS server: 2001:7fd::1 (k.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:7fd::1
DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:7fe::53
DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0. 0.0.0.0.0. 0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip 6.arpa failed on the DNS server 2001:dc3::35
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________ __________ __________ __________ _________
Domain: photonics.org
photonics-dc01 PASS FAIL FAIL n/a WARN FAIL n/a
......................... photonics.org failed test DNS
C:\Users\Administrator>
I have also included a screenshot of the DNS file structure. If there is any other information you need, just let me know.
If anyone can assist me with this problem, I would really appreciate it.
Thank you.
Make sure client can reach DNS server.
This is what I have configured:
Server configured as domain controller
Active directory role installed
DNS role installed
Domain controller and DNS server have the same IP address 192.168.5.7
DHCP role installed
DHCP scope options 15 & 6
I can ping the domain controller from the client computer
I can ping the domain controller with the machine name from the client computer
When I ping the the domain controller with the -a switch from the client computer, it returns the fully qualified domain name of the server.
When I run nslookup from the client computer, it resolves the FQDN and the IP address of the the DNS server.
https://theitbros.com/install-and-configure-dns-server-on-windows-server-2012/
The above link is a tutorial about installing and configuring DNS.
In this tutorial after the DNS role is installed, only the machine name is visible on the left hand side. He then configures the primary zone, then the forward lookup zone, and then the A record.
On my test server, I installed active directory before the DNS role. When I install the DNS role, it looks like the system is installing the forward lookup zone automatically. Is this normal for the system to configure the forward lookup zone automatically? I’m not sure if the primary zone is being configured at all.
I am just learning all this, but I think some DNS files have not been created.
This is the output of the dcdiag test DNS:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>dcd
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = photonics-dc01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\PH
Starting test: Connectivity
An error that is usually temporary occurred during DNS host lookup.
Please try again later.
Got error while checking LDAP and RPC connectivity. Please check your
firewall settings.
......................... PHOTONICS-DC01 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\PH
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... PHOTONICS-DC01 passed test DNS
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : photonics
Running enterprise tests on : photonics.org
Starting test: DNS
Test results for domain controllers:
DC: photonics-dc01.photonics.o
Domain: photonics.org
TEST: Basic (Basc)
Error: No LDAP connectivity
Warning: adapter
[00000010] Broadcom NetXtreme Gigabit Ethernet has invalid
DNS server: 192.168.5.7 (PHOTONICS-DC01)
Error: all DNS servers are invalid
No host records (A or AAAA) were found for this DC
Warning: The Active Directory zone on this DC/DNS server was
not found (probably a misconfiguration)
TEST: Forwarders/Root hints (Forw)
Error: Both root hints and forwarders are not configured or
broken. Please make sure at least one of them works.
TEST: Dynamic update (Dyn)
Warning: Failed to add the test record dcdiag-test-record in z
one photonics.org
TEST: Records registration (RReg)
Error: Record registrations cannot be found for all the network
adapters
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 192.168.5.7 (PHOTONICS-DC01)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.photonics.org. fail
ed on the DNS server 192.168.5.7
DNS server: 2001:500:12::d0d (g.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:500:1::53 (h.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:500:200::b (b.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:500:2::c (c.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:500:2d::d (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:500:9f::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:500:a8::e (e.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:7fd::1 (k.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________
Domain: photonics.org
photonics-dc01 PASS FAIL FAIL n/a WARN FAIL n/a
......................... photonics.org failed test DNS
C:\Users\Administrator>
I have also included a screenshot of the DNS file structure. If there is any other information you need, just let me know.
If anyone can assist me with this problem, I would really appreciate it.
Thank you.
ASKER
Yes, I have statically assigned the DNS address in the network adapter card. My DHCP is working. It assigned and IP address to the workstation.
AD relies on DNS, so when you're creating a new domain controller with a new domain, DNS is required, and it creates the default zones (_msdcs.yourdomain.com and yourdomain.com) both as AD-integrated primary zones.
I don't see the screenshot you mentioned.
Can you post output of ipconfig /all and dcdiag /v (best to put them in code blocks)?
I don't see the screenshot you mentioned.
Can you post output of ipconfig /all and dcdiag /v (best to put them in code blocks)?
ASKER
The screen shot is there now. I am totally new to all of this. I am learning as fast as I can. What do you mean by "code blocks"?
We are closing. I will send you the information first thing AM. Thank you for helping me.
We are closing. I will send you the information first thing AM. Thank you for helping me.
No problem.
You can put text into code blocks by using the formatting toolbar at the top of the editing window when you're composing a post. Just highlight the text you want to put in a block, then click CODE.
You can put text into code blocks by using the formatting toolbar at the top of the editing window when you're composing a post. Just highlight the text you want to put in a block, then click CODE.
Looks like this.
Code blocks really help when you post a large amount of text to avoid scrolling (also uses fixed-width font).
It appears that the zone (primary, AD-integrated) for the domain is not present (but _msdcs is). We could just create it, but it is probably better to do some investigation first for things like events that might indicate why the zone isn't there. I'd start off with a general sweep for error or warning events that pertain to DNS or Directory Service.
You could just start over, but if you're trying to learn ways you might fix things, this could be a good opportunity for you.
You could just start over, but if you're trying to learn ways you might fix things, this could be a good opportunity for you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This the output from the dcdiag /test:dns /v
This the ipconfig output from the server
This is the ipconfig output from the client computer
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>dcdiag /v /test:dns
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
* Verifying that the local machine photonics-dc01, is a Directory Server.
Home Server = photonics-dc01
* Connecting to directory service on server photonics-dc01.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=photonics,DC=o
rg,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name
,CN=Sites,CN=Configuration,DC=photonics,DC=org
Getting ISTG and options for the site
* Identifying all servers.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=photonics,DC=o
rg,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS Settings,CN=PHOTONICS-DC01,CN=Serv
ers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=photonics,DC=org
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\PHOTONICS-DC01
Starting test: Connectivity
* Active Directory LDAP Services Check
An error that is usually temporary occurred during DNS host lookup.
Please try again later.
Got error while checking LDAP and RPC connectivity. Please check your
firewall settings.
......................... PHOTONICS-DC01 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\PHOTONICS-DC01
Test omitted by user request: Advertising
Test omitted by user request: CheckSecurityError
Test omitted by user request: CutoffServers
Test omitted by user request: FrsEvent
Test omitted by user request: DFSREvent
Test omitted by user request: SysVolCheck
Test omitted by user request: KccEvent
Test omitted by user request: KnowsOfRoleHolders
Test omitted by user request: MachineAccount
Test omitted by user request: NCSecDesc
Test omitted by user request: NetLogons
Test omitted by user request: ObjectsReplicated
Test omitted by user request: OutboundSecureChannels
Test omitted by user request: Replications
Test omitted by user request: RidManager
Test omitted by user request: Services
Test omitted by user request: SystemLog
Test omitted by user request: Topology
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: VerifyReferences
Test omitted by user request: VerifyReplicas
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
See DNS test in enterprise tests section for results
......................... PHOTONICS-DC01 passed test DNS
Running partition tests on : ForestDnsZones
Test omitted by user request: CheckSDRefDom
Test omitted by user request: CrossRefValidation
Running partition tests on : DomainDnsZones
Test omitted by user request: CheckSDRefDom
Test omitted by user request: CrossRefValidation
Running partition tests on : Schema
Test omitted by user request: CheckSDRefDom
Test omitted by user request: CrossRefValidation
Running partition tests on : Configuration
Test omitted by user request: CheckSDRefDom
Test omitted by user request: CrossRefValidation
Running partition tests on : photonics
Test omitted by user request: CheckSDRefDom
Test omitted by user request: CrossRefValidation
Running enterprise tests on : photonics.org
Starting test: DNS
Test results for domain controllers:
DC: photonics-dc01.photonics.org
Domain: photonics.org
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
Error: No LDAP connectivity
The OS
Microsoft Windows Server 2012 R2 Standard (Service Pack level:
0.0)
is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000010] Broadcom NetXtreme Gigabit Ethernet:
MAC address is D0:67:E5:ED:A1:2D
IP Address is static
IP address: 192.168.5.7
DNS servers:
Warning:
192.168.5.7 (PHOTONICS-DC01) [Invalid]
Warning: adapter
[00000010] Broadcom NetXtreme Gigabit Ethernet has
invalid DNS server: 192.168.5.7 (PHOTONICS-DC01)
Error: all DNS servers are invalid
No host records (A or AAAA) were found for this DC
The SOA record for the Active Directory zone was not found
Warning: The Active Directory zone on this DC/DNS server was
not found (probably a misconfiguration)
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid
(unreachable)]
Name: b.root-servers.net. IP: 2001:500:200::b [Invalid (unr
eachable)]
Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unrea
chable)]
Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unre
achable)]
Name: e.root-servers.net. IP: 2001:500:a8::e [Invalid (unre
achable)]
Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unre
achable)]
Name: g.root-servers.net. IP: 2001:500:12::d0d [Invalid (un
reachable)]
Name: h.root-servers.net. IP: 2001:500:1::53 [Invalid (unre
achable)]
Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreac
hable)]
Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (
unreachable)]
Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreach
able)]
Name: l.root-servers.net. IP: 2001:500:9f::42 [Invalid (unr
eachable)]
Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreac
hable)]
Error: Both root hints and forwarders are not configured or
broken. Please make sure at least one of them works.
TEST: Dynamic update (Dyn)
Warning: Failed to add the test record dcdiag-test-record in z
one photonics.org
[Error details: 9002 (Type: Win32 - Description: DNS server fa
ilure.)]
Test record dcdiag-test-record deleted successfully in zone ph
otonics.org
TEST: Records registration (RReg)
Error: Record registrations cannot be found for all the network
adapters
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 192.168.5.7 (PHOTONICS-DC01)
1 test failure on this DNS server
Name resolution is not functional. _ldap._tcp.photonics.org. fail
ed on the DNS server 192.168.5.7
[Error details: 9002 (Type: Win32 - Description: DNS server failu
re.)]
DNS server: 2001:500:12::d0d (g.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:12::d0d
[Error details: 1460 (Type: Win32 - Description: This operation returne
d because the timeout period expired.)]
DNS server: 2001:500:1::53 (h.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:1::53
[Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:200::b (b.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:200::b
[Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:2::c (c.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2::c
[Error details: 1460 (Type: Win32 - Description: This operation returned b
ecause the timeout period expired.)]
DNS server: 2001:500:2d::d (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2d::d
[Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2f::f
[Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:9f::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:9f::42
[Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:a8::e (e.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:a8::e
[Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:ba3e::2:30
[Error details: 1460 (Type: Win32 - Description: This operation retu
rned because the timeout period expired.)]
DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:c27::2:30
[Error details: 1460 (Type: Win32 - Description: This operation retur
ned because the timeout period expired.)]
DNS server: 2001:7fd::1 (k.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fd::1
[Error details: 1460 (Type: Win32 - Description: This operation returned bec
ause the timeout period expired.)]
DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fe::53
[Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]
DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:dc3::35
[Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
_________________________________________________________________
Domain: photonics.org
photonics-dc01 PASS FAIL FAIL n/a WARN FAIL n/a
......................... photonics.org failed test DNS
Test omitted by user request: LocatorCheck
Test omitted by user request: Intersite
C:\Users\Administrator>
This the ipconfig output from the server
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>
C:\Users\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : photonics-dc01
Primary Dns Suffix . . . . . . . : photonics.org
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : photonics.org
Ethernet adapter Ethernet 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 68-1C-A2-12-91-26
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : D0-67-E5-ED-A1-2D
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.5.7(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.5.7
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{1D6DF34A-812B-4606-8179-4A1B5ABE620E}:
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 isatap.{8460C284-A455-4514-AD4A-1BDD52356436}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\Administrator>
This is the ipconfig output from the client computer
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : clay-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : photonics.org
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 1C-65-9D-AB-A5-39
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : photonics.org
Description . . . . . . . . . . . : Intel(R) 82577LM Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 5C-26-0A-23-EA-14
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b49b:512b:abad:782d%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.5.17(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, July 26, 2018 2:31:58 PM
Lease Expires . . . . . . . . . . : Tuesday, April 20, 2021 2:31:57 PM
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.5.7
DHCPv6 IAID . . . . . . . . . . . : 291251722
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-04-B3-E3-5C-26-0A-23-EA-14
DNS Servers . . . . . . . . . . . : 192.168.5.7
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.photonics.org:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : photonics.org
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{31A8CE15-485C-424D-85C2-88F0D7F648C7}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
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
Tunnel adapter isatap.{13989F9C-CAAD-4394-98D8-0E1A68FE5C31}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Windows\System32>
ASKER
Jeff Glover,
Yes, The DNS server is pointing to itself. The domain controller IP is:192.168.5.7
The DNS server IP is 192.168.5.7
I assume I should delete the photonics.org first, then create the zone again? What sub folder do I create the A record in? Yes, the client computer NIC DNS is statically set to 192.168.5.7
I’ll try it. Thank you for your help.
Yes, The DNS server is pointing to itself. The domain controller IP is:192.168.5.7
The DNS server IP is 192.168.5.7
I assume I should delete the photonics.org first, then create the zone again? What sub folder do I create the A record in? Yes, the client computer NIC DNS is statically set to 192.168.5.7
I’ll try it. Thank you for your help.
I guess the question here is, Is the screenshot accurate now. In your Forward Lookup Zones, do you have a Zone called photonics.org along with the msdcs.photonics.org zone or is it just how it looks, only the _msdcs zone? If the main zone is not created, then yes. Just create it. when you do, it will have a ns record in it. Create the A record there in the photonics.org folder.
And to answer your question about when to do it, I have found that with Server 2012(R2) it is best to install DNS first get it working and then do AD. If you installed AD and then installed DNS, You will have to make the zone manually.
And to answer your question about when to do it, I have found that with Server 2012(R2) it is best to install DNS first get it working and then do AD. If you installed AD and then installed DNS, You will have to make the zone manually.
ASKER
Yes!! Your instructions worked!! Thank you! Do you know what could have caused the error? This is a clean installation, it was never connected to another server. I would like to understand what was wrong so I can fix this if it happens on a future installation.
Thank you again.
Thank you again.
ASKER
Yes, when I created the photonics.org zone, it created the _msdcs folder and all the associated sub folders.
right-click the network adapter>select IP v4> click properties> Use the following DNS server addresses enter the IP of the DNS server
This can also be done via DHCP where the DNS server IPs are automatically populated on your workstations