| To: | Qmail mailing list <qmail@list.cr.yp.to> |
|---|---|
| Subject: | Re: Strange behavior |
| From: | Fabio Busatto <fabio.busatto@sikurezza.org> |
| Date: | Fri, 23 Feb 2007 15:23:01 +0100 |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | gmail-qmail@securepoint.com |
| Delivered-to: | sp.com.list@gmail.com |
| Delivered-to: | mailing list qmail@list.cr.yp.to |
| In-reply-to: | <3817DF8FDC449F47971A5110B604F1D9779342@mail-eu.europe.sento.com> |
| Mailing-list: | contact qmail-help@list.cr.yp.to; run by ezmlm |
| References: | <3817DF8FDC449F47971A5110B604F1D9779342@mail-eu.europe.sento.com> |
| Reply-to: | Qmail mailing list <qmail@list.cr.yp.to> |
| User-agent: | Mutt/1.4.2i |
On Fri, Feb 23, 2007 at 02:45:26PM +0100, Steffen Bisgaard wrote: > Both domains resolve to the same ip address inside the LAN. > It seems as if qmail, or tcpserver, is listening on port 25 but only on one > domain - is this possible? This is a nonsense. Programs bind ports on ip addresses, not on hostnames. So, if you start a program with a hostname, it resolves and then uses the associated ip address. Telnet clients do the same, they first resolve the hostname into an ip address and then connect to it. All domain-related stuff could only be done at application layer, but the tcp connection cannot be blocked (there is no way for the server to know which is the hostname typed in the client looking only at the layers from transport to link). So, if you resolve both hostnames in the same ip address, telnet will connect to both, or none. Bye Fabio |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Strange behavior, Steffen Bisgaard |
|---|---|
| Next by Date: | RE: Strange behavior, Steffen Bisgaard |
| Previous by Thread: | Strange behavior, Steffen Bisgaard |
| Next by Thread: | RE: Strange behavior, Steffen Bisgaard |
| Indexes: | [Date] [Thread] [Top] [All Lists] |