IIS6 on Windows XP with Dynamic IP

This machine is part of AD. Are there issues with running IIS on machine
with dynamically assigned IP addres?

Thanks in advance

Not reallly.
You should always access the machine by the FQDN (
http://hostname.domainname.tld ),...so the IP# is not relevant.
As long as your LAN's name resolution is healthy and without design flaws
you will be fine.

Contrary to common superstition and forklore,...using an IP# in a URL is
worse not better,...less dependable not more dependable. so use the Name.
This is mostly true when the browser on the client-side happens to also have
proxy settings because the LAN uses a Proxy. IE does NOT handle IP#s
correctly in the addressbar when it also has proxy settings at the same
time,...I don't know if other browsers have the same problem of not. It is
just simply better to avoid a problem like that in the first place,...so
again,...use the Name,...even using a Netbios Name is still better than
using an IP#.

Examples:
FQDN http://hostname.domainname.tld
Netbios Name http://hostname


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"RG" <(E-Mail Removed)> wrote in message
news:E199C726-9D52-46EB-98BA-(E-Mail Removed)...
> This machine is part of AD. Are there issues with running IIS on machine
> with dynamically assigned IP addres?
>
> Thanks in advance

Thanks for the answer. BTW... I did nslookup for type ptr on the machine's
ip address from the machine itself. It didn't resolve even though the
machine is part of AD.

Is this a problem? How is it that dns entries aren't automatically
registered for members of the domain?

I thnk I saw a post which said no reverse ip resolution could also be a
problem.

Thanks again

"Phillip Windell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Not reallly.
> You should always access the machine by the FQDN (
> http://hostname.domainname.tld ),...so the IP# is not relevant.
> As long as your LAN's name resolution is healthy and without design flaws
> you will be fine.
>
> Contrary to common superstition and forklore,...using an IP# in a URL is
> worse not better,...less dependable not more dependable. so use the
> Name. This is mostly true when the browser on the client-side happens to
> also have proxy settings because the LAN uses a Proxy. IE does NOT
> handle IP#s correctly in the addressbar when it also has proxy settings at
> the same time,...I don't know if other browsers have the same problem of
> not. It is just simply better to avoid a problem like that in the first
> place,...so again,...use the Name,...even using a Netbios Name is still
> better than using an IP#.
>
> Examples:
> FQDN http://hostname.domainname.tld
> Netbios Name http://hostname
>
>
> --
> Phillip Windell
>
> The views expressed, are my own and not those of my employer, or
> Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
> "RG" <(E-Mail Removed)> wrote in message
> news:E199C726-9D52-46EB-98BA-(E-Mail Removed)...
>> This machine is part of AD. Are there issues with running IIS on machine
>> with dynamically assigned IP addres?
>>
>> Thanks in advance
>
>

You're not going to need reverse-lookup.

If you want to test the forward lookup, ping the name

c:\> ping machinename or FQDN

If you want to test the forward lookup ping the IP# with "-a"

c:\> ping -a 192.168.21.54

In ten years I have probably used NSLookup three times. Two of the three is
probably didn't help me with anything and the third mislead me to a problem
that didn't exist.


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------





"RG" <(E-Mail Removed)> wrote in message
news03CCF89-7A6D-4BC2-836E-(E-Mail Removed)...
> Thanks for the answer. BTW... I did nslookup for type ptr on the
> machine's ip address from the machine itself. It didn't resolve even
> though the machine is part of AD.
>
> Is this a problem? How is it that dns entries aren't automatically
> registered for members of the domain?
>
> I thnk I saw a post which said no reverse ip resolution could also be a
> problem.
>
> Thanks again
>
> "Phillip Windell" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Not reallly.
>> You should always access the machine by the FQDN (
>> http://hostname.domainname.tld ),...so the IP# is not relevant.
>> As long as your LAN's name resolution is healthy and without design flaws
>> you will be fine.
>>
>> Contrary to common superstition and forklore,...using an IP# in a URL is
>> worse not better,...less dependable not more dependable. so use the
>> Name. This is mostly true when the browser on the client-side happens to
>> also have proxy settings because the LAN uses a Proxy. IE does NOT
>> handle IP#s correctly in the addressbar when it also has proxy settings
>> at the same time,...I don't know if other browsers have the same problem
>> of not. It is just simply better to avoid a problem like that in the
>> first place,...so again,...use the Name,...even using a Netbios Name is
>> still better than using an IP#.
>>
>> Examples:
>> FQDN http://hostname.domainname.tld
>> Netbios Name http://hostname
>>
>>
>> --
>> Phillip Windell
>>
>> The views expressed, are my own and not those of my employer, or
>> Microsoft,
>> or anyone else associated with me, including my cats.
>> -----------------------------------------------------
>>
>>
>> "RG" <(E-Mail Removed)> wrote in message
>> news:E199C726-9D52-46EB-98BA-(E-Mail Removed)...
>>> This machine is part of AD. Are there issues with running IIS on
>>> machine
>>> with dynamically assigned IP addres?
>>>
>>> Thanks in advance
>>
>>
>

"Phillip Windell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...

> If you want to test the forward lookup ping the IP# with "-a"
>
> c:\> ping -a 192.168.21.54

Meant "reverse".