On Thu, Jul 04, 2002 at 07:36:29AM -0700, Ray Olszewski wrote:
>At 08:26 AM 7/4/02 -0400, George Georgalis wrote:
>>I just remembered, my bering distro won't do hostname lookups.
>>
>>resolv.conf is okay
>>hosts.allow/deny are okay
>>the route is okay
>
>
>How do you know all of these are "okay"? In particular, have you confirmed
>that you can ping the IP addresses of the resolvers listed in resolv.conf?
>You should confirm that, at least, before looking to more complicated answers.
I know they are okay, because I pretty much know what I'm doing. I'm
new to LRP not Linux. I can ping the LAN resolver, and it does work. I
forgot to mention, I've also checked the iptables rules and they are
okay, verified by no messages in the log.
I also tried adding these to both the lrp and the LAN resolver.
# iptables -I INPUT -p udp --dport 53 -j ACCEPT
# iptables -I INPUT -p udp --dport 53 -j LOG --log-prefix "DNS-in "
The LAN resolver logs other host lookups but not the lrp. Likewise, the
lrp logs when I dig it, but no log when I try to ping a hostname, I can
ping the resolver by ip.
>>ping galis.org just hangs. not sure how else to look up a name, am I
>>missing a package? What could be wrong? It does ping ip addresses.
>
>
>If your system passes the above test, try posting the usual dagnostics.
I didn't assign a broadcast address when I brought up the interfaces,
could that be a problem?
Bering V1.0-rc2
Linux fw01 2.4.18 #1 Sun Apr 21 12:50:34 CEST 2002 i586 unknown
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:a0:cc:5a:b6:12 brd ff:ff:ff:ff:ff:ff
inet 192.168.9.66/24 scope global eth0
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:a0:cc:d9:21:e0 brd ff:ff:ff:ff:ff:ff
inet 10.1.1.1/8 scope global eth1
inet 10.0.0.1/8 scope global secondary eth1:1
inet 10.0.0.2/8 scope global secondary eth1:2
inet 10.0.0.3/8 scope global secondary eth1:3
inet 10.0.0.4/8 scope global secondary eth1:4
5: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:a0:cc:5b:1c:37 brd ff:ff:ff:ff:ff:ff
inet 62.81.93.66/26 scope global eth2
6: eth3: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:40:05:41:9d:1d brd ff:ff:ff:ff:ff:ff
inet 201.13.105.34/27 scope global eth3
201.13.105.32/27 dev eth3 proto kernel scope link src 201.13.105.34
62.81.93.64/26 dev eth2 proto kernel scope link src 62.81.93.66
192.168.9.0/24 dev eth0 proto kernel scope link src 192.168.9.66
10.0.0.0/8 dev eth1 proto kernel scope link src 10.1.1.1
127.0.0.0/8 via 127.0.0.1 dev lo
default via 62.81.93.65 dev eth2
>Finally, this sort of question belongs on leaf-user, NOT leaf-devel. I'be
>moved it in my reply.
Okay by me. I thought I had a development issue. My guess is I've
stripped something that's required for name resolution. So I ask, what
is used for host lookups (the udp/53 call) on lrp?
// George
--
GEORGE GEORGALIS, System Admin/Architect cell: 347-451-8229
Security Services, Web, Mail, mailto:[EMAIL PROTECTED]
File, Print, DB and DNS Servers. http://www.galis.org/george
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Caffeinated soap. No kidding.
http://thinkgeek.com/sf
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
