[dunkyb]

Hmm ... NTL's DNS seem to time out a LOT for me .... eg:

C:\Documents and Settings\dunkyb>nslookup 86.15.50.67
Server: cache2.ntli.net
Address: 194.168.8.100
DNS request timed out.
timeout was 2 seconds.
*** Request to cache2.ntli.net timed-out

Request again straight after, and it worked....

C:\Documents and Settings\dunkyb>nslookup 86.15.50.67
Server: cache2.ntli.net
Address: 194.168.8.100
Name: cpc3-cosh5-0-0-cust578.cos2.cable.ntl.com
Address: 86.15.50.67

Try again ....

C:\Documents and Settings\dunkyb>nslookup 86.15.50.67
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 194.168.8.100: Timed out
Server: cache1.ntli.net
Address: 194.168.4.100
Name: cpc3-cosh5-0-0-cust578.cos2.cable.ntl.com
Address: 86.15.50.67

Tried some more common sites (google.com, yahoo, etc) which all resolved fine, then tried some completely random domains....

nslookup cheeseandbiscuits.com
Server: cache2.ntli.net
Address: 194.168.8.100
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to cache2.ntli.net timed-out

nslookup cheeseandbiscuits.com
Server: cache2.ntli.net
Address: 194.168.8.100
Non-authoritative answer:
Name: cheeseandbiscuits.com
Address: 204.13.161.32

Fails first time, works second. I was thinking it could be the authorative ns servers not responding, but it states that the request to the NTL dns timed out? I dont know much about the windows resolver, but I think it usually states that the ISP's dns server cant find the domain if that was the case.

Just seems a little hit n miss?

Admittadly I have yet to try from a direct connection, or from the linux router...