Re: Re: dselect and resolving
Dont know what that is , but I do know I cant get on your site Scott t. Parr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect and resolving
Em Ter, 2002-02-12 às 00:32, Richard Cobbe escreveu: Lo, on Monday, February 11, John Cichy did write: 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. I'm not entirely sure how this works, but there's a very good chance that /etc/nsswitch.conf is more significant than /etc/host.conf. What does the `hosts' line say from nsswitch.conf? I am not sure this is the problem. Since when using mirror you get an error, you will get the same error by using the enterprise.com from your hosts file, since the name to IP resolution is done locally the result will be exactly the same. After getting that error apt-get will assume wrong address and begin solving using the second option: dns and connect to the public server. Anyway since you can't get in your server with the name mirror: you will not be able to use it. Put the server back in the inside zone and not in the DMZ. Michel.
Re: dselect and resolving
Em Ter, 2002-02-12 às 00:29, John Cichy escreveu: On Monday 11 February 2002 21:32, Richard Cobbe wrote: Lo, on Monday, February 11, John Cichy did write: 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. I'm not entirely sure how this works, but there's a very good chance that /etc/nsswitch.conf is more significant than /etc/host.conf. What does the `hosts' line say from nsswitch.conf? hosts files dns John A stupid question are you able to connect with lynx to your virtual host ? Seems your internal router/firewall has problems with name based virtual hosting. Michel.
Re: dselect and resolving
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. That is not the correct way to do it, name it anything else (mirror for ex.) and update the /etc/apt/sources.list file to point to this address. I think I found your solution: change the setup of your virtual server in order to inclue a ServerPath /distributions directive in the VirtualHost definition take a look at http://httpd.apache.org/docs/vhosts/name-based.html Michel.
Re: dselect and resolving
On Tuesday 12 February 2002 06:43, Michel Loos wrote: Em Ter, 2002-02-12 às 00:29, John Cichy escreveu: On Monday 11 February 2002 21:32, Richard Cobbe wrote: Lo, on Monday, February 11, John Cichy did write: 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. I'm not entirely sure how this works, but there's a very good chance that /etc/nsswitch.conf is more significant than /etc/host.conf. What does the `hosts' line say from nsswitch.conf? hosts files dns John A stupid question are you able to connect with lynx to your virtual host ? Seems your internal router/firewall has problems with name based virtual hosting. I have worked around this problem by by symlinking the debian directory to the top level host and it now does work. The router/firewall does not have a problem with name based hosting, It has been working for over a year with no problems. The problem is I have the firewall blocking DMZ servers from going out and back in. There is no need to do this. The problem is that apt is resolving to dns first, if it does not find it answer, then it looks in the hosts file, so it is ignoring hosts and nsswitch.conf files. Anyway, it is now working. John
Re: dselect and resolving
On Tuesday 12 February 2002 06:35, Michel Loos wrote: Em Ter, 2002-02-12 às 00:32, Richard Cobbe escreveu: Lo, on Monday, February 11, John Cichy did write: 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. I'm not entirely sure how this works, but there's a very good chance that /etc/nsswitch.conf is more significant than /etc/host.conf. What does the `hosts' line say from nsswitch.conf? I am not sure this is the problem. Since when using mirror you get an error, you will get the same error by using the enterprise.com from your hosts file, since the name to IP resolution is done locally the result will be exactly the same. After getting that error apt-get will assume wrong address and begin solving using the second option: dns and connect to the public server. The DMZ is NAT'd, ie according to dns it has a public IP address, but the addresses the servers talk to are private. In my host file, I put the private address, this is how I know that apt is going to dns first, because it is saying that it is trying to connect to the public address, but when I added 'mirror' to the hosts line defining enterprisepenguin.com, and used 'mirror' sources.list apt said it was connecting to the private address, but at that point the web server had no idea what it was supposed to serve, so it returned a 404. Anyway since you can't get in your server with the name mirror: you will not be able to use it. Put the server back in the inside zone and not in the DMZ. It works now. Thanks for your help... John
dselect and resolving
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. TIA, John
Re: dselect and resolving
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. TIA, John Did you add your mirror in the /etc/apt/sources.list ? If you did, apt-get update (or dselect - update) should check your mirror. Usually they still will connect to the public server for download since probably your mirror is not as uptodate as the public server Michel.
Re: dselect and resolving
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 Osamu -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki [EMAIL PROTECTED], GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://qref.sourceforge.net/quick/ +
Re: dselect and resolving
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. John
Re: dselect and resolving
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? That is not the correct way to do it, name it anything else (mirror for ex.) and update the /etc/apt/sources.list file to point to this address. Michel.
Re: dselect and resolving
On Monday 11 February 2002 17:43, 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. TIA, John Did you add your mirror in the /etc/apt/sources.list ? If you did, apt-get update (or dselect - update) should check your mirror. Usually they still will connect to the public server for download since probably your mirror is not as uptodate as the public server Michel. The machine is not trying to connect to the public mirrors because I removed the public entries from the sources.list file. I have 15 machines that I am converting and 5 more that will be added. I created the mirror and set up a cron to keep me within about 4 hours of the public servers before I even started the conversion so I would limit the use of my 'conectivity' bandwidth and also to be 'kind' to the public servers. The problem is that dselect hangs while it is trying to connect to the mirror. This machine was built from my mirror while it was on my private network. The fact that it resolved to the public address while on the private network was ok because the router/firewall passes from private to DMZ. The mirror is a virtual web server on my primary web server so that does not allow me to just define the IP address of the mirror in the sources.list file. I can't seem to figure out a way to get dselect to resolve from the hosts file. John
Re: dselect and resolving
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. That is not the correct way to do it, name it anything else (mirror for ex.) and update the /etc/apt/sources.list file to point to this address. Michel.
Re: dselect and resolving
On Monday 11 February 2002 18:42, John Cichy wrote: 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 sorry miss typed LOCAL IPenterprisrpenguin.com 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. That is not the correct way to do it, name it anything else (mirror for ex.) and update the /etc/apt/sources.list file to point to this address. Michel.
Re: dselect and resolving
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. You can even use an IP in sources.list instead of a hostname. If there is still a problem it comes from your second router. Michel.
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. You can even use an IP in sources.list instead of a hostname. If there is still a problem it comes from your second router. I guess my router/firewall could be a little more forgiving, and if dselect will not look at the hosts file, I guess it will have to be. But getting it to use the host file just seems better, why run the traffic across the router if the machines can just talk through the switch? John
Re: dselect and resolving
John Cichy wrote: [snip!] This has caused enough confusion! Why do you _need_ to use the symbolic name for the mirror??? Why not just use the IP address in sources.list? Like this: deb ftp://192.168.83.4/debian stable main contrib non-free or whatever your local ip address is. Regards Tom
Re: dselect and resolving
On Monday 11 February 2002 19:34, Thomas Cook wrote: John Cichy wrote: [snip!] This has caused enough confusion! Why do you _need_ to use the symbolic name for the mirror??? Why not just use the IP address in sources.list? Like this: deb ftp://192.168.83.4/debian stable main contrib non-free Because it is on a virtual server, if you use the IP you hit the top level server which does not have access to the directorys in question. Regards Tom
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.40enterprisepenguin.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
Re: dselect and resolving
Lo, on Monday, February 11, John Cichy did write: 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. I'm not entirely sure how this works, but there's a very good chance that /etc/nsswitch.conf is more significant than /etc/host.conf. What does the `hosts' line say from nsswitch.conf? Richard
Re: dselect and resolving
On Monday 11 February 2002 21:32, Richard Cobbe wrote: Lo, on Monday, February 11, John Cichy did write: 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. I'm not entirely sure how this works, but there's a very good chance that /etc/nsswitch.conf is more significant than /etc/host.conf. What does the `hosts' line say from nsswitch.conf? hosts files dns John
