Re: dselect and resolving
On Monday 11 February 2002 19:04, Michel Loos wrote:
> Em Seg, 2002-02-11 às 21:42, John Cichy escreveu:
> > On Monday 11 February 2002 18:40, Michel Loos wrote:
> > > Em Seg, 2002-02-11 às 21:19, John Cichy escreveu:
> > > > On Monday 11 February 2002 18:15, Osamu Aoki wrote:
> > > > > On Mon, Feb 11, 2002 at 08:43:25PM -0200, Michel Loos wrote:
> > > > > > Em Seg, 2002-02-11 ?s 13:50, John Cichy escreveu:
> > > > > > > Hello all,
> > > > > > >
> > > > > > > It seems the dselect ignores the host file when updating it's
> > > > > > > lists. I have a debian mirror in my DMZ and have added an entry
> > > > > > > in my hosts file to use an internal address to access the
> > > > > > > mirror, but it seems that dselect is ignoring that entry and
> > > > > > > trying the public address instead. Does anyone know how to make
> > > > > > > dselect look at the hosts file, my host.conf has the entry :
> > > > > > >
> > > > > > > order hosts,bind
> > > > > > >
> > > > > > > so I would think that it would resolve to the address in the
> > > > > > > host file.
> > > > > >
> > > > > > Did you add your mirror in the /etc/apt/sources.list ?
> > > > > > If you did, apt-get update (or dselect -> update) should check
> > > > > > your mirror.
> > > > >
> > > > > For "dselect", "apt-get update" is not enough. You need to make
> > > > > sure to run "dselect update". That what previous post by a debian
> > > > > developer, as I remember.
> > > > >
> > > > > > Usually they still will connect to the public server for download
> > > > > > since probably your mirror is not as uptodate as the public
> > > > > > server
> > > >
> > > > This machine was built on the private network from my mirror, not
> > > > from the the public server. The problem is that now that the machine
> > > > is in the DMZ it is it is using my dns which is resolving to the
> > > > public address, not what is in it's hosts file.
> > >
> > > Let me get that right: your mirror is named http.us.debian.org in your
> > > hosts file?
> >
> > No, my host file contains an entry for:
> >
> > enterprisepenguin.com LOCAL IP
> >
> > my sources.list file has entries:
> >
> > http://enterprisepenguin.com/distributions/debian/
> >
> > and dselect tries to connect to my public IP for enterprisepenguin.com
> > rather then the LOCAL IP in the hosts file.
>
> In fact it the same thing use another name in your hosts file and point
> sources.list to that one, this works at least if your DMZ zone accept
> port 80 connections to your mirror from inside. I have the same sort of
> set-up.
I just tried this:
192.168.2.40 enterprisepenguin.com mirror
and changed only one entry in the sources list to mirror with an interesting
result, mirror returned a 404 not found error (expected because of named
based virtual host) and then the enterprisepenguin.com [PUBLIC IP] entry
hung. This say to me that dselect is doing the opisite of what of what I have
my host.conf file set up is, i.e. it looked in dns first (and found the
enterprisepenguin.com entry), then looked in the hosts file (and found
mirror). The host.conf says:
order hosts,dns
Any thoughts?
John
Reply to: