[Leaf-user] Re: Re: Bering with SSH and TinyDNS
Hi Matthew- I have a Win2k server inside my local lan that handles my internal dns and forwarding to bering (dnscache) for external addresses. My resolv.conf is: Nameserver 127.0.0.1 If I had to put tinydns on I could take off weblet and just check the logs manually. I did forget that some have to use ppp/pppoe so that will add more packages. I usually make a copy of this disk without pump, weblet and some modules that I no longer need and add ppp for if, more like when with comcast, the cable goes out. John ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Re: Re: Bering with SSH and TinyDNS
John Stauffer wrote: Hi Matthew- I have a Win2k server inside my local lan that handles my internal dns and forwarding to bering (dnscache) for external addresses. Roger that. My resolv.conf is: Nameserver 127.0.0.1 But in this case, the LEAF box, using that nameserver, queries the dnscache for name resolution. Dnscache will not have name/address pairs for your internal lan, and my guess is that when you sit down at the LEAF and type nslookup 192.168.x.y where x and y are replaced with real IP's on your internal LAN that you don't get an instant response. Am I correct? If the lookup does succeed, it probably is coming from your LEAF /etc/hosts. I'm just curious because using tinydns takes care of that, and I faced the same problem recently. Regards, Matthew If I had to put tinydns on I could take off weblet and just check the logs manually. I did forget that some have to use ppp/pppoe so that will add more packages. I usually make a copy of this disk without pump, weblet and some modules that I no longer need and add ppp for if, more like when with comcast, the cable goes out. John ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] Re: Re: Bering with SSH and TinyDNS
Matthew, I do use the hosts file to resolve the names Bering needs to. I'd rather have the space for sshd and other packages I may need. I haven't used tinydns for any of my setups since I started using lrp with ppp in 1999. John -Original Message- From: Matt Schalit [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 8:08 PM To: John Stauffer Cc: [EMAIL PROTECTED] Subject: Re: [Leaf-user] Re: Re: Bering with SSH and TinyDNS John Stauffer wrote: Hi Matthew- I have a Win2k server inside my local lan that handles my internal dns and forwarding to bering (dnscache) for external addresses. Roger that. My resolv.conf is: Nameserver 127.0.0.1 But in this case, the LEAF box, using that nameserver, queries the dnscache for name resolution. Dnscache will not have name/address pairs for your internal lan, and my guess is that when you sit down at the LEAF and type nslookup 192.168.x.y where x and y are replaced with real IP's on your internal LAN that you don't get an instant response. Am I correct? If the lookup does succeed, it probably is coming from your LEAF /etc/hosts. I'm just curious because using tinydns takes care of that, and I faced the same problem recently. Regards, Matthew If I had to put tinydns on I could take off weblet and just check the logs manually. I did forget that some have to use ppp/pppoe so that will add more packages. I usually make a copy of this disk without pump, weblet and some modules that I no longer need and add ppp for if, more like when with comcast, the cable goes out. John ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Re: Re: Bering with SSH and TinyDNS
John Stauffer wrote: Matthew, I do use the hosts file to resolve the names Bering needs to. I'd rather have the space for sshd and other packages I may need. I haven't used tinydns for any of my setups since I started using lrp with ppp in 1999. John Ahaa. Ok that's what I figured was going on. When you connect to your LEAF sshd from your internal LAN, the sshd does a reverse lookup on the client's ip address. Does the sshd login delay for 10's of seconds until it does the lookup from /etc/hosts? Or do you have your LEAF nsswitch.conf set to look at hosts first and dns second? I think it's good to hear how others solve that exact delay issue I solved by setting up tinydns. Matt ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user