could not resolve DNS name
 

Hi,
I use NTL broadband SErvice 512 kbps .I wanted to connect to www.dosth.com
but couln't get it connected thru NTL .
CAn anyone tell me why it's not working from NTL .All my friends are able to connect thru to the main page ?
I believe the DNS is not been resolved by NTL .
Can any one shed me lights on this please ?

Ganesh.

Re: could not resolve DNS name
 

Ping / traceroute it?

Re: could not resolve DNS name
 

Has the site only just been registered? If so its possible ntl's DNS has not yet updated.

Plus there is no 512 kbps service on ntl.

Re: could not resolve DNS name
 

:welcome:

Have you tried specifying a proxy server?

http://www.cableforum.co.uk/kb/12/ho...pecify-a-proxy

http://homepage.ntlworld.com/robin.d...trancache.html

http://www.cableforum.co.uk/kb/47/li...-proxy-servers

Re: could not resolve DNS name
 

NTL's dns servers are resolving it fine, as are all others I have tried.

Re: could not resolve DNS name
 

Thanks for all the replies ,It's a newly registered website ,but my friends in USA and London were able to see .
Ping didn't work ,timeout is reached everytime.
Tried tracing the route in www.dnsstuff.com in the column "tracert" .
It had 17 hop steps ,but looks like it has failed from 14 to 17 th step .This is the output .If anyone could help me with this issue i would very much appreciate it.
Thansks & REgards,
GAnesh

HopTime 1Time 2Time 3IPHostnameReturn TTLCountryTime116 ms19 ms19 ms216.26.129.91 [www.DNSstuff.com 1st hop]252UNITED STATESUnix: 7:56:28.19224 ms7 ms7 ms216.26.128.181 edge-rtr02.ge-0-3-0.sdf.xodiax.net.252UNITED STATESUnix: 7:56:28.194311 ms14 ms14 ms65.117.168.137 chi-edge-09.inet.qwest.net.251UNITED STATESUnix: 7:56:28.21949 ms16 ms16 ms205.171.20.121 chi-core-01.inet.qwest.net.250UNITED STATESUnix: 7:56:28.38858 ms16 ms16 ms205.171.20.170 chi-core-02.inet.qwest.net.250UNITED STATESUnix: 7:56:28.410610 ms13 ms13 ms205.171.205.34 cer-core-01.inet.qwest.net.248UNITED STATESUnix: 7:56:28.422796 ms108 ms117 ms205.171.139.146 chp-brdr-01.inet.qwest.net.248UNITED STATES 89 ms15 ms15 ms205.171.4.14 [Missing reverse DNS entry]247UNITED STATESUnix: 7:56:28.572910 ms13 ms13 ms152.63.73.21 0.so-5-0-0.XL2.CHI13.ALTER.NET.245UNITED STATESUnix: 7:56:28.6131013 ms16 ms16 ms152.63.68.89 0.so-0-0-0.TL2.CHI2.ALTER.NET.244UNITED STATESUnix: 7:56:28.6301134 ms52 ms61 ms152.63.1.177 0.so-2-3-0.TL2.NYC8.ALTER.NET.245UNITED STATESUnix: 7:56:28.6571238 ms48 ms57 ms152.63.16.37 0.so-2-0-0.CL2.EWR6.ALTER.NET.245UNITED STATESUnix: 7:56:28.7411350 ms39 ms59 ms152.63.28.49 POS7-0.GW2.EWR17.ALTER.NET.245UNITED STATESUnix: 7:56:28.83314*** 15*** 16*** 1773 ms83 ms92 ms69.72.137.162 server5.24hostingnow.com.
[Reached Destination]50UNITED STATESUnix: 7:56:31.892

Re: could not resolve DNS name
 

That is the most awful trace layout - can't follow it - This is a trace from my NTL connection ;

There is no problem here that I can see.

It would be much more useful if you did a trace from your connection rather than dns-stuff.

Re: could not resolve DNS name
 

Iam able to logon from other networks like BT,freeserve .
Even it did work for my friend in London who has got NTL .
I believe it's the Local NTL's DNS server not been updated .The trace in your reply seems to look good .Iam attaching mine again .
From the 14 th HOP it's blank

