Cable Forum - View Single Post

gatj98 · 23-07-2004, 00:39

I don't have any file sharing or anything like that running - just plain old web-browsing and it goes. I think it must be a dns problem - because if I can connect to home from work bi-directional communication must be possible - to send an email requires two servers to talk to each other. My understanding is that an incoming connection - such as an email message comes from a known ip address, so the recipient server (mine) doesn't have to do a look-up to reply to the request, so it can recieve incoming email even when it can't resolve dns properly. However of course to instigate connections from my system I need to be able to resolve dns properly - and it's this that fails. It's almost as if the ntl network says you've had your ip address lease for x amount of time, so I won't respond to dns requests until you renew it manually. My router, a netgear RT314, renews the ip automatically when necessary (and also updates our dyndns account with any changes)

I have a linux box which runs a dns server - it provides dns for our network, and caches look-ups for external addresses - it passes external requests to the ntl dns servers. I haven't touched the setup, and it had been running fine for over 18 months. Maybe my router is on the blink and isn't renewing the dhcp properly.....

23-07-2004, 00:39	#24
gatj98 Inactive Join Date: Feb 2004 Posts: 4	Re: NTL Disconnecting I don't have any file sharing or anything like that running - just plain old web-browsing and it goes. I think it must be a dns problem - because if I can connect to home from work bi-directional communication must be possible - to send an email requires two servers to talk to each other. My understanding is that an incoming connection - such as an email message comes from a known ip address, so the recipient server (mine) doesn't have to do a look-up to reply to the request, so it can recieve incoming email even when it can't resolve dns properly. However of course to instigate connections from my system I need to be able to resolve dns properly - and it's this that fails. It's almost as if the ntl network says you've had your ip address lease for x amount of time, so I won't respond to dns requests until you renew it manually. My router, a netgear RT314, renews the ip automatically when necessary (and also updates our dyndns account with any changes) I have a linux box which runs a dns server - it provides dns for our network, and caches look-ups for external addresses - it passes external requests to the ntl dns servers. I haven't touched the setup, and it had been running fine for over 18 months. Maybe my router is on the blink and isn't renewing the dhcp properly.....