DNS Problem

Started by Anonymous, February 09, 2004, 02:15:18 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Anonymous

I seem to be having a problem getting to my server and I think the culprit is good old DNS.

Can somebody please try the following and tell me which works (if any)?

tracert 82.41.75.121
tracert //www.sutherlandweb.co.uk

cheers

OldBloke

I cannot connect to either IP or address.

IP pings OK.

//www.sutherlandweb.co.uk pings as 212.4.208.117

HTH
"War without end. Well, what was history if not that? And how would having the stars change anything?" - James S. A. Corey

Benny

http://www.dns-tools.com/default.asp?prog=...st=82.41.75.121

9 16 15 31  208.175.10.93 dcr1-so-3-3-0.chicago.cw.net
10 109 110 125  166.63.210.18 zcr1-loopback.londonlnt.cw.net
11 125 109 125  166.63.222.38 telewest.londonlnt.cw.net
12 125 125 125  194.117.136.141 -
13 125 125 125  62.31.64.53 ubr10-edin.blueyonder.co.uk
14 141 125 140  82.41.75.121 82-41-75-121.cable.ubr10.edin.blueyonder.co.uk


IP address: 213.171.193.41
Host name: //www.sutherland.co.uk
Alias:
server41.livedns.org.uk




And more?
 //www.sutherland.co.uk
Non-authoritative answer:
Name:   //www.sutherland.co.uk
Address: 213.171.193.41

Authoritative answers can be found from:
sutherland.co.uk        nameserver = ns2.livedns.co.uk.
sutherland.co.uk        nameserver = ns1.livedns.co.uk.
>
===============
Master of maybe

Anonymous

Thanks peeps. DNS from here seems to be royally screwed up if you ask me.

The IP that OB got resolved is the IP of the DNS server that is meant to be managing DNS requests :(

Strangely, I cannot even trace to the 82.41.75.121 IP so there may be a further problem at this end (work that is)

Anonymous

Mmmm, maybe it ain't DNS. Here is trace to same box using different CNAME:

c:\>tracert blueball.deadmen.co.uk -d

Tracing route to blueball.deadmen.co.uk [82.41.75.121]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  146.105.134.254
  2     2 ms     2 ms     2 ms  146.105.135.253
  3    10 ms    10 ms    10 ms  62.6.192.82
  4    17 ms    17 ms    17 ms  62.7.194.59
  5    25 ms    16 ms    16 ms  217.32.190.178
  6    16 ms    16 ms    16 ms  217.32.236.67
  7    16 ms    16 ms    16 ms  146.105.71.249
  8    17 ms    17 ms    22 ms  146.105.64.3
  9    31 ms    28 ms    22 ms  146.105.67.9
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.

Benny

Hang on, sutherland points to the 213 whatever address, bb.dead etc points to the 80 whatever. Are they the same box?

Pinging //www.sutherland.co.uk [213.171.193.41] with 32 bytes of data:

Request timed out.

Ping statistics for 213.171.193.41:
    Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum =  0ms, Average =  0ms
Control-C
^C
C:\Documents and Settings\James.Dyson>ping blueball.deadmen.co.uk

Pinging blueball.deadmen.co.uk [82.41.75.121] with 32 bytes of data:

Reply from 82.41.75.121: bytes=32 time=211ms TTL=134
Reply from 82.41.75.121: bytes=32 time=210ms TTL=134
Reply from 82.41.75.121: bytes=32 time=220ms TTL=134

Ping statistics for 82.41.75.121:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 210ms, Maximum =  220ms, Average =  213ms
===============
Master of maybe

Anonymous

not //www.sutherland.co.uk but //www.sutherlandweb.co.uk

I'm at home now. Problem solved. My router had lost it's port forwarding information!!!

Don't know how. The manual ports were all OK (CS and stuff) it was the uPNP stuff that went FUBAR (mail and web)