Re: reverse dns broken
 

Dynu technical support have advised me to turn on an option in the client tool which tells the tool to use port 1025 instead of 80.


This seems to have done the trick.

Thanks for everyones input.

Re: reverse dns broken
 

Just re-noticed this thread - the Derby one is still screwed, so am dropping another note...

Re: reverse dns broken
 

Thanks BBKing - I'm the Derby one that's still screwed :) . Was going to post a follow-up here today, but you've beaten me to it.

Re: reverse dns broken
 

finally got back on, something was definatly broke this morning... router had no ip from ntls dhcp... then when i got a ip it kept dropping it and i could only browse via IP

stb seemed to be suffering as well, was totally unresponsive to the remove or key pad

Re: reverse dns broken
 

Shouldn't be anything to do with DNS, dropping off like that.

Is DNS fixed for Derby? I mentioned it to someone earlier...

Re: reverse dns broken
 

BBKing - it seems to be. The end of my long DNS name has now changed from "manc.broadband.ntl.com" to "bagu.broadband.ntl.com" but, it now works. Thanks for getting that sorted.

Re: reverse dns broken
 

As part of ongoing upgrades some DHCPs are being moved around and in preperation for tier uplift some core network resegmentation (not local HFC, core network) is taking place, shiny new routers for some! :)

Re: reverse dns broken
 

sounds good

Re: reverse dns broken
 

all seems fixed but i noticed part of my host has gone back to bagu (from manc) for the billionth time :P

Re: reverse dns broken
 

Reflects a change in DHCP servers. Consolidation onto fewer, smaller, faster, cheaper, better, you get the picture.