RE: Homeseer and Dyndns

[Paul Miller <pmiller@xxxxxxx>]

Paul,

your w2k problem is the issue one of the arp cache still having the info
(arp -a) or is it still in the dns cache (ipconfig /displaydns)?



-----Original Message-----
From: Paul Gordon [mailto:paul_gordon@xxxxxxx]
Sent: 20 March 2001 09:47
To: ukha_d@xxxxxxx
Subject: Re: [ukha_d] Homeseer and Dyndns


>
>But to see this web page I must lookup my IP using the dyndns web page
and
>then type in this IP address into IE.  Is there any way I can just put
in


That kinda defeats the object!!


>webpage address that is the same all the time. (what is the name of the
>homeseer web page, I cannot find this anywhere as it seems to be too
>dynamic)

The whole point of dynamic DNS is to be able to do exactly that. The
name
would/should be whatever name you >choose< to register beneath the
Dynamic
DNS service providers domain name, for example,
"www.ianshouse.dyndns.org"
then as long as you have a DDNS client that correctly updates your
dynamic
registration(s) with that service (and does so promptly!), then
resolvers
should be able to use that name to find your webserver.

The fact that when you go to the DDNS webpage and look up your IP
address,
and find that is is correct and current, (as proved by the fact that
browsing to it gets to your HS webpage), proves that your client update
is
occurring quite correctly...

I would then look at the configuration of the resolvers... Do you have a

cacheing DNS server between your resolver and the DynDNS server?

I have a very similar problem at the moment with some W2K workstations,
- I
also use the DynDNS service, and a Dynamic DNS client to register my
Home
webserver (NT4 server & IIS4), which redirects incoming HTTP requests
to
my
internal Homeseer webserver. I find that the dynamic update portion
works
perfectly, IE when my server's IP address changes, the client correctly
updates the dynamic registration, and does so very quickly. Checking the

DynDNS webpage therefore shows the correct IP address, just as in your
case.
However, I then find that some PC's on my internal LAN can ping the FQDN

correctly, while others cannot, due to resolving an incorrect (earlier)
IP
address. My internal LAN also has a cacheing DNS server AND A proxy
server
(also on the same NT4 & IIS4 box), and my internal clients use ONLY
these
internal services. My initial belief was that my internal DNS server was

caching the IP address for the FQDN from an earlier lookup, and issuing
that
to subsequent requests, - EVEN after the server had disconnected &
reconnected and obtained (and registered)a different IP. However, I've
looked in MY DNS servers' cache, and I cannot see it, so that doesn't
>seem<
to be the case...

I haven't got to the bottom of this yet, but I think I may have
determined
that W2K clients and Win9X clients behave differently in how they
perform
DNS queries,... I am still investigating, so I'll let you know if/when I

figure it out...

Anyone a Whizz on DNS care to chime in?....


Paul G.

>
>I noticed an earlier mail where someone had put up a wiring diagram and

>this
>was done using dyndns.  Can I do this too.
>
>IanW

________________________________________________________________________
_
Get Your Private, Free E-mail from MSN Hotmail at
http://www.hotmail.com.





Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/