Name resolving in domain

  • Thread starter Thread starter Ed
  • Start date Start date
E

Ed

Hi all,

I have a question about name resolving.
We are using Active Directory and have a domain, let's say it is
mydomain.com. For member server of the domain we can resolve names with the
DNS in our domain. We also have a few servers that are workgroup servers.
However name resolving is not working 100% with these workgroup servers. For
example, if we have the following two host records :

hostA 10.1.1.1
hostB 10.1.1.2

If I use ping command in one of our member server in AD the pings are
successful. However if I use ping command in the workgroup server, hostA can
be reached by ping but hostB will be shown as unknown host. I double checked
this in our DNS and both are valid records.
Does anyone have idea?
Thx
 
In
Ed said:
Hi all,

I have a question about name resolving.
We are using Active Directory and have a domain, let's say it is
mydomain.com. For member server of the domain we can resolve names
with the DNS in our domain. We also have a few servers that are
workgroup servers. However name resolving is not working 100% with
these workgroup servers. For example, if we have the following two
host records :

hostA 10.1.1.1
hostB 10.1.1.2

If I use ping command in one of our member server in AD the pings are
successful. However if I use ping command in the workgroup server,
hostA can be reached by ping but hostB will be shown as unknown host.
I double checked this in our DNS and both are valid records.
Does anyone have idea?
Thx
Click to expand...


We'll need more info...

Pinging by single name or FQDN makes a difference. If by single name, it
uses the search suffix. If pinging by single name and the machine is just a
workgroup machine without a Primary DNS Suffix, which then means the search
suffix is blank, then it will try to use only NetBIOS and if that is not the
NetBIOS name, then unknown host will be your result.

So.......

1. How are you pinging?

ping hostb
ping hosta
ping hosta.mydomain.com
ping hostb.mydomain.com

Which ones work above on which machine?

2. Search suffix on machines?

3. What DNS addresses are on the machines?

4. Please provide an Unedited ipconfig /all from the two servers you're
trying this from (the member server and the non-member server). This will
give us a solid view of your config for diagnosing.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Here is what I've got so far. Thanks.

"Ace Fekay [MVP]"
In


We'll need more info...

Pinging by single name or FQDN makes a difference. If by single name, it
uses the search suffix. If pinging by single name and the machine is just a
workgroup machine without a Primary DNS Suffix, which then means the search
suffix is blank, then it will try to use only NetBIOS and if that is not the
NetBIOS name, then unknown host will be your result.

So.......

1. How are you pinging?

ping hostb
ping hosta
ping hosta.mydomain.com
ping hostb.mydomain.com

Which ones work above on which machine?
Click to expand...
Pinging with the 3rd and 4th work fine.... but not the first two
2. Search suffix on machines?
Click to expand...
I think none on both machines.
3. What DNS addresses are on the machines?
Click to expand...
the local DNS computer that we have
4. Please provide an Unedited ipconfig /all from the two servers you're
trying this from (the member server and the non-member server). This will
give us a solid view of your config for diagnosing.

--
Click to expand...

from a non-member server :
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : HKGFIN01
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Server Adapter
Physical Address. . . . . . . . . : 00-02-B3-9D-7C-16
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.88.16
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.88.1
DNS Servers . . . . . . . . . . . : 192.168.88.10

From a member server :
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : hkgfp01
Primary DNS Suffix . . . . . . . : eastpointhk.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : eastpointhk.com

Ethernet adapter Intel Pro 1000 Port 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Server
Adapter #2
Physical Address. . . . . . . . . : 00-07-E9-09-16-99
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.88.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.88.1
DNS Servers . . . . . . . . . . . : 192.168.88.15
192.168.88.10
 
In
Ed said:
Here is what I've got so far. Thanks.

Pinging with the 3rd and 4th work fine.... but not the first two
I think none on both machines.

the local DNS computer that we have


from a non-member server :
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : HKGFIN01
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Server
Adapter Physical Address. . . . . . . . . : 00-02-B3-9D-7C-16
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.88.16
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.88.1
DNS Servers . . . . . . . . . . . : 192.168.88.10

From a member server :
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : hkgfp01
Primary DNS Suffix . . . . . . . : eastpointhk.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : eastpointhk.com

Ethernet adapter Intel Pro 1000 Port 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port
Server Adapter #2
Physical Address. . . . . . . . . : 00-07-E9-09-16-99
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.88.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.88.1
DNS Servers . . . . . . . . . . . : 192.168.88.15
192.168.88.10
Click to expand...


What is your internal AD DNS domain name? Is it eastpointhk.com? I'm going
to assume so at this point...

Apparently it's due to not having a search suffix. Pinging by single name,
the DNS resolver will suffix your search suffix. If there is no search
suffix, it will look at hosts file first, then LMHOSTS then broadcast it as
a NetBIOS name (computer name). If not found as a NetBIOS name on your
subnet, then you'll get the host unknown message.

On the machine that's a member server, then it will suffix eastpointhk.com
(because that is it's search suffix) and ask DNS for that name,
hosta.eastpointhk.com or hostb.eastpointhk.com. If either one doesn't exist
under the eastpointhk.com zone name in YOUR DNS, then you'll get the host
not found message.

On the machine that is not a member server, it has no search suffix. So
therefore it's treating it as a NetBIOS name (as a computer name). If that
computer doesn't exist with that name on your subnet, then host unknown msg.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Thanks, Ace.

It looks like I have to add the search suffix in those non-member servers in
our domain. What if later those computers are joining the domain? Would I
need to manually remove the search suffix? If not removed would the DNS
resolve the computer as pc.domain.com.domain.com?

Thought this is a rather stupid question. Sorry.
Ed

"Ace Fekay [MVP]"
 
In
Ed said:
Thanks, Ace.

It looks like I have to add the search suffix in those non-member
servers in our domain. What if later those computers are joining the
domain? Would I need to manually remove the search suffix? If not
removed would the DNS resolve the computer as
pc.domain.com.domain.com?

Thought this is a rather stupid question. Sorry.
Ed
Click to expand...

Nah, not a stupid question. If I remember correctly, the manual ones you
enter will remain. So if that's correct, you'll need to remove them, if yhou
don't want them.

:-)


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top