<div>
- look in your dns if this pc is listed in the forward and reverse lookup zon<br />
- During nslookup choose a speficied DNS Server<br />
- check the clients dns server (the right one and the right order)<br />
- make a ipcondif /flushdns and ipconfig /registerdns on this client and your ping client
</div>


- look in your dns if this pc is listed in the forward and reverse lookup zon
- During nslookup choose a speficied DNS Server
- check the clients dns server (the right one and the right order)
- make a ipcondif /flushdns and ipconfig /registerdns on this client and your ping client

<div>
Ok interesting. I have a handful of my desktop machines listed in the reverse lookup zones.<br />
Shouldn't that be created automaticaly when a new machine is added to the domain?<br />
<br />

</div>


Ok interesting. I have a handful of my desktop machines listed in the reverse lookup zones.
Shouldn't that be created automaticaly when a new machine is added to the domain?



<div>
What I mean is out of the 35+ desktop machines I have running in my domain looks like only 6 machines are listed in the reverse lookup zones
</div>


What I mean is out of the 35+ desktop machines I have running in my domain looks like only 6 machines are listed in the reverse lookup zones

<div>
<div class="content wysiwyg-content">
Ok I think this is an easy fix. If I want to do an nslookup on an IP address in my domain I get a Non-existent domain.<br />
<br />
&gt;nslookup &nbsp;10.1.10.3<br />
Server: domain.DNS.com<br />
Address: 10.1.10.98<br />
<br />
*** domain.dns.com can't find 10.1.10.3: Non-existent domain<br />
<br />
however if i ping 10.1.10.3<br />
<br />
Reply from 10.1.10.3: bytes=32 time&lt;1ms TTL=128<br />
<br />
Any ideas what is causing the non nslookup?<br />
<br />
<br />
<br />
<br />

</div>
</div>


Ok I think this is an easy fix. If I want to do an nslookup on an IP address in my domain I get a Non-existent domain.

>nslookup  10.1.10.3
Server: domain.DNS.com
Address: 10.1.10.98

*** domain.dns.com can't find 10.1.10.3: Non-existent domain

however if i ping 10.1.10.3

Reply from 10.1.10.3: bytes=32 time<1ms TTL=128

Any ideas what is causing the non nslookup?






No Nslookup

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.