asked on

Server cannot resolve itself in DNS or NSLOOKUP

I have spent 10+ hours trying to find a resolution and I can't do it anymore. I am pulling my hair out trying to troubleshoot this issue more. I have seen similar problems posted and tried several ways to resolve my issue but to no avail...

I have a single Server 2003 R2 with several clients. After a vendor installed ACT on my server I have had DNS Issues. I cannot get the server to resolve itself with DNS and therefore clients were having issues using everything on the network. (I entered manual entries within clients' hosts files to temporarily patch the situation).

I have uninstalled & reinstalled DHCP & DNS, manually recreated the DNS Zones, Netdiag /fix, Edited and reconfigured the cache.dns file, manually entered root hints.

Any help would be greatly appreciated.

Here are the dcdiag results:
Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\OLIVESERVER
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
with DNS
......................... OLIVESERVER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\OLIVESERVER
Starting test: Replications
......................... OLIVESERVER passed test Replications
Starting test: NCSecDesc
......................... OLIVESERVER passed test NCSecDesc
Starting test: NetLogons
......................... OLIVESERVER passed test NetLogons
Starting test: Advertising
......................... OLIVESERVER passed test Advertising
Starting test: KnowsOfRoleHolders
......................... OLIVESERVER passed test KnowsOfRoleHolders
Starting test: RidManager
......................... OLIVESERVER passed test RidManager
Starting test: MachineAccount
......................... OLIVESERVER passed test MachineAccount
Starting test: Services
......................... OLIVESERVER passed test Services
Starting test: ObjectsReplicated
......................... OLIVESERVER passed test ObjectsReplicated
Starting test: frssysvol
......................... OLIVESERVER passed test frssysvol
Starting test: frsevent
......................... OLIVESERVER passed test frsevent
Starting test: kccevent
......................... OLIVESERVER passed test kccevent
Starting test: systemlog
......................... OLIVESERVER passed test systemlog
Starting test: VerifyReferences
......................... OLIVESERVER passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : olivepromo
Starting test: CrossRefValidation
......................... olivepromo passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... olivepromo passed test CheckSDRefDom

Running enterprise tests on : olivepromo.com
Starting test: Intersite
......................... olivepromo.com passed test Intersite
Starting test: FsmoCheck
......................... olivepromo.com passed test FsmoCheck

Here are the netdiag results:
Computer Name: OLIVESERVER
DNS Host Name: oliveserver.olivepromo.com
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 15 Model 67 Stepping 3, AuthenticAMD
List of installed hotfixes :
KB924667-v2
KB925398_WMP64
KB925902
KB927891
KB929123
KB930178
KB931784
KB932168
KB933729
KB933854
KB935839
KB935840
KB936021
KB936782
KB938127
KB938464
KB941569
KB941693
KB943055
KB943460
KB943485
KB944338-v2
KB944653
KB945553
KB946026
KB948496
KB948590
KB948745
KB949014
KB950762
KB950974
KB951066
KB951072-v2
KB951698
KB951746
KB951748
KB952954
KB953838
KB953838-IE7
KB953839
Q147222

Netcard queries test . . . . . . . : Passed

Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : oliveserver
IP Address . . . . . . . . : 192.168.0.3
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.0.1
Primary WINS Server. . . . : 192.168.0.3
Dns Servers. . . . . . . . : 192.168.0.3

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
No remote names have been found.

WINS service test. . . . . : Passed

Global results:

Domain membership test . . . . . . : Passed

NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{3776633C-798E-42FE-9B30-5320138564C3}
1 NetBt transport currently configured.

Autonet address test . . . . . . . : Passed

IP loopback ping test. . . . . . . : Passed

Default gateway test . . . . . . . : Passed

NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.

Winsock test . . . . . . . . . . . : Passed

DNS test . . . . . . . . . . . . . : Failed
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '192.168.0.3'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.

Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{3776633C-798E-42FE-9B30-5320138564C3}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{3776633C-798E-42FE-9B30-5320138564C3}
The browser is bound to 1 NetBt transport.

DC discovery test. . . . . . . . . : Passed

DC list test . . . . . . . . . . . : Passed

Trust relationship test. . . . . . : Skipped

Kerberos test. . . . . . . . . . . : Passed

LDAP test. . . . . . . . . . . . . : Passed

Bindings test. . . . . . . . . . . : Passed

WAN configuration test . . . . . . : Skipped
No active remote access connections.

Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information

The command completed successfully

Here are NSLOOKUP Results:
C:\Documents and Settings\Administrator>nslookup
*** Can't find server name for address 192.168.0.3: Non-existent domain
Default Server: UnKnown
Address: 192.168.0.3

packetguy

Is the DNS service running? Go to Start > My Computer and right click, then select Manage. Then expand Services and Applications and click on Services. Scroll down to DNS Server and make sure its status is "Started" and it's Startup Type is "Automatic".

If the DNS service is running, then you may have encountered one of the known quirks of Win2003 DNS -- it sometimes just quits working for unknown reasons. Usually you can fix it by running the DNS wizard again. In Start > Administrative Tools > Manage Your Server run the DNS setup wizard again. Recreate the Foward and Reverse lookup ranges. Inside the router set the primary DNS to 192.168.0.3, and the secondary DNS to your ISP DNS or some other known recursive DNS server.

In a pinch you can use 4.2.2.1 as a public DNS server for testing, but DO NOT leave it at that setting, because 4.2.2.1 is very heavily used; abusing it may get it shut down.

mkaustubh

Is IPv6 installed on this box if yes then please uninstall it :

netsh interface ipv6 uninstall
We need reboot after this.

OR

How do I disable IPv6?

Navigate to the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
Either create or modify the following DWORD value:
DisabledComponents
Give this registry entry a value of 0xFFFFFFFF and then reboot.

Also make sure that there is no HOST file on the server itself.

Also try and Ping the GUID of the server ,if it resolves to the right IP then its fine,otherwise delete the GUID and restart Netlogon service.

Hope this helps!

getair

ASKER

packetguy:
Is the DNS service running? Go to Start > My Computer and right click, then select Manage. Then expand Services and Applications and click on Services. Scroll down to DNS Server and make sure its status is "Started" and it's Startup Type is "Automatic".

It is running and is set to automatic. The Netlogon service fails with the error # 5781

If the DNS service is running, then you may have encountered one of the known quirks of Win2003 DNS -- it sometimes just quits working for unknown reasons. Usually you can fix it by running the DNS wizard again. In Start > Administrative Tools > Manage Your Server run the DNS setup wizard again. Recreate the Foward and Reverse lookup ranges. Inside the router set the primary DNS to 192.168.0.3, and the secondary DNS to your ISP DNS or some other known recursive DNS server.

I have done this already and it does not create the default _msdsc zone and the issue still exists. I was told to manually create the zone _msdsc and run the netdiag /fix command. Neither of those items resolved the issue. So I went through and manually configured the root hints.

In a pinch you can use 4.2.2.1 as a public DNS server for testing, but DO NOT leave it at that setting, because 4.2.2.1 is very heavily used; abusing it may get it shut down.

I am using DNS Fowarders to OpenDNS's servers which allows my clients to at least browse the web without issues. Only internal is having issues.

getair

ASKER

Is IPv6 installed on this box if yes then please uninstall it :

netsh interface ipv6 uninstall
We need reboot after this.

OR

How do I disable IPv6?

Navigate to the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
Either create or modify the following DWORD value:
DisabledComponents
Give this registry entry a value of 0xFFFFFFFF and then reboot.

IPv6 is not installed

Also make sure that there is no HOST file on the server itself.

It has a host file, but there is nothing in it other than 127.0.0.1 Localhost. Should that file be completely removed? If I delete it will it not just recreate itself?

Also try and Ping the GUID of the server ,if it resolves to the right IP then its fine,otherwise delete the GUID and restart Netlogon service.

How and where do I do this? I cannot ping by server name...

ASKER CERTIFIED SOLUTION

Henrik Johansson

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

getair

ASKER

For the nslookup-error: You're missing the reverselookup for 192.168.0.3 in DNS. Create the reverse zone and runipconfig/registerdns.

Zone was created under reverse lookup zones but when I go into the created NS I try to resolve the IP address but it is unable to resolve the IP on its own. I can manually enter it.

After performing those items and restarting the Net Logon and DNS services I still get this error when performing NSLOOKUP:
Here are NSLOOKUP Results:
C:\Documents and Settings\Administrator>nslookup
*** Can't find server name for address 192.168.0.3: Non-existent domain
Default Server: UnKnown
Address: 192.168.0.3

For the dcdiag-error: Run dcdiag/fix to see if it helps.

Here are the results:
C:\Documents and Settings\Administrator>dcdiag /fix

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\OLIVESERVER
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
with DNS
......................... OLIVESERVER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\OLIVESERVER
Starting test: Replications
......................... OLIVESERVER passed test Replications
Starting test: NCSecDesc
......................... OLIVESERVER passed test NCSecDesc
Starting test: NetLogons
......................... OLIVESERVER passed test NetLogons
Starting test: Advertising
......................... OLIVESERVER passed test Advertising
Starting test: KnowsOfRoleHolders
......................... OLIVESERVER passed test KnowsOfRoleHolders
Starting test: RidManager
......................... OLIVESERVER passed test RidManager
Starting test: MachineAccount
......................... OLIVESERVER passed test MachineAccount
Starting test: Services
......................... OLIVESERVER passed test Services
Starting test: ObjectsReplicated
......................... OLIVESERVER passed test ObjectsReplicated
Starting test: frssysvol
......................... OLIVESERVER passed test frssysvol
Starting test: frsevent
......................... OLIVESERVER passed test frsevent
Starting test: kccevent
......................... OLIVESERVER passed test kccevent
Starting test: systemlog
......................... OLIVESERVER passed test systemlog
Starting test: VerifyReferences
......................... OLIVESERVER passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : olivepromo
Starting test: CrossRefValidation
......................... olivepromo passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... olivepromo passed test CheckSDRefDom

Running enterprise tests on : olivepromo.com
Starting test: Intersite
......................... olivepromo.com passed test Intersite
Starting test: FsmoCheck
......................... olivepromo.com passed test FsmoCheck

C:\Documents and Settings\Administrator>

Ensure that the DNS-zones allow dynamic updates to let the server register itself's records.

Secure and unsecure updates are allowed (for testing purposes).

Henrik Johansson

Can you post a screenshot of the DNS-MMC with focus on the reverse zones?