Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 370
  • Last Modified:

How does DNS work on a LAN w/no server?

We have a single server with a static IP address that acts as a file server.  No DNS, no DHCP.  We have a DLink DIR-655 router as well that does the DHCP.  All the other clients have dynamic IP.

When pinging the server by IP address, there's a response.  When pinging or trying to reach it by hostname, there isn't a response.  All the dynamic clients are working with both their hostnames and IP addresses.

Manually entering in an entry to the host file of a client alleviates the problem of reaching the server via hostname, but any idea why the computer suddenly can't be reached by hostname?  I thought it was the router.  Isn't my router supposed to have a cache for local DNS?
0
epichero22
Asked:
epichero22
2 Solutions
 
John HurstBusiness Consultant (Owner)Commented:
A D-Link is a simple consumer router and you do not have DNS working on your server. So you have no option here but to use the HOSTS file to use hostnames. Your D-Link (and most entry level routers) won't do this.

.... Thinkpads_User
0
 
John HurstBusiness Consultant (Owner)Commented:
If your server is not a domain server, make sure everything is on the same workgroup. Also make sure the server is on the same subnet (it should be).

It occurs to me that if your server *is* a domain server, then you should be able to access it by hostname.

... Thinkpads_User
0
 
epichero22Author Commented:
Well it worked for several months, then two weeks ago, all the clients couldn't reach the server.  So yes, I updated the Host file, and it worked.

I thought the router managed DNS.  Other host names work when you ping them.  What's up with that?
0
2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

 
John HurstBusiness Consultant (Owner)Commented:
Perhaps do a TCP/IP repair on your server. Look up Microsoft Support for your particular server for TCP/IP repair and follow the steps.

Also, simply restarting the server may make it accessible again.

The router is managing external DNS and I don't think that has any effect here.

.... Thinkpads_User
0
 
bfasonCommented:
You are most likely recieving internal name resolution through netbios. It is enabled by default on windows operating systems for backward compatability and provides host name resolution to computers in the same broadcast domain. The router most likely assigns DNS settings to the client via DHCP which are usually the same ones the router receives from the isp.

Quick way to determine is open a command promtp and type "ipconfig /all" on a workstation

Under each adapter you will see the dns server assigned and also see if NetBios over Tcp/ip is enabled.
0
 
AkinsdNetwork AdministratorCommented:
Every home based router runs DHCP and DNS by default. You wouldn't be able to access any website without DNS.

To answer your question; you were using DNS assigned to your router by your ISP. DHCP normally would update DNS entries using dynamically. The router also pulls a DNS suffix from your ISP eg (hsd1.ca.comcast.net.)

Check the domain name on your router. Also run ipconfig /all on any workstation and see what the primary DNS suffix is.

Your server most likely is using a FQDN (Fully Qualified Domain Name) eg. if the dns suffix is "hsd1.ca.comcast.net" and your server host name is epichero22, then the FQDN of your server would be epichero22.hsd1.ca.comcast.net..

That most likely is what the router has for your server in its table. Editing LMHost files (LAN Manager Hosts files)  simply bypasses DNS name look up for that entry. Computers check their host files before querying a DNS server.

Hope that helps
0
 
gsmartinCommented:
As mentioned, NetBIOS is installed by default.  When use try accessing the file server by name in a UNC path this is referred to as a NetBIOS name.  NetBIOS resolution can only happen in anyone of the following three ways:  1) Through WINS, which requires a server running the WINS server service that will dynamically updates the WINS database with NetBIOS/computer names.  2) Resolve NetBIOS/computer names via the local LMhost file on each workstation and server.  This is a manual file that would need to be updated on all systems as systems are added and removed from the network.  3) Resolve NetBIOS names via an elected Master Browser (through the Computer Browser service) within a workgroup or domain.  The Master Browser is typically the highest level/version workstation or server operating system on the network, which can change as systems are added or removed from the network.  Note all systems need to reference the same workgroup/domain name for anyone of the systems to see each-other.

Since you weren't using DNS or Host files then you weren't resolving hostnames, which require FQDN either by pointing systems to a DNS server or by using a local host file on each system.  

My recommendation and preference, if possible, is to promote your file server to a DC and/or add a at least one dedicated Active Directory server to run DNS and DHCP.  This would easily resolve your issues and provide a centralized logon AD services Domain environment.   The systems can then will automatically update DNS bus DDNS; which is configured by default on all systems.  Make sure to add forward lookup DNS servers for external DNS resolution.

As long as DNS is implemented WINS won't be required; assuming you are running Windows 2000 Server or later in Native mode.  Hopefully, something more recent i.e. Windows 2008 R2 or later.
0
 
gsmartinCommented:
Corrections:   Ignore - "use try" in second sentence.  When accessing the file server....

Sorry, for some of the typos created by me an my iPhone.

bus = via  ...when talking about DNS and DDNS
0

Featured Post

Veeam Task Manager for Hyper-V

Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now