Recently i switched to OpenDns with Familyshield.I have applied the dns setting on my belkin wireless router. If i dont use internet for 3-4 hours,my ISP asks me to re-login again,then i cant access the login page or internet. Then i have to go to dns setting on my router and change the setting to 'Automatic from ISP' and then i can see the login page. It only happens when my ISP asks me to login again otherwise it fine.
You need split horizon DNS service.
Your ISP is apparently one of those that uses internal domain names for things that are intended to be visible only to customers attached to its network. It directs you to the WWW page at, say,
Obviously, OpenDNS — which, ironically, also provides customized versions of the DNS namespace — doesn't know anything about such arragements. Nor can you tell it.
So you need what is known as split-horizon DNS service. You need to ensure that all DNS lookups for
There's almost certainly no way that you can do this with a domestic-grade router. Such routers lack the capability. You won't be able to do this by adjusting the DNS clients on the individual workstations on your LAN, either. It's not a capability built into any but a very few DNS clients. (Pretty much only MacOS has this mechanism.)
What you have to do instead is run a forwarding proxy DNS server, somewhere on your LAN. You configure that server to perform conditional forwarding, splitting
If the necessity of having to have a single machine powered on if any other machines on the LAN are powered on gives you pause, you could even run individual forwarding proxy DNS servers on each workstation, rather than one central one serving your entire LAN. Running a DNS server on each workstation isn't exactly a novel thing in the world of Internet. People were doing it as a matter of course some thirty years ago. Most current operating systems actually come with DNS server softwares provided as standard. If you have BSDs, Linuxen, Macintoshes, Solarises, and so forth, setting up a forwarding proxy DNS server is a simple matter of installing djbdns, PowerDNS, BIND, or suchlike and configuring it with the appropriate conditional forwarding rules.
The non-Server editions of Microsoft Windows are the glaring exceptions. Even Windows Server has a DNS server as standard. So it's only really if you have an all-Windows-workstations network, without any Windows Server machines or non-Windows machines, that you will suffer from not having the software capability right there in the box.
There are other ways to address this, of course: scripts that do complex dances to reconfigure things temporarily and log-in, bodges using