Hello All,
I have been experiencing problems whenever I want to use an alternate dialup isp instead of my main default one. I use Mandrake 10.1 with kppp as my dialer. After I have connected to one isp, if I disconnect and select the second isp, the connection is successfull but sites don't open up. The kppp accounts are set to delete earlier dns entries so that everytime there is a fresh entry and the firewall is also flushed but no luck. If the system is rebooted then I can use the second isp.
Conclusion: Whatever isp is dialled first works, for the next, its a hit and run case with more failures than success.
Any clues? Any Tips or tricks? How would a regular user like a customer do it, as it can be done in windows?
Regards,
Rony.
___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
On Thursday 21 Jul 2005 3:43 pm, Rony Bill wrote:
Hello All,
I have been experiencing problems whenever I want to use an alternate dialup isp instead of my main default one. I use Mandrake 10.1 with kppp as my dialer. After I have connected to one isp, if I disconnect and select the second isp, the connection is successfull but sites don't open up. The kppp accounts are set to delete earlier dns entries so that everytime there is a fresh entry and the firewall is also flushed but no luck. If the system is rebooted then I can use the second isp.
there is a file called /etc/resolv.conf where the dns nameserver is specified. When you dial up the first isp, it's dns server is put as the first line in the file. When you dial the second isp, the first isp's dns server is still in the first line of resolv.conf. Best solution to this would be to run your own caching-only nameserver and set the first line of resolv.conf to 'nameserver 127.0.0.1' and make sure mdk doesnt overwrite this file on reboot or on changing the isp. This way you will have your own dns always and need not rely on the isp dns - bsnl and mtnl for example are notorious for their dns servers to go phut every now and then
Any clues? Any Tips or tricks? How would a regular user like a customer do it, as it can be done in windows?
i may be wrong, but i dont think there is any way that one can make a linux machine run like windoze
Rony Bill ronbillypop@yahoo.co.uk wrote: Any clues? Any Tips or tricks? How would a regular user like a customer do it, as it can be done in windows?
Did you try restartting the network? Did you try traceroute www.google.com et al.?
Probably the routes are not getting flushed right?
Regards,
Chirag
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Sometime on Thu, Jul 21, 2005 at 03:43:50PM +0530, Rony Bill said:
Hello All,
Conclusion: Whatever isp is dialled first works, for the next, its a hit and run case with more failures than success.
Hmm, you need to delete the routing tables before trying another ISP. This should be done automatically but i dont know why
# route del default
before connecting to another ISP.
Any clues? Any Tips or tricks? How would a regular user like a customer do it, as it can be done in windows?
However you dont want your clients to issue commands like this right?
Anurag
Anurag wrote:
Hmm, you need to delete the routing tables before trying another ISP. This should be done automatically but i dont know why
# route del default
before connecting to another ISP.
I checked the routing tables and for every connection it has new routes as per the isp. Once the connection is closed, the routing table removes that entry. The /etc/resolv.conf also shows the correct dns entries of the respective isp and deletes them automatically once the connection is closed. This problem happens only with mtnl and a few times even on reboot, it did not open sites. I guess its their compatibility problem with linux.
Meanwhile I am trying to figure out what is a caching-only name service as suggested by Kennith.
Regards,
Rony.
___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
On 7/24/05, Rony Bill ronbillypop@yahoo.co.uk wrote:
Meanwhile I am trying to figure out what is a caching-only name service as suggested by Kennith.
Regards,
Rony.
Hi,
I've setup a cahing dns using this guide: http://www.tldp.org/HOWTO/DNS-HOWTO-3.html
My ISP's dns was taking too much time to resolve hosts. It was taking 10 seconds to lookup google.com http://google.com, so I setup my own caching nameserver.
-Akshay
On Sun, 2005-07-24 at 21:49, Rony Bill wrote:
Meanwhile I am trying to figure out what is a caching-only name service as suggested by Kennith.
$ cat /etc/resolv.conf
nameserver 127.0.0.1 nameserver 202.144.66.6
# /etc/rc.d/init.d/named start
There. Now you don't always have to depend on your ISPs DNS server. You've got your own caching only name server. "Caching only" because you are just caching the host-ip map looked up from the root servers, as opposed to being an authorative server in which case you would have the zone files for that domain.
Regards, NMK. ----------------------------------------------------------------------- A man with one watch knows what time it is. A man with two watches is never quite sure.
On Sunday 24 Jul 2005 10:25 pm, Nadeem M. Khan wrote:
$ cat /etc/resolv.conf
nameserver 127.0.0.1 nameserver 202.144.66.6
# /etc/rc.d/init.d/named start
make sure the caching nameserver is installed - you can check out from the 'install software' option in the 'configure your computer' option of mandrake10
This problem happens only with mtnl and a few times even on reboot, it did not open sites. I guess its their compatibility problem with linux. PPP is PPP whether it is linux or windows, hence question of mtnl compatible with linux doesnt arise. If there had been any compatibility issues then the connection would not have established during the 1st phase of connection i.e LCP.
This problem of getting logged on and not able to tranfer data used to happen with VSNL also, but it used to happen during daytime and never in the night for me. Did you notice the time when this problem occurs? Probably your connecting during heavy internet use hours (day time) and mtnl's bandwidht pool policy might not be in place?.
Meanwhile I am trying to figure out what is a caching-only name service as suggested by Kennith.
Caching-only name servers will not have any records of their own. When it recevied a request from a client for the first time it will query on behalf of a client to a nameserver. The next time client requests the caching server, it will answer from the date in its cache thus saving bandwidth and improving response.
--------------------------------- Start your day with Yahoo! - make it your home page
On Monday 25 Jul 2005 10:01 am, chirag radhakrishnan wrote:
Caching-only name servers will not have any records of their own. When it recevied a request from a client for the first time it will query on behalf of a client to a nameserver. The next time client requests the caching server, it will answer from the date in its cache thus saving bandwidth and improving response.
no - the caching only name server directly queries the root nameservers on the internet (and of course caches the results). The 'only' refers to the fact that the other elements of a dns server do not run - ie, the machine does not have its own internal dns. bsnl, mtnl and vsnl regularly screw up their dns servers, so it is advisable to run ones own as already suggested
Kenneth Gonsalves lawgon@thenilgiris.com wrote: On Monday 25 Jul 2005 10:01 am, chirag radhakrishnan wrote:
Caching-only name servers will not have any records of their own. When it recevied a request from a client for the first time it will query on behalf of a client to a nameserver. The next time client requests the caching server, it  will answer from the date in its cache thus saving bandwidth and improving response.
no - the caching only name server directly queries the root nameservers on the internet (and of course caches the results). The 'only' refers to the fact that the other elements of a dns server do not run - ie, the machine does not have its own internal dns. bsnl, mtnl and vsnl regularly screw up their dns servers, so it is advisable to run ones own as already suggested
No- It depends on the zone that you define. If you have a zone '.' of type hint and you provide root servers, then and only then will it refer to the root servers. If instead of root servers you provide any other server it should query that and obtain a non-authorative answer.
I dont know how often vsnl/bsnl screw their dns servers but in case of production proxy servers generally you have a local caching server to improve performance. Helps when you have more than 20/30 hits per second.
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Monday 25 Jul 2005 1:50 pm, chirag radhakrishnan wrote:
No- It depends on the zone that you define. If you have a zone '.' of type hint and you provide root servers, then and only then will it refer to the root servers.
what other way is there to set up a caching only nameserver?
If instead of root servers you provide any other server it should query that and obtain a non-authorative answer.
this depends on what you put in /etc/resolv.conf
Kenneth Gonsalves lawgon@thenilgiris.com wrote:
what other way is there to set up a caching only nameserver?
Instead of providing the root servers take hints from other DNS server.
If instead of root servers you provide any other server it should query that and obtain a non-authorative answer.
this depends on what you put in /etc/resolv.conf
since we are talking about locally configured caching-servers, /etc/resolv.conf must lookup localhost for resolving.
Regards,
Chirag
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com