i think DNS is enough. if glen can setup a reverse
proxy dns for all the IPs in his network, it should
give the server's resolver the proper ip when DNS is
queried therefore making it easier for the ftp server
to do the look up.
--- Rusty Carruth <[EMAIL PROTECTED]> wrote:
> Gregor Maier <[EMAIL PROTECTED]> wrote:
> >
> > On 26-Jul-2001 Rusty Carruth wrote:
> > > Glen Sagers <[EMAIL PROTECTED]> wrote:
> > ...
> > >> Do I need to manually setup DHCP or DNS?
> > >> Glen
> > >
> > > Well, sort of.
> > >
> > ...
> > > Then it should be much faster...
> > ...
> > If you're network gets bigger you may want to
> setup a small dns server for your
> > network. The method with /etc/hosts works fine.
> But you'll have to keep all
> > hosts files on all machine up to date or you'll
> fancy results.
> > If you have more than 5 I would really suggest to
> setup dns. Have a look at the
> > DNS-Howto. It's quite good and you get a working
> dns server in (almost) no time
>
> And, since Glen said that he's using dhcp and thus
> 'cannot know' what IP
> addresses go with what machine (which is not the
> point, really), then its
> sounding like dns is the easiest answer.
>
> However, I'd not bother trying to make the names
> mean anything relative to
> the machine that gets it. Lets not lose track of
> the whole purpose we're
> doing this - to make ftpd able to find a name given
> an ip addr (later, if
> we find out that ftpd will complain or error if that
> name and the name
> the client machine knows itself by do not match,
> then we can address
> the issue of making the names match, but it will be
> much easier I think).
> (Well, ok, the ACTUAL reason is to get rid of the
> startup delay, but I'm
> pretty sure the startup delay is because of
> reverse-name-lookup, so that's
> what we're trying to fix here ;-)
>
> Ok, so either on DNS or in /etc/hosts, define names
> for all IP addresses
> your DHCP server could give out. Write a little
> basic program to create
> the file, as its a template with numbers changing.
> Since I know /etc/hosts
> by heart, I'll use it as an example, but you could
> 'easily' modify this to
> be the format bind (or equiv) needs. So, if you
> were doing /etc/hosts,
> it might look like this:
>
> 10.40.1.1 m001001
> 10.40.1.2 m001002
> 10.40.1.3 m001003
> ...etc...
> 10.40.2.1 m002001
> 10.40.2.2 m002002
> ...etc...
>
> that gives every possible ip address a name, and you
> don't have to change
> the name whenever a machine gets a new IP address.
>
> (BTW - if you are using ISC dhcp I think you can set
> it up so that ip addresses
> are assigned based upon MAC address of the host
> adapter, thus keeping the
> addresses the same for the machines you decide you
> want to stay at one 'spot')
>
> Now, if you want to assign reasonable names to each
> individual machine, you're
> going to be forced into working with your DHCP
> server to assign the same IP
> address (or name, but its the same thing, really)
> based upon the client
> host adapter's MAC address. But that was not the
> point of the original
> question, as I recall ;-)
>
> rc
>
>
> Rusty E. Carruth Email:
> [EMAIL PROTECTED] or [EMAIL PROTECTED]
> Voice: (480) 345-3621 SnailMail: Schlumberger ATE
> ___
> FAX: (480) 345-8793 7855 S. River
> Parkway, Suite 116 \e/
> Ham: N7IKQ @ 146.82+,pl 162.2 Tempe, AZ
> 85284-1825 V
> ICBM: 33 20' 44"N 111 53' 47"W
> http://tuxedo.org/~esr/ecsl/index.html
>
>
>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
