DNS & DHCP

[rgao]

Hi, there
I'm new in this field,recently I have a questions (related with DNS& DHCP) confused me,could you guys help me get coreect answe?
Q: when we're looking for an address in internet(eg.microsoft.com),Isp's DNS is responsible for name&IP address translation.but when we're looking for another computer "computerA" in our local network,who is responsible for name& ip translation? Local DNS server? since using DHCP,ip address is always changed,how can local DNS server get these updated info?

 

[dredoggg]

Basically, yes, local DNS server is responsible for local name resolution.
As for 'how can local DNS server get these updated info?'
It depends on your setup.
Are you using Windows 2000 DNS?
If so check out this FAQ on how to get DNS running properly in a Win2K environment:

http://www.tek-tips.com/faqs.cfm?spid=950&sfid=2998

The FAQ tells you to have all the local machines use local DNS. When a 2000 machine boots up it registers with the Win2k DNS, much like clients would register with WINS in NT4 environments.

does that help?

 

[yizhar]

HI.

Local (and external) name resolution depends on many factors, for example:
OS of workstations and servers.
Configuration of workstation and servers.

MS Windows workstations will resolve names using all or some of the following:
Cached resolutions.
HOSTS
DNS
LMHOSTS
WINS
Broadcast

But the order is dependant on the OS, configuration, and the application which asked for the ip address - if it uses Winsock or Netbios or other interface.

About DNS - the workstation will use only the first (primary) DNS server configured for it (unless it fails), and does not have an option to use different DNS server for internal versus external host names. However the workstation will try different methods for name resolution.

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[sauce21]

DNS is a tricky matter. The term to remember when working in a Windows 2000 envirionment is DDNS (Dynamic DNS). This is the process of dynamic client registration. When a client pc boots up and receives an IP address it looks for the authoritative name server and registers itself to the DNS. This is the main difference between NT and 2K. In NT the DHCP server would be queried by the DNS server and update it's tables.

You might also look into Bind on a linux platform. You can completely replace the Windows DNS at a fraction of the price. Remember though this choice is only valid if the version of bind you are running supports DDNS. Bind version 8.2 had "claimed" support for DDNS, 8.3 it actually started working, and 8.3 and up are seemless. The other nice thing about this is that it integrates with your Active Directory Domain perfectly. The DHCP gives out an address to the client with the authoritative name server set to the linux box, the linux box gets the client update. The client computer joins itself to the domain if the user has permissions and thats about it.

Sauce