Re: routing prob

From: David Efflandt (efflandt_at_xnet.com)
Date: 02/25/05 

Date: Fri, 25 Feb 2005 03:05:18 +0000 (UTC)

On Thu, 24 Feb 2005 20:41:26 +0100, Jens Hofmeier <jhofmeir@hotmail.com> wrote:
> "David Efflandt" <efflandt@xnet.com> schrieb im Newsbeitrag
> news:slrnd1s96m.dle.efflandt@typhoon.xnet.com...
>> On Thu, 24 Feb 2005 19:11:28 +0100, Jens Hofmeier <jhofmeir@hotmail.com>
> wrote:
>> > Hello,
>> >
>> > this may be a newbie question, but since i'm new to linx, i'll give it a
>> > try:
>> > Where are the routing settings stored? Every time i restart the network
>> > service with "service network restart"
>> > some strange entries appear when typing "route":
>> > It's a route to
>> > 169.254.0.0 * 0.0.0.0 U 0 0 0 eth1
>> > I don't know where this comes from, since i've never entered it.
>>
>> That might be the default IP range used by Windows boxes that fail to get
>> a DHCP IP.
>>
>> > It also takes a few seconds until the last of the three entries there is
>> > displayed (Dest=default), does anyone know why?
>> > I'm using FC3 2.6.10
>>
>> Most likely DNS timeout attempting to resolve IPs that do not resolve.
>> route -n is quicker and sometimes easier to interpret.
>
> I don't think it's a DNS Problem; the entry that causes the delay is the
> following:
> default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1

The fact that 192.168.1.1 shows as an IP instead of name (no reverse DNS)
could easily explain a DNS timeout delay.

> or, using route -n
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
> any other suggestions? Furtheron i need to know where the network service
> fetches its settings from

Is route -n quicker (say yes)?

Which network service? Configuration of interfaces is usually something
in /etc/sysconfig. Resolving names is related to settings in /etc/ files
nsswitch.conf, host.conf, hosts and resolv.conf (and possibly your own
named.conf if doing your own DNS). Networking and network deamons are
usually started by scripts in /etc/init.d (or /etc/rc.d) symlinked in an
rc#.d subdir, where # is runlevel. Other network services may be launched
on the fly by inetd or xinetd. Status for commands like ifconfig, route
and arp are obtained from /proc.

Relevant Pages

  • Re: mystery rogue browser master on subnet
    ... DC's, two are running DNS. ... available as a network service from an upstream server. ... 10-15 minutes hoping that a legit browse master shows up. ... active devices then issue the following command for each IP address ...
    (microsoft.public.win2000.networking)
  • Ghost DNS entry
    ... Re: Ghost DNS record ... PTR record on all DNS server and I cannot find that record on ... However I can still resolve IP from name using ...
    (microsoft.public.windows.server.dns)
  • Re: Need Help from DNS Expert on Subdomain DNS Records
    ... When you use nslookup to resolve these names do you get the correct internal ... domain from within and outside our firewall. ... public IP to point to the same private IP, ... You need to verify that the all DNS servers assigned to a the DNS Client be ...
    (microsoft.public.windows.server.dns)
  • Re: download cvsup?
    ... Also the rest of the network is currently working. ... Eliminate all things superfluous to troubleshooting the DNS problem. ... whatever I try I can't seem to resolve external hosts, ... or whether the lookup is returning from your DNS server. ...
    (freebsd-questions)
  • Re: Cannot a DC, HOPELESS Case
    ... If the DC is not fully registered in DNS then it won't resolve ... the DCs NIC properties specify the correct DNS server. ... >>> error whenever I'm running DCpromo! ...
    (microsoft.public.win2000.active_directory)