kcn
asked on
NetBIOS Name and Host Name Resolution
Please correct my statement if my understanding are wrong .
(a) The clients after Window 2000 , able to dynamic update their host name to DDNS through their DHCP Server ( not DHCP client ) ??
(b) Window Server 2003 able to dynamic update its host name to DDNS through DHCP client ( not DHCP server ) even its TCP/IP Statically configured ???
(c) If the Window Server 2003 only has server name ( not FQDN ) , it can register its "server name " with DDNS when WINS server is not available ??
(d) Can XP Pro client dynamically register its computer name ( not FQDN ) to DDNS Server if the WINS Server is not available ???? Through DHCP client or DHCP Server ??
(e) DNS can resolve FQDN as well as NetBIOS name ( computer name ) ???
(a) The clients after Window 2000 , able to dynamic update their host name to DDNS through their DHCP Server ( not DHCP client ) ??
(b) Window Server 2003 able to dynamic update its host name to DDNS through DHCP client ( not DHCP server ) even its TCP/IP Statically configured ???
(c) If the Window Server 2003 only has server name ( not FQDN ) , it can register its "server name " with DDNS when WINS server is not available ??
(d) Can XP Pro client dynamically register its computer name ( not FQDN ) to DDNS Server if the WINS Server is not available ???? Through DHCP client or DHCP Server ??
(e) DNS can resolve FQDN as well as NetBIOS name ( computer name ) ???
A. Correct, except Windows 2000 could do this too.
B. Correct, providing the client's network adapter is set to register it's host name in DNS (default).
C. Not really. DNS names are based on a hierarchy, not a flat name space. DNS names can be set to be resolved through NetBIOS in the DNS server settings.
D. No
E. Sort of
B. Correct, providing the client's network adapter is set to register it's host name in DNS (default).
C. Not really. DNS names are based on a hierarchy, not a flat name space. DNS names can be set to be resolved through NetBIOS in the DNS server settings.
D. No
E. Sort of
ASKER
Firebar ,
in workstation or server , under TCP/IP properites > advanced button > WINS Tab > enable NetBIOS over TCP/IP .
This "Enable NetBIOS over TCP/IP " is for what purpose ???
in workstation or server , under TCP/IP properites > advanced button > WINS Tab > enable NetBIOS over TCP/IP .
This "Enable NetBIOS over TCP/IP " is for what purpose ???
To allow NetBIOS name requests to be sent through DNS.
ASKER
Hi Firebar ,
So , this "enable NetBIOS over TCP/IP " is request DNS Server to resolve NetBIOS Name ( computer name ) to IP Address ?? Am I right ?
So , this "enable NetBIOS over TCP/IP " is request DNS Server to resolve NetBIOS Name ( computer name ) to IP Address ?? Am I right ?
That's right
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Chris ,
So, my (a) question is incorrect too because client running 2000 and after can dynamic register their
hostname (NOT single label name ) to DDNS through their DHCP client . Please confirm (a)
In short , all client running 2000 and after can dynamically register their hostname to DDNS even they configured as static IP ?? ==> Please confirm this statement ..
Append Primary DNS Suffix at DNS Tab ( TCP/IP properties > advanced button > DNS Tab ) is the ones will "add" Primary DNS Suffix (domain name ) on the single label name and make the client with single label name can register with DNS server ??? If the single label name is AA and Primary DNS Suffix is BB.com , then Append Primary DNS Suffix will make it as AA.BB.com ==> Please comment this statement .
Last question :- "enable NetBIOS over TCP/IP " is for what purpose ????
So, my (a) question is incorrect too because client running 2000 and after can dynamic register their
hostname (NOT single label name ) to DDNS through their DHCP client . Please confirm (a)
In short , all client running 2000 and after can dynamically register their hostname to DDNS even they configured as static IP ?? ==> Please confirm this statement ..
Append Primary DNS Suffix at DNS Tab ( TCP/IP properties > advanced button > DNS Tab ) is the ones will "add" Primary DNS Suffix (domain name ) on the single label name and make the client with single label name can register with DNS server ??? If the single label name is AA and Primary DNS Suffix is BB.com , then Append Primary DNS Suffix will make it as AA.BB.com ==> Please comment this statement .
Last question :- "enable NetBIOS over TCP/IP " is for what purpose ????
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Chris ,
Before I make thing confuse let me understand one thing first :-
1) At DNS Tab ( TCP/IP Properties > advanced Tab ) , can we divide "Append Primary and connection specifix DNS siffix " into 2 sentenses as such "Append Primary DNS Suffix " & "Append Connection Specific DNS Suffix " ??? If can , please answer (2) and (3) too .
2) Setting "Append Primary DNS SuffiX " on XP Client machine is for what purpose ??
3) Setting "Append Connection Specific DNS Suffix " on XP Client machine is for what purpose ??
Thanks .
Before I make thing confuse let me understand one thing first :-
1) At DNS Tab ( TCP/IP Properties > advanced Tab ) , can we divide "Append Primary and connection specifix DNS siffix " into 2 sentenses as such "Append Primary DNS Suffix " & "Append Connection Specific DNS Suffix " ??? If can , please answer (2) and (3) too .
2) Setting "Append Primary DNS SuffiX " on XP Client machine is for what purpose ??
3) Setting "Append Connection Specific DNS Suffix " on XP Client machine is for what purpose ??
Thanks .
2. If the XP computer is joined to a Windows domain, the DNS name for that domain is set as the primary DNS suffix. This option allows one to specify a DNS suffix other than the domain's DNS suffix as the primary.
More information on XP's interaction with DNS can be found here; http://support.microsoft.com/kb/305553
More information on XP's interaction with DNS can be found here; http://support.microsoft.com/kb/305553
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Chris ,
Your comment : "In 1 the Primary DNS Suffix will be appended to the query, the computer will ask DNS for "computername.domain.com",
So, the "computername" will get the name resolution from DNS server even it is only single label name ??? ==> please confirm this statement
Your comment : "In 1 the Primary DNS Suffix will be appended to the query, the computer will ask DNS for "computername.domain.com",
So, the "computername" will get the name resolution from DNS server even it is only single label name ??? ==> please confirm this statement
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Good , above first question is answered ..
Come to your previous comment on 2nd question "The Connection specific suffix comes in to play when that connection is used (instead of for all connections). It is used in the same as the Primary DNS Suffix otherwise, it helps build a query up to send to DNS."
"when that connection is used .. " which connection .. I am confused ...
Come to your previous comment on 2nd question "The Connection specific suffix comes in to play when that connection is used (instead of for all connections). It is used in the same as the Primary DNS Suffix otherwise, it helps build a query up to send to DNS."
"when that connection is used .. " which connection .. I am confused ...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
In TCP/IP properties > Advanced Tab > DNS Tab >
DNS suffix for this connection ( )
( / ) Register this connection's address in DNS
( ) Use this connection's DNS suffix in DNS registration
How to set above stuffs , anything to do with "connection specfic DNS suffix " ??
I really like to know how to use above stuffs .. Please teach ...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
As I know , for XP Client wit single label computer name , it will get the name resolution as below order :
WINS
Broadcast
DNS
So, it will use broadcast to resolve its single label name first before look for DNS server help , am I right ?
The order depends on the client (operating system), but you'll normally get these for Single-Label names:
Hosts
LMHosts
DNS
WINS
Broadcast
Or something very close to that.
Chris
windows server 2003/XP:
hostname resolution process in order:
1.client cache /hosts file
2.DNS
3.Netbios name cache
4.wins
5. broadcast.
6.lmhosts
hostname resolution process in order:
1.client cache /hosts file
2.DNS
3.Netbios name cache
4.wins
5. broadcast.
6.lmhosts
ASKER
sulimanw ,
your hostname resolution process in order whether is similar to SINGLE LABEL name resolution process in order ??
Please confirm . Because I am asking Single Label Name resolution order .
Thanks .
your hostname resolution process in order whether is similar to SINGLE LABEL name resolution process in order ??
Please confirm . Because I am asking Single Label Name resolution order .
Thanks .
ASKER
From this link
http://www.comptechdoc.org/os/windows/wintcp/wtcpname.html ...
to me it look like for Window Client with Single Label Name , if go for single label name resolution , the "Broadcast" will come early before go for DNS help ( default setting in window client ) ..
Please help to confirm this .. Thanks.
http://www.comptechdoc.org/os/windows/wintcp/wtcpname.html ...
to me it look like for Window Client with Single Label Name , if go for single label name resolution , the "Broadcast" will come early before go for DNS help ( default setting in window client ) ..
Please help to confirm this .. Thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Apologies, Hosts is not missed, they do state that it is loaded into the DNS Client Resolver cache, meaning it is checked at the same time as 2.
Chris
ASKER
Chris ,
Sorry , from the link you provided , it look to me it is discussing about Hostname resolution instead of Single Label Name resolution ???
I thought hostname is refered as FQDN and NetBios Name is referred as computer name ( single label name ) ???
Sorry , from the link you provided , it look to me it is discussing about Hostname resolution instead of Single Label Name resolution ???
I thought hostname is refered as FQDN and NetBios Name is referred as computer name ( single label name ) ???
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I got it after read one more time ...
Thanks Chris and everyone ...
Thanks Chris and everyone ...
No problem :)
Chris
I think I earned an assist here
http://support.microsoft.com/kb/816592