Share via

Non domain computers not able to resolve names of internal clients

Question

Monday, July 19, 2010 2:37 PM

Dear All

 

I am having a internal DNS server. Forwarder configured. Few Pc are not in domain. For these PC external sites rea resolved by the dns server. But internal hosts are not getting resolved. 

 

Please help.

 

All replies (6)

Monday, July 19, 2010 3:13 PM

Have you checked these non-domain computers to make sure they are configured to point to the internal DNS servers?  If they are not, they will not be able to resolve internal host names.

 

Visit: anITKB.com, an IT Knowledge Base.

Tuesday, July 20, 2010 3:20 AM

Yes all are DHCP clients and getting IP of DNS as configured that of domain members. One more thing those who are not in domain are not able to  create any host record in dns. 

Tuesday, July 20, 2010 6:37 AM

   Are the non AD machines using the FQDN or only the machine name? If they are not domain members they probably do not have the DNS suffix for the domain to add to the machine name to form the FQDN.

 

Bill

Wednesday, July 21, 2010 2:06 AM

Yes all are DHCP clients and getting IP of DNS as configured that of domain members. One more thing those who are not in domain are not able to  create any host record in dns. 

Hi Sumeet,

 

Thanks for posting here.

 

If the dynamic update method of your AD integrated DNS server is “Security Only”, then the client computers which not joined domain will not create and update record in this DNS server.

 

Secure Dynamic Update

 

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

 

And I agree with Bill, please set DNS suffix or check if the domain name could be resolved from no domain joined computer, if yes, please check if the host FQDN could be resolved.

 

And please post “ipconfig /all ”of problematic client computer and DNS server here  for further investigation.

 

Thanks.

 

Tiger Li

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Wednesday, July 21, 2010 6:41 AM

I have tried for with DNS suffix in cleints. But this option is not available with Windows 2008 DHCP options. I can not add it manually to All pcs. Secondarily we are going to use MDT for  deployments  for the new cleints booting from PE can not access the deployments share as they can not resolve the name of the MDT server.

 

ipconfig/all of a Server (Client for dns not a part of domain )

 

-
C:\Users\Administrator>hostname
WSUS-RND-INDIA

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : WSUS-RND-INDIA
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS
 VBD Client)
   Physical Address. . . . . . . . . : E4-1F-13-64-19-52
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.68.31.26(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.68.31.254
   DNS Servers . . . . . . . . . . . : 10.68.31.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{B0B753D5-0EFF-4CA4-9DC8-08DA8A3B7F20}:

   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

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:cf2e:3096:30c9:2b51:f5bb:e0e5(Pref
erred)
   Link-local IPv6 Address . . . . . : fe80::30c9:2b51:f5bb:e0e5%17(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Administrator>nslookup wsus-rnd-india
Server:  ad-master-india.sany.in
Address:  10.68.31.4

*** ad-master-india.sany.in can't find wsus-rnd-india: Server failed

 

The nslookup of the DNS server  is as

 

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : ad-master-india
   Primary Dns Suffix  . . . . . . . : sany.in
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : sany.in

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS
 VBD Client)
   Physical Address. . . . . . . . . : 00-1A-64-C7-05-BC
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.68.31.4(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.68.31.254
   DNS Servers . . . . . . . . . . . : 10.68.31.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

   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* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Administrator>

 

 

Wednesday, July 21, 2010 8:09 AM

Hi sumeet,

Thanks for your update.

you may like to perform the tests below to verfiy if the DNS service on ad-master-india is normal and check if host wsus-rnd-india's reocred is exited.

  1. perform "nslookup wsus-rnd-india" on server ad-master-india
  2. Perform "nslookup ad-master-india" on server wsus-rnd-india

and please post the result here.

Thanks.

Tiger Li

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.