James Knott wrote:
Sandy Drobic wrote:
Marcin Floryan wrote:
On 17/01/2008, David C. Rankin <[EMAIL PROTECTED]> wrote:
Ken Schneider wrote:
No, this is just another of my anal retentive moments where
I can't
understand why my machine wants to ssh out to the world as
mail.3111skyline.com. It's another of my inquisitively stupid "Why?"
questions. I mean, what logic on the box looks to bind dns and says, "I
want to be known as mail today? Hell, why not nemesis.3111skyline.com,
it real name? (Ur, Umm, the name of the box is probably at fault) I
should have called the son-of-a-bitch accommodating.3111skyline.com and
I wouldn't have to put up with this stuff.
I know it doesn't matter, but why?
It is simply a problem of incorrectly configured reverse DNS for the
domain. A lookup for 66.76.63.120 yields mail.3111skyline.com. If mail
and nemesis are on machine as it seems to be I would also consider
using CNAME.
The remote client will log the DNS-Name of the reverse lookup as the
client name. How the client announces itself to the world is dependent
on the hostname that was configured on the box itself.
Does IP now send host names along with the IP address? Any such
announcement would have to be application dependent. The name I've
No, unless the developer likes pain, the resolution is the job of the os.
If your box opens a connection to a remote server then the remote server only
sees the ip address of your box. The only way to get a hostname for that ip
address is to look up the ptr record of that ip from the authoritative dns
server responsible for the address space that contains the ip address of your box.
If such a ptr record exists, the remote server now has a hostname
corresponding to that ip address.
In the next step the hostname is verified by looking up this hostname, now the
remote server is asking the dns server responsible for the domain of that
hostname to find out, what the corresponding ip address for that hostname is.
If the hostname exists in dns and points to an ip address, the remote server
can now check if the hostname resolves back to the ip address of your box.
If that check is successful then the remote server can assume that the
hostname is indeed a match for the ip address.
There are many ways to foul up this resolution, and ISPs and service providers
have found and implemented most of them. :-/
--
Sandy
List replies only please!
Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
