[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

resolve ip address to hostname

Hi,

Presently I have a windows 2000 pro edition, it's running win route lite for sharing internet(this is our gateway).
I need to have something like a dns server running in that machine(resolving ip to hostname).
The win route lite has a feature called forwarding dns request, which doesn't help.
Netbios is turn off on all the client workstations.
I've tried to use the host file on the gateway seems the client workstations isn't resolving hostnames only domain names.
example
1.1.1.1        www.domainname.com   <-----------it can resolve this record
2.2.2.2         hostname                        <-----------it doesn't resolve this (for client workstations)

how to resolve ip address to hostname?


Thanks,
0
lynnton
Asked:
lynnton
  • 8
  • 6
  • 4
  • +2
1 Solution
 
DbaylissnzCommented:
I sujest you read this KB carefully, it explains the name resolution order
http://support.microsoft.com/kb/172218/EN-US/

Please advise if this is useful

0
 
lynntonAuthor Commented:
Dbaylissnz,

Sad to say, it wasn't usefull.

Thanks,
Lynnton
0
 
rhandelsCommented:
Maybe you could use the FQDN for resolvance... like

2.2.2.2 --> hostname.domainname.com

Else, try adding the host names to the LMHOSTS file. Also, try to see if the hosts file is called hosts, not hosts.sam..
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
lynntonAuthor Commented:
rhandels,

I've tried placing a record to lmhost and rebooting the gateway.
2.2.2.2 hostname #PRE

it work perfectly on the gateway, unfortunately the client workstation it not resolving the hostname.

by the way what's the difference between hosts.sam and hosts files?

Thanks,
Lynnton
0
 
rhandelsCommented:
Normally, the hosts file is created as a sample file (not used) and then it's called hosts.sam(ple), then all settings within the hosts file don't work...

Is this hostname within the domain?? Within the same subnet as the workstations??
0
 
lynntonAuthor Commented:
rhandels,

what is ple?

there's no domain.
network subnetting is all good. yes same subnet.

Thanks,
Lynnton
0
 
rhandelsCommented:
Meant to compelet the word sample....

So the hostname should be pointing to the default gatewqay i guess??

Why don't you enable NetBios over TCP/IP?? It works like a charme, specially for these kind of small networks...
0
 
lynntonAuthor Commented:
rhandels,

The client workstation's dns are pointing to the gateway server.
enabling netbios would generate lots of network traffic and bandwidth. all those arp resolution isn't good.

Thanks,
Lynnton
0
 
rhandelsCommented:
>>enabling netbios would generate lots of network traffic and bandwidth. all those arp resolution isn't good.<<

Depends on how many workstation you have. The broadcast traffic will only be within your own site.. Normally the hosts resolvance should work, but if it doesn't (and you added the items correctly, for as far as i can see) and you don't have a DNS server, i guess this is you only option apart from installing a DNS server within the workgroup....
0
 
adamdrayerCommented:
NetBIOS doesn't generate lots of network traffic.  I wouldn't recommend it over a 384k WAN, but you're probably running at 300x that.  If you have so many computers that you'll even notice layer2 broadcasts, then you should be using a Windows Server product anyway.

Losts of times, records in the HOSTS file pointing to hosted websites cannot be resolved.  This has to do with the way the sites like earthlink host them.

HOSTS is for dns and need to point to FQDNs like www.domain.com.  LMHOSTS is for NetBIOS names and need to point to client computer names.

Also, I think you are trying to add a record to the HOSTS file of the gateway, and use it to resolve names on the client.  You cannot do this.  HOSTS and LMHOSTS only allow name resolution to occur on the computer they are located on.  If you would like to use one computer to resolve names for another, you need a DNS or WINS server, or you need to enable broadcast resolution.
0
 
lynntonAuthor Commented:
adamdrayer,

Hmm, it's working using hosts file.
ONLY for domain names (FQDN)

Do you know a software that is only for dns(hostname to ip)? so that i could install it on the gateway.

Thanks,
Lynnton
0
 
adamdrayerCommented:
I'm not sure what you are asking.  Sorry.  DNS should always be thought of in the form of hostname.domain.tld like 'server1.mydomain.net'

the DNS hostname is normally the same as the Computername.  You can't resolve DNS hostnames without the domain attached.  If software lets you do this, then it is appending the domain name and tld for you without your knowledge.  It has to do with determining which is the authoritative zone for your particular request.  Fortunately, NetBIOS names also use the computername.  This means that the NetBIOS name and DNS Hostname are usually identical.

Therefore if you want to resolve a DNS Hostname, you need to append the domain suffix usually, or just resolve the NetBIOS name instead.
0
 
DbaylissnzCommented:
lynnton,

This seems to be going around in circles, Can you please answer the following for the good people here:

1.. What is your prefered method of name resolution for this.
2.. Why do you not wish to use Netbios, DNS Server, etc?
3.. How do you see long term upgradability, and compatability, not to mention the time it will take to resolve issues.

The link I presented earilier laid out the normal methods of name resolution, it appears that you wish to use local hosts to do this thus removing network traffic (minimal), this method is over complicated and time consuming as growth of network = more time managing this.

Unless you need a super secure network (and even they use things like DHCP, DNS!) I would stick to the normal tools, there is more than enough things that can be tweaked in the network, dont make your life difficult by doing stuff like this.
0
 
campbelcCommented:
Within our corporate environment, where I'm positive we have 1000's of times more workstations then yourself, we use DHCP, DNS, WINs etc. Broadcasts normally are of little or no concern if the IP addressing is done properly and you aren't using hubs (still not much of a concern).

I would have to agree with Dbaylissnz, that for long term growth and managability, DNS would be the route to go. Manage the name resolution in one location and be done with it.
0
 
campbelcCommented:
Ok, some more information:

I think, I stress the think part, what you are trying to do is this.

You would like to assign full qualified domain names, but not have to always type out the full name?

How I do it here is:
BCRMLWS01.rml.bc.somehospital.org --> 10.10.104.x

But our internal users can either go after the FQDN or bcrmlws01.

try adding the domain information, in my case, rml.bc.somehospital.org in Local Area Connections, right click and select properties on Local Area Connection,  Click on properties, select IP, click on properties, click on advanced, click on DNS, and enter it in the field for DNS suffix for this connection.

What this will do is each time your uses enter the FQDN it will of course work, but when they just type BCRMLWS01 the local IP connection will attach the DNS suffix automatically.
0
 
lynntonAuthor Commented:
campbelc,

Your setup works like a charm. ( i can resolve hostname to ip now)
I do have FQDN in the host file of the gateway and clients can resolve it.
example
dell.mailserver.com

when doing your setup (adding primary dns suffix order) how does the name gets resolved?
i added dell.mailserver.com to primary dns suffix in tcp/ip
and how does it differ from adding DNS suffixes in the DNS tab.

by the way i'm searching for something that can be installed in the gateway, so that we wouldn't have to update all the workstations.

Thanks,
Lynnton

0
 
lynntonAuthor Commented:
campblec,

Hold on, I think your on to something here. GREAT IDEA !!!

Let me try to add primary DNS suffix on the GATEWAY then see if the clients can resolve it (hostname to IP).

1. does this mean everytime there's a request for DELL (hostname) the gateway will forward it to DELL.mailserver.com?

or all of the client request for name resolution will go to the primary DNS suffix?   <---this is not good it will cause flooding

2. how does this differ from adding DNS suffix rather than adding Primary DNS suffix?

Thanks,
Lynnton
0
 
campbelcCommented:
Well the "Append primary and connection specific DNS suffixes" will allow you to add many differnet DNS suffixes if you have many internal domains but for some reason don't want to use a DNS server.

The "DNS suffix for this connection" will just add the dns suffix by default for your one domain. If you have more then one domain say mail.domain1.com and mail.domain2.com then you would need to add all the domain suffixes in the "Append these suffixes in this order" piece.

What is the main reasoning for NOT having a DNS system service running?
0
 
campbelcCommented:
Ok, in reading your last comment, please answer this.

If you leave the hostname off the FQDN, what is the main domain name?

Really though, super easy way to do this is to setup DHCP and DNS, then can have DHCP assign all your DNS settings when they are assigned their IP addresses.

I do have a doc for setting up a basic DHCP and DNS configuration. Little to no overhead on the server and can have it setup in less then 5 mintues.
0
 
campbelcCommented:
Lynnton, I keep hearing you use the word flooding, but if you even have a halfway decent network, flooding isn't an issue. I guess unless your running a network over BNC still.

Even running on 10 MB CAT5 copper I don't think this is a real concern unless you have 100's of workstations.
0
 
lynntonAuthor Commented:
campbelc,

as posted earlier...

I'll this approach tomorrow. I have a good feeling it will work as you've planned.

Thanks,
Lynnton


_______________________________________
rhandels,

The client workstation's dns are pointing to the gateway server.
enabling netbios would generate lots of network traffic and bandwidth. all those arp resolution isn't good.

Thanks,
Lynnton
________________________________________
0
 
campbelcCommented:
Thanks and good luck.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 8
  • 6
  • 4
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now