[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Weird DNS error?



Thanks Bob and Tom.

I didn't install a DNS server and I am connecting via DHCP.

The results of the various commands are below.

Thanks for your help!

Greg

# dpkg -l bind
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
un  bind           <none>         (no description available)

# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp

# cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 192.168.1.254

# grep hosts /etc/nsswitch.conf
hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1d:72:80:50:cb
          inet addr:192.168.1.103  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21d:72ff:fe80:50cb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14800 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3465 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2590636 (2.4 MiB)  TX bytes:301977 (294.8 KiB)
          Interrupt:20 Memory:f8200000-f8220000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:108 errors:0 dropped:0 overruns:0 frame:0
          TX packets:108 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8956 (8.7 KiB)  TX bytes:8956 (8.7 KiB)

# netstat -rn
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
0.0.0.0         192.168.1.254   0.0.0.0         UG        0 0          0 eth0

# cat /etc/hosts
127.0.0.1	localhost
127.0.1.1	sunny

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

On Mon, Oct 24, 2011 at 5:48 PM, Bob Proulx <bob@proulx.com> wrote:
> Greg van Anders wrote:
>> I just did a brand new installation of Squeeze. The install seemed
>> to go fine and I didn't notice any problems.
>
> Did you select, at the task selection menu, the "DNS Server" task?
> You should be able to resolve names in both cases but the debug route
> is different in the different cases.  If you selected it then you will
> have bind9 installed.  If not then you won't.  Either is okay.  We
> just need to know.
>
>  $ dpkg -l bind9
>
>> Upon booting, however, I don't seem to be able to resolve any hosts
>> other than www.debian.org and security.debian.org.
>
> That is odd.  You are booting using a DHCP address or a static
> address?  DHCP will supply a nameserver.  If static then you must
> supply one statically.
>
> What are the contents of your /etc/network/interfaces file?
>
>  $ cat /etc/network/interfaces
>
> What are the contents of your /etc/resolv.conf file?
>
>  $ cat /etc/resolv.conf
>
> Also /etc/nsswitch.conf just to make sure it isn't a reason either.
>
>  $ grep hosts /etc/nsswitch.conf
>  hosts:          files dns
>
> Unfortunately there are several possibilities here depending upon the
> contents of the files and the debug path is different depending upon
> the result.  I will stop there but that should get things going.
>
>> If I open up a terminal, ifconfig shows an IP address, and I can
>> traceroute to other hosts for which I know the IP, but I can't for
>> anything I specify by name.
>
> Good.  You have network connectivity.  Network connectivity is a
> prerequisite for DNS to work.  But those are two separate things and
> otherwise unrelated to each other.
>
> Bob
>


Reply to: