John Hardin wrote:
While shit has happened too many times, I don't see why a browser would
do PTR lookup when given an IP.
If security settings are defined by the server's hostname or domain name
you'd kinda have to, or else say that all numeric-IP URLs are inherently
untrustworthy.
In that
John Hardin a écrit :
> On Wed, 8 Oct 2008, mouss wrote:
>
>> John Hardin a écrit :
>>
>>> I've recently come across some anomalous behavior in Vista and Win2k3
>>> when confronted with a host's rDNS returning "localhost". It seems
>>> Vista and Win2k3 replace this with the local hostname. To illus
On Wed, 8 Oct 2008, mouss wrote:
John Hardin a écrit :
I've recently come across some anomalous behavior in Vista and Win2k3
when confronted with a host's rDNS returning "localhost". It seems
Vista and Win2k3 replace this with the local hostname. To illustrate:
ping -a 123.30.74.2
AFAIK,
John Hardin a écrit :
> All:
>
> I've recently come across some anomalous behavior in Vista and Win2k3
> when confronted with a host's rDNS returning "localhost". It seems
> Vista and Win2k3 replace this with the local hostname. To illustrate:
>
>ping -a 123.30.74.2
>
AFAIK, "-a" doesn't change
All:
I've recently come across some anomalous behavior in Vista and Win2k3 when
confronted with a host's rDNS returning "localhost". It seems Vista and
Win2k3 replace this with the local hostname. To illustrate:
ping -a 123.30.74.2
(Note: this isn't new, some searching reveals a blog post
