DynIP

[cyberprof]

I have recently experimented with DynIp and set up an account with the domain name -

http://newname.dynip.com

and the service worked fine. I have unsubscribed with dynip and they assure me the service is cancelled, however, everytime I type

http://newname.dynip.com

into my browser I am getting the home page of my localhost folder. (IIS 5)

I have tried everything to stop it, how is this still happening. Has anyone had a similar experience.

Any help much appreciated

J

 

[aznluvsmc]

Try clearing the DNS cache on your computer or restarting.

To clear the cache, type IPCONFIG /flushdns at the command prompt.

Steven S.
MCSA
A+, Network+, Server+, i-Net+

 

[cyberprof]

Just flushed my dns cache and restarted, still doing the same thing

 

[aznluvsmc]

Well the URL is not mapped to any IP address so DynIP did unregister it. Trying pinging the URL and see what the response is. I'm pretty sure you'll get a host not found error.

Steven S.
MCSA
A+, Network+, Server+, i-Net+

 

[cyberprof]

Sorry, I used 'newname' as an example, the actual address was pt.dynip.com. Here are the results of the ping. It looks like it's pinging the I.P. address of my machine.

Pinging pt.dynip.com [127.0.0.1] with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

[aznluvsmc]

It seems like it's registered to 127.0.0.1 as I can also ping that URL. Maybe it will take some time to be unregistered?

Steven S.
MCSA
A+, Network+, Server+, i-Net+

 

[wagnj1]

I ran a tracert on pt.dynip.com and it just stopped at my localhost (127.0.0.1 - its not actually pinging your ip):

H:\>tracert pt.dynip.com

Tracing route to pt.dynip.com [127.0.0.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1ms localhost [127.0.0.1]

Trace complete.

H:\>


I also ran a sam spade on you URL (samspade.org isn't working 100% right now) here's what I got:

pt.dynip.com = [ 127.0.0.1 ]
Registrant:
CanWeb Internet Services Ltd. DYNIP-DOM
265 Front St. N. Suite 204
Sarnia ON N7T 7X1
CA
Domain Name: DYNIP.COM
Administrative Contact Technical Contact:
Grant David david@CANWEB.CA
265 Front St. N. Suite 204
Sarnia ON N7T 7X1
CA
(519) 332-6900 fax: (519) 332-6464
Record expires on 06-Feb-2006.
Record created on 05-Feb-1997.
Database last updated on 14-Apr-2004 13: 33: 46 EDT.
Domain servers in listed order:
DISCOVERY.DYNIP.COM 204.225.44.10
ALTAIR.CANWEB.CA
NS3.DYNIP.COM 204.50.159.194

This is confusing, as it resolves the URL to your 127.0.0.1 but stops tracing at mine.

 

[aznluvsmc]

Tracert has to resolve the name before it can perform the trace. Since the name resolves to 127.0.0.1, Tracert will point back to the localhost so it does make sense that the trace stops at your computer. Cyberprof, give Dynip a call or e-mail letting them know that they are resolving a domain name to 127.0.0.1 so they can fix it.

Steven S.
MCSA
A+, Network+, Server+, i-Net+

 

[cyberprof]

OK, I have tried contacting them but I'm getting no reply yet. I will keep trying as this problem is very annoying.

Is my localhost site open to the

http://WWW at

the moment.

Thanks for your advice

J

 

[aznluvsmc]

Since the URL resolves to the localhost, anyone who enters that URL will always be pointed back to their computer. 127.0.0.1 is a reserved loopback address used for testing on the local machine.

Steven S.
MCSA
A+, Network+, Server+, i-Net+

 

[wagnj1]

I couldn't get access to it over

http://WWW right

now

 

[cyberprof]

OK, Cheers