Re: Name resolution for local names using DHCP
- From: Unruh <unruh-spam@xxxxxxxxxxxxxx>
- Date: Mon, 17 Dec 2007 22:20:13 GMT
Robert Harris <robert.f.harris@xxxxxxxxxxxxxxxx> writes:
Charles Russell wrote:
Unruh wrote:I know I'm jumping in late, but static addresses are not a terribly good
Charles Russell <NOSPAM@xxxxxxxxxxxxx> writes:
Unruh wrote:
Charles Russell <NOSPAM@xxxxxxxxxxxxx> writes:Yes, it does. But why should static IP addresses be required, when
Charles Russell wrote:Some routers allow you to tell the dhcp service on the router to
I can't figure out how to get name resolution for computers on myThanks for the responses, everybody. I infer that there is no
home WLAN, though everything works all right if I type in explicit
IP addresses. The IP addresses will vary because of DHCP, so I
can't simply put them in /etc/hosts.
The hostnames and IP addresses are all known to the router
(Linksys wrt54g), as I can confirm by querying the router. Should
the router not resolve these local hostnames? Or do I
misunderstand how this should work under DHCP?
simple fix within the capability of the DHCP server in my $50
Linksys wrt54g router. Given that there is no simple fix, and that
the only problem is that I have to manually enter IP addresses
whenever I do local ftp or ssh, I think I'll follow the principle:
"If it ain't broke (much), don't fix it (much)."
allways
assign ip address X to MAC address Y. Look through the manual to see if
your router allows that.
the DHCP server already has the hostname-IP address associations it
needs to resolve the local hostname?
You have become fixated on your particular solution to the problem.
Let go.
Or spend you life trying to persuade Linksys to do it your way.
Just trying to understand a bit more about networking, and to find the
simplest solution to a noncritical problem.
OK, static addresses.
Thanks.
idea - they don't scale in the sense that if you add another computer to
a network of n machines, then you have to change the /etc/hosts file of
all n existing machines.
It depends on what the value of n is. If it is 3 then that is not a problem
If it is 10 or 1000 then it is. Most homes have at most 3 computers.
YOu can also write a script to transfer the /etc/hosts file to all machines
when needed.
Also you could set up one of the machines as a dns server and use it to
resolve for the others. This is much more work than updating /etc/hosts
once a year for 3 machines. If you have 10 or 100 or more, then it may well
be the way to go.
1. Are you sure that your router can't to hostname to IP address
translations? It may just be that it has a wrong idea of your domain
names. If the host name of another computer is, say, machine, try to
resolve (e.g. with the command hosts):
The amount of time he has already spent just typing his queries exceeds the
work of updating /etc/hosts for the next 5 years.
machine.
(the following dot will stop your own computer appending its own idea of
the domain name)
Otherwise, look at the router's idea of the domain name and try to resolve:
machine.domain.name.
(if the domain name is domain.name)
Of course that may not work either, but it will test whether your router
can resolve local hostnames.
2. Run avahi. Then each machine will advertise its own hostname and IP
address and you will be able to resolve say, machine, as machine.local
Robert.
- Follow-Ups:
- Re: Name resolution for local names using DHCP
- From: Charles Russell
- Re: Name resolution for local names using DHCP
- References:
- Name resolution for local names using DHCP
- From: Charles Russell
- Re: Name resolution for local names using DHCP
- From: Charles Russell
- Re: Name resolution for local names using DHCP
- From: Unruh
- Re: Name resolution for local names using DHCP
- From: Charles Russell
- Re: Name resolution for local names using DHCP
- From: Unruh
- Re: Name resolution for local names using DHCP
- From: Charles Russell
- Re: Name resolution for local names using DHCP
- From: Robert Harris
- Name resolution for local names using DHCP
- Prev by Date: Re: Name resolution for local names using DHCP
- Next by Date: Discovering DHCP linux device
- Previous by thread: Re: Name resolution for local names using DHCP
- Next by thread: Re: Name resolution for local names using DHCP
- Index(es):
Relevant Pages
|