 | | | DNS lookup failure on Linksys router | DNS lookup failure on Linksys router 2004-12-19 - By Steven J. Yellin
Back
Since phoenix1 and phoenix2 can ping phoenixl by name (bad policy to
use the difference between "1" and "l" as the only difference between
names) I guess you have a router which runs a DNS and knows that phoenixl
has IP 192.168.1.105. I assume the router knows about phoenix1 and
phoenix2, too. Can phoenix1 ping phoenix2 by name? If so, I don't know
why the router refuses to tell phoenixl the IP's of phoenix1 and phoenix2.
Maybe someone else can help. But another way of supplying phoenixl with
the relationship between IP and name is to add appropriate lines in
/etc/hosts for phoenix1 and phoenix2.
Speaking of /etc/hosts, you may be better off removing the line
192.168.1.105 phoenixl
and replacing the first line
127.0.0.1 localhost.localdomain localhost lo
with
127.0.0.1 localhost.localdomain localhost phoenix1
so that your computer knows localhost is the same as phoenixl. That way
it won't matter to phoenixl what IP it gets assigned, and "hostname -f",
"hostname -i", ... may stop complaining about "Host name lookup failure".
Steven Yellin
On Sun, 19 Dec 2004, Joshua E Vines wrote:
> This is a SOHO network. ISP is Verizon. Two computers running WinXP,
> three running Win98. Router is 192.168.1.1 and has no name or domain. No
> domain has been asigned to this network by Verizon (dynamic IP address).
> For the sake of arguing, three computers on the network have the names:
> phoenix1 (WinXP), phoenix2 (Win98), and phoenixl (Shrike).
> Router serves as DNS for Windows (only one DNS entry set on the Windows
> machines).
>
> 'hosts' contains:
>
> 127.0.0.1 localhost.localdomain localhost lo
> 192.168.1.1 router
> 192.168.1.105 phoenixl #as assigned by the router's DHCP
> #(low DHCP traffic so it does not change)
>
> Except for localhost, hosts on the Windows machines are blank.
> When phoenixl is not listed, hostname [-s|-a|-i|-f|-d|-y] (any of the
> options will do it) reports "Host name lookup failure". hostname without
> any options reports "phoenixl". On startup, X-Windows (not to be
> confused with Windows XP), complains of name resolution problems.
> When phoenixl is listed, hostname [-s|-a|-i|-f|-d|-y], reports
> "phoenixl" like it should.
> In either case, nslookup [/anyhostname/] reports ";; connection timed
> out; no servers could be reached".
>
> 'resolv.conf' contains:
> nameserver 192.168.1.1
>
> 'ifcfg-eth0' contains:
> DEVICE=eth0
> BOOTPROTO=dhcp
> ONBOOT=yes
> USERCTL=no
> PEERDNS=no
> TYPE=Ethernet
> DHCP_HOSTNAME=phoenixl
>
> ifconfig -a reports:
> eth0 Link encap:Ethernet HWaddr /mac address/
> inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:64 errors:0 dropped:0 overruns:0 frame:0
> TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:10042 (9.8 Kb) TX bytes:7455 (7.2 Kb)
> Interrupt:5 Base address:0x7000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:3593 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3593 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:244982 (239.2 Kb) TX bytes:244982 (239.2 Kb)
>
> netstat -nr reports:
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
> eth0
>
> phoenix1 and phoenix2 can ping phoenixl by name.
> phoenixl can not ping phoenix1 and phoenix2 by name.
>
> p.s.: do you know of a command or an otherwise short program to convert
> end-of-line characters (to go from Linux to DOS and back) in text files?
>
> --
>
> * * * * * * * * * * * * * * *
> Joshua E Vines
> jev@(protected)
>
>
--
Shrike-list mailing list
Shrike-list@(protected)
https://www.redhat.com/mailman/listinfo/shrike-list
|
|
|