APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

login slow dns setup

© December 2004 (various authors)

What is this stuff?

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):

Newsgroups: comp.unix.sco.misc
From: bill@wjv.com (Bill Vermillion)
Subject: Re: Login prompt very slow
Message-ID: <G20sDr.19L3@wjv.com> 
References: <8rivo7$ufn$1@nnrp1.deja.com>
<> Date: Fri, 6 Oct 2000 17:53:51 GMT In article <>, Ken Wolff <kenw@cscc.maximus.com> wrote: >At 01:55 PM 10/6/00 +0000, Bill Vermillion wrote: >>And it's not a problem when the networks are properly set up.

>Except when your using DNS and your internet connection goes down.
>Despite having all local IPs in /etc/hosts and having "hostresorder
>local bind" in /etc/resolv.conf, once we loose our internet
>connection we run into the delay.

I still say 'when the networks are properly set up'.

If your internet connection goes down and you won't be able to get
to external sites. 

So I'm assuming you are having local problems. Go back and read the
fixes. If you have windows machines make sure they all have the
entries in them.

Or better yet, run DNS locally, and have every machine point to
that.  The other solutions - all machines have their own private
version of the /etc/hosts file - get's cumbersome to maintain.

DNS isn't that hard.  And it's a one place solution - maintain it
on one machine and just add entries when knew machines come up.

Instead of adding ONE line to /etc/hosts, you add a line to
what is the DNS hosts equivalent AND a line to the reverse mapped
file.   Editing two files to add one machine - and having everyting
work properly - is a very small price to pay.

Again - the problem is that the target machines can't resolve the
IP/name of the connecting machine.  Why local machines are not seen
when your ISP goes down is a strange scenario in my way of looking
at networks.

Since most of the machines I work on are net connected, I prefer
the really secure approach, and if you can't be resolved you are
ignored.   The argument that Linux lets you in immediately won't
work for me - I'm the type that keeps my doors locked when I'm
inside too.


Bill Vermillion -   bv @ wjv . com

Got something to add? Send me email.

(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

-> login slow dns setup ––>Re: Login prompt veryslow

Inexpensive and informative Apple related e-books:

El Capitan: A Take Control Crash Course

Take Control of iCloud, Fifth Edition

Sierra: A Take Control Crash Course

Take Control of Numbers

Take Control of Upgrading to El Capitan

Printer Friendly Version

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us

Printer Friendly Version

Two years from now, spam will be solved. (Bill Gates, 2004)

Linux posts

Troubleshooting posts

This post tagged:




Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode

SCO Unix Sales, Support, & Service

Phone:  707-SCO-UNIX (707-726-8649Toll Free: 833-SCO-UNIX (833-726-8649)