From: "David Galligani" <davidgalligani@es.luxottica.com>
To: James <james@piku.org.uk>, linux-admin@vger.kernel.org
Subject: R: unable to resolve things...
Date: Mon, 13 May 2002 15:51:44 +0200 [thread overview]
Message-ID: <00eb01c1fa85$53eb04b0$010a910a@es.luxottica.com> (raw)
In-Reply-To: Pine.LNX.4.30.0205131432030.20238-100000@quantum.ukshells.co.uk
Can you send us
the files of named (/etc/named.conf and /var/named/* )?
ciao
david
----- Original Message -----
From: James <james@piku.org.uk>
To: <linux-admin@vger.kernel.org>
Sent: Monday, May 13, 2002 3:41 PM
Subject: unable to resolve things...
> I've just set this Linux machine up to connect to an Alcatel ADSL router
> using dhcpcd (the router is configured for DHCP spoofing). eth0 has now
> been given a working IP address, and I can ping IP addresses of places
> like google.
>
> However, I can't ping "www.google.com" or any other names. They won't
> resolve.
>
> BUT if I type 'nslookup' I can talk to a DNS and resolve them manually,
> however nothing else seems to be able to look addresses up except
> nslookup.
>
> This machine is routing data for a LAN, and runs named. Other machines
> that have this Linux box set as their DNS server can resolve things
> though and they can browse the web.
>
> My resolv.conf contains:
>
> ---
> search rda.lan
> nameserver 10.0.0.5
> ---
>
> (10.0.0.5 is this machine's internal IP)
>
> and nsswitch.conf contains:
>
> ---
> hosts: dns files
> networks: files dns
> ---
>
> and I've restarted inetd for fun.
>
> This machine is configured to route traffic using ipfwadm.
>
> ifconfig contains:
>
> ---
> eth0 Link encap:Ethernet HWaddr 00:50:DA:50:01:FB
> inet addr:xxx.xxx.xxx.xxx Bcast:xx.255.255.255 Mask:255.0.0.0
> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:57415 errors:0 dropped:0 overruns:1 frame:0
> TX packets:73421 errors:0 dropped:0 overruns:0 carrier:0
> collisions:4286 txqueuelen:100
> Interrupt:9 Base address:0xfc00
>
> eth0:1 Link encap:Ethernet HWaddr 00:50:DA:50:01:FB
> inet addr:10.0.0.5 Bcast:10.255.255.255 Mask:255.0.0.0
> UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:9 Base address:0xfc00
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:88 errors:0 dropped:0 overruns:0 frame:0
> TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> ---
>
> it's only got one network card in it, so I am using aliased IPs to make it
> talk to the local lan too.
>
> What obvious thing have I not done?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-05-13 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 13:41 unable to resolve things James
2002-05-13 13:51 ` David Galligani [this message]
[not found] ` <00e001c1fa84$bec91200$010a910a@es.luxottica.com>
2002-05-13 14:52 ` R: " James
2002-05-13 15:09 ` Glynn Clements
2002-05-13 15:21 ` James
2002-05-13 15:42 ` rich+ml
2002-05-13 17:13 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00eb01c1fa85$53eb04b0$010a910a@es.luxottica.com' \
--to=davidgalligani@es.luxottica.com \
--cc=james@piku.org.uk \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).