[CLUE-Tech] named & Suse 9

[Mike Staver]

>>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.
>
>  
>
Yeah, here is the output of route -n for me:

kenny:/etc # route -n    
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
64.242.89.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
kenny:/etc # slocate resolv.conf
bash: slocate: command not found

Even though I added this to my /etc/sysconfig/network/ifcfg-eth0:

GATEWAY='64.242.89.254'

and then restarted the network, it still didn't take.... so I used my 
new favorite linux config tool, yast, and set it up that way... and sure 
enough, it works now.  I'm confused though because I don't know where 
that information gets stored seeing as manually editing the files does 
no good.  Thanks for the input everybody.