From Newsgroup: news.software.readers

HTTP servers can handle multiple websites on the same IP address and
port because the request headers include the hostname.

Is there anything like that for NNTP, or does the server on a given IP
address always behave exactly the same? In other words, if
news.example.com and nntp.example.com have the same IP address, can
the server tell which hostname the client is calling?

Thanks.
--
they're OK, the last days of May
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: news.software.readers

Adam Funk <a24061@ducksburg.com> wrote:

HTTP servers can handle multiple websites on the same IP address and
port because the request headers include the hostname.

Is there anything like that for NNTP, or does the server on a given IP address always behave exactly the same? In other words, if
news.example.com and nntp.example.com have the same IP address, can
the server tell which hostname the client is calling?

There aren't any headers sent by the client until they post
something to a newsgroup, and even then probably nothing useful, so
I don't see how that could work.
--
__ __
#_ < |\| |< _#
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: news.software.readers

On 2025-11-20, Computer Nerd Kev wrote:

Adam Funk <a24061@ducksburg.com> wrote:

HTTP servers can handle multiple websites on the same IP address and
port because the request headers include the hostname.

Is there anything like that for NNTP, or does the server on a given IP
address always behave exactly the same? In other words, if
news.example.com and nntp.example.com have the same IP address, can
the server tell which hostname the client is calling?

There aren't any headers sent by the client until they post
something to a newsgroup, and even then probably nothing useful, so
I don't see how that could work.

That's what I thought --- thanks.
--
Logic is the beginning of wisdom, not the end.
---Spock
--- Synchronet 3.21a-Linux NewsLink 1.2