Fwd: [clue-tech] resolver question

[Dave Price]

I use qwest DSL also -

My (in)action(not)tec device appears to be set up as a caching DNS
server - however my experience and some tests have shown that it is
not a very good one.

I have taken to using the following script to start my laptop when I
boot it at this location:

[davep at ldpx:~]$ cat bin/go
#!/bin/bash
sudo /sbin/modprobe ndiswrapper
sudo /sbin/iwconfig wlan0 essid "ACTIONTEC"
sudo /sbin/iwconfig wlan0 key "*localwepkey*"
sudo /sbin/ifconfig wlan0 up
sudo /sbin/dhclient  wlan0
#sudo /sbin/route add default gw 192.168.0.1
/sbin/iwconfig wlan0
/sbin/ifconfig wlan0
sudo cp /etc/resolv.bev /etc/resolv.conf
sleep 10
sudo service openvpn start
sleep 5
startx

and ...

[davep at ldpx:~]$ cat /etc/resolv.bev
search myworkdomain.com
nameserver 127.0.0.1
nameserver 205.171.3.65
nameserver 205.171.2.65

(of course, you want to put in your own wep key and search domain)
I am running CentOS and have the standard bind.i386 package installed
- the other 2 resolvers are backups which I gleaned from a windows box
booted off the same DSL modem.

You may not need the openvpn client either, but that is how I start
here, with pauses to slow things down, and ifconfig lines to give
feedback that I have a wireless link and dhcp lease ...

The key is overwriting the /etc/resolv.conf that dhclient creates - it
would point to 192.168.0.1, and disregard the fact that I am running
bind locally, and know about 2 other DNS servers as well.  Before this
tweak, web access was flakey at best.

I boot to a CLI login, and not always on this network.

If you use a graphical login, and always boot into the same LAN, you
might put this into  rc.local or something similar.

I hope this helps ...

aloha,
dave

On 9/17/06, Steve Lowe <sdlowe at mac.com> wrote:
> The way I understand it, It should work if 192.168.0.1 is a
> nameserver, even caching. If it's *just * a router, it won't return
> anything for DNS requests, forcing the request to failover to the
> other IP address in the list.
>
> Did you restart the actiontec after making the changes? I just
> checked my computer and the settings in my router:
> domain lowenet.net
> nameserver 216.17.128.1
> nameserver 216.17.128.2
>
> Which are the nameservers for FRII which I have configured in my
> Linksys router. Incidentally, I've got the Actiontec in bridging mode
> since I have the /29 network from FRII. One of the IP addresses is
> assigned to my Linksys for the LAN, and it serves DHCP.
>
> On Sep 16, 2006, at 11:49 PM, Jeff Cann wrote:
>
> > When I get a DHCP lease on my linux box, the resolver lists the
> > following:
> >
> > search domain.actdsltmp
> > nameserver 192.168.0.1
> > nameserver 205.171.3.65
> >
> > The 205.171 is Qwest.  However, when I try to resolve certain
> > domain names, they do not work.  If I change the first name server
> > to the other well-known Qwest name server [205.171.2.65], I am then
> > able to resolve any domain name.
> >
> > So, I thought:  Hey, I should be able to set the name servers on my
> > actiontec dsl device.  In the DHCP settings, I changed the name
> > server setting from 'automatic' to 'static' and filled in the
> > 205.171.2.65 and 205.171.3.65 IP addresses.
> >
> > This fixes the problem for DHCP clients.
> >
> > But, on further reflection, it seems like the first name server
> > [192.168.0.1] is supposed to go to my LAN router [since it's the
> > network address] and then into the great beyond.  Am I
> > understanding this correctly?  If this is the case, why won't name
> > server queries work consistently?
> > Incidentally, even after I changed the actiontec DHCP settings, new
> > DHCP leases still give out the original 192.168.0.1 and the
> > 205.171.3.65
> >
> > I am running the firewall and I have a static IP.  Not sure if this
> > affects the situation.
> >
> > I appreciate any thoughts.
> >
> > Jeff
> > _______________________________________________
> > clue-tech mailing list
> > clue-tech at cluedenver.org
> > http://www.cluedenver.org/mailman/listinfo/clue-tech
>
> _______________________________________________
> clue-tech mailing list
> clue-tech at cluedenver.org
> http://www.cluedenver.org/mailman/listinfo/clue-tech
>