1 4 ms 9 ms 9 ms 216.26.129.91 [www.DNSstuff.com 1st hop]
2 2 ms 5 ms 5 ms 216.26.128.181 edge-rtr02.ge-0-3-0.sdf.xodiax.net.
3 14 ms 245 ms 700 ms 65.117.168.137 chi-edge-09.inet.qwest.net.
4 10 ms 16 ms 15 ms 205.171.20.121 chi-core-01.inet.qwest.net.
5 52 ms 41 ms 62 ms 205.171.20.170 chi-core-02.inet.qwest.net.
6 12 ms 15 ms 15 ms 205.171.205.34 cer-core-01.inet.qwest.net.
7 11 ms 14 ms 14 ms 205.171.139.146 chp-brdr-01.inet.qwest.net.
8 10 ms 12 ms 12 ms 205.171.4.14 [Missing reverse DNS entry]
9 10 ms 13 ms 13 ms 152.63.73.21 0.so-5-0-0.XL2.CHI13.ALTER.NET.
10 22 ms 13 ms 22 ms 152.63.68.89 0.so-0-0-0.TL2.CHI2.ALTER.NET.
11 35 ms 43 ms 52 ms 152.63.1.177 0.so-2-3-0.TL2.NYC8.ALTER.NET.
12 94 ms 225 ms 139 ms 152.63.16.37 0.so-2-0-0.CL2.EWR6.ALTER.NET.
13 40 ms 70 ms 78 ms 152.63.28.49 POS7-0.GW2.EWR17.ALTER.NET.
14 * * *
15 * * *
16 * * *
17 37 ms 53 ms 63 ms 69.72.137.162
[Reached Destination]server5.24hostingnow.com. 50 UNITED STATES

Re: could not resolve DNS name
 

The fact they are blank is not really relevant as you reached the destination ok.

Re: could not resolve DNS name
 

Everything looks fine with ntl's dns...

> www.dosth.com
Server: cache2.ntli.net
Address: 194.168.8.100

Non-authoritative answer:
Name: dosth.com
Address: 69.72.137.162
Aliases: www.dosth.com

> 69.72.137.162
Server: cache2.ntli.net
Address: 194.168.8.100

Name: server5.24hostingnow.com
Address: 69.72.137.162


sounds like a local proxy issue, so try doing as Matt D suggested and specify a proxy server. You could also try browsing to the site (or indeed PCBD message) and then pressing CTRL + F5 or typing the address as http://www.dosth.com/?1 and is if that makes any difference. Also clear you local cache files, and make sure you haven't put an incorrect entry for the site in the hosts file on your machine.

MB

Re: could not resolve DNS name
 

Tried using proxy ,it didn't help either .
But i was able to connect to www.dosth.com ,when i used VPN connection to my office network (connected to NTL and then connected to my office network thru Virtual Private Network) .
It clearly proves something to do with the NTL conection,but could not find out what ...If any one could shed me some light ...please do so

Thanks & Regards,
Sharmila

Re: could not resolve DNS name
 

Hello this is the route trace i managed to get for www.dosth.com



Hop# Avg Loss % Address
ms
1 10 10.63.208.1
2 30 33 80.0.54.13 (leed-t2cam1-a-ge95.inet.ntl.com)
3 10 80.0.241.33 (leed-t2core-a-ge-wan61.inet.ntl.com)
4 10 62.253.185.17 (lee-bb-a-so-120-0.inet.ntl.com)
5 23 62.253.185.238 (pop-bb-b-so-100-0.inet.ntl.com)
6 16 208.185.188.41 (so-3-0-0.cr1.lhr3.uk.above.net)
7 15 33 208.184.231.150 (pos0-0.er1a.lhr3.uk.above.net)
8 * 100 0.0.0.0
9 * 100 0.0.0.0
10 * 100 0.0.0.0
11 * 100 Unable to reach 69.72.137.162 (www.dosth.com)

It clearly says itcould not reach .

Sharmila

Re: could not resolve DNS name
 

this doesn't show much as in your earlier post, the traceroute did reach the destination.

Have you edited the results of this traceroute? because every dns server i have tried, resolves 69.72.137.162 to server5.24hostingnow.com- not www.dosth.com. also i have never seen a traceroute which will try to hope to 0.0.0.0 ip addresses.

Oh and also, just FYI everything past pop-bb-b-so-100-0.inet.ntl.com is outside of ntl's network.

Re: could not resolve DNS name
 

What are you using to do these traces ?

FYI, that trace shows the traffic apparently got lost in the above.net network, well beyond ntl's network.

Re: could not resolve DNS name
 

Hi,
I used the websites from google that trace the route .
I used analagx website to trace the route as well ,ofcourse failed to reach the destination .
Iam quite wondering when it works for everyone why is not working for me ?
i've not modified anything in the trace result .
The first trace was done from www.dnsstuff.com ,though it says it reaches the destination in between steps from 14 to 17 are blank .Infact i do tried adding up proxy server ,but in vain.

Sharmila

Re: could not resolve DNS name
 

There is no point in doing traces from websites to your destination, they are proving nothing about how you connect.

Re: could not resolve DNS name
 

to run a traceroute from your own computer, go to

start-> run -> type "cmd" (if you are using win98/me type "command")

then press return.
You will get a dos window open, and then in this one type "tracert www.dosth.com"
press return

then copy and paste the results here :) oh and btw none of the quotes should be typed ;)

MB