Colchester or DNS problems

[Pulse^]

Hi folks,

Today and yesturday, I have been having problems with my ntl connection. I use irc a lot, and yesturday, I could not log onto my normal server, but I could log onto a different server on the network. I did find something that was strange. This is what I get when I connect to dalnet.

[12:33] *** Looking Up Your Hostname...
[12:33] *** Checking Your Identd...
* Identd request from 194.68.45.50
* Identd replied: 1031, 6667 : USERID : UNIX : genesis
[12:33] *** Identd Response Received
[12:33] *** Your Hostname Was Found (Hostname In Cache)
-
[12:33] Welcome to the DALnet IRC Network Altern8(genesis@81.103.13.**)

Normally my host resloves but for 2 days running it has not. So I used the /dns command

* Dns resolving 81.103.13.**
-
* Resolved 81.103.13.** to void
-
* Dns resolving 81.103.13.*
-
* Resolved 81.103.13.* to cpc2-colc*-*-0-cust4.colc.cable.ntl.com
-
* Dns resolving cpc2-colc*-*-0-cust4.colc.cable.ntl.com
-
* Unable to resolve cpc2-colc*-*-0-cust4.colc.cable.ntl.com

For some reason, the IP resolves to my computer name (void), but when I try the same IP address without the last number, it resolves back to my host name. Then if I try to resolve the host name, it comes up with 'unable to resolve. I use ntl's name servers 194.168.4.100, 194.168.8.100

Has anyone else experinced this? or just a local (colchester) thing? or anyone have any ideas how to fix this?

Cheers

Kev

[Greebox]

All of a sudden last night the STB threw a wobbly as it does occasionally. All services came back,surfing email MSN but IRC now refuses to connect to the server I normally use but like yourself I can connect to other servers. All items in the chain STB, Router and PC's have been sequentially rebooted.

What's it all about ?

Pulse - your ip resolves back to cpc2-colc3-3-0-custxx.colc.cable.ntl.com on every dns server I have tried (inc ntl's).

[Greebox]

Definitely a DNS problem in my case, as I found the IP for my server (I'm using Gamesurge - 195.68.206.250) connected to that immediately I think I'll add it to the Hosts table to save problems in the future.

[Pulse^]

Hiya,



Thanks for your replies. By the look of things, the reverse dns was not working properly, *shrug* but things seemed to be working ok now, I noticed they were working from about yesterdayâ₠¬â„¢s lunch time onwards.



Cheers



Kev