[CLUE-Tech] named & Suse 9

[Collins Richey]

On Sun, 28 Mar 2004 01:10:07 -0700
Mike Staver <staver at fimble.com> wrote:

> I feel dumb for asking this here... but I can't figure it out.  I set
> up a Suse 9 box with dhcp - and then today I changed the IP to a
> static one.  I did so by modifying the file
> /etc/sysconfig/network/ifcfg-eth0, and I changed it to:
> 
> BOOTPROTO='static'
> MTU=''

should be ok to default. Used for segmenting packets. Usually you don't
need to screw around with this.

> REMOTE_IPADDR=''

don't have a clue. Most google entries have this as an empty string
except for WLAN and handheld setups.

> STARTMODE='onboot'
> UNIQUE='qnJ_.Er3ucFQoZE2'

This appears to be an id for cards (wlan? pmcia?)

> DEVICE='eth0'
> BROADCAST='64.242.89.255'
> IPADDR='64.242.89.11'
> NETMASK='255.255.255.0'
> NETWORK='64.242.89.0'
> 

> 
> should contain.  I left them alone as a result.  I can ssh into this
> box under that IP now, but running named on it fails.  Here are my
> logs:
> 

> Mar 27 23:31:58 linux named[2104]: client 193.231.236.25#11505: error 
> sending response: network unreachable
> Mar 27 23:31:58 linux named[2104]: client 193.231.236.17#53: error 
> sending response: network unreachable
> 
> Obviously, the part that concerns me is "network unreachable". 

In my experience, this is usually a problem with resolv.conf or routes.
What does 'route -n show'. dhcp will usually add a default route for
you. Maybe you need a GATEWAY= now that you are hard coding an ip
address?

On my system, DHCP sets up the routes as follows:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0    
   0 eth0 127.0.0.0       127.0.0.1       255.0.0.0       UG    0      0
       0 lo 0.0.0.0         192.168.0.1     0.0.0.0         UG    0     
0        0 eth0

Note the last entry is a default route to my router.

>  
> I can't find the normal /etc/resolv.conf that I'm used to in Red Hat. 
> 
> I'm also confused because to find resolv.conf, I would normally type:
> 
> locate resolv.conf
> 
> But, I get this when trying:
> 
> kenny:/home/staver # locate resolv.conf
> bash: locate: command not found
> 

Maybe SUSE doesn't have the alias locate for slocate?

OTOH, very suspicious if there is no /etc/resolv.conf

mine looks like this

domain my_local_domain_name
nameserver 192.168.0.1 (the address my router responds to)
search attbi.comDEST   (I've been using this since ATT days; still works
                                           on comcast)


HTH,

-- 
Collins Richey - Denver area
gentoo testing 2.6.3-rc2 nptl udev