| Art Alexion on 20 Jul 2006 13:47:58 -0000 |
|
I solved this by adding the two DNS servers that the router uses to the list of servers to use, the router being the first, and the others following in order. I actually got competent help on this from Verizon tech support. (Always a crap shot, but sometimes with winning results.) Problem solved. On Tuesday 04 July 2006 13:11, gyoza@comcast.net wrote: > Art Alexion wrote: > > On Thursday 29 June 2006 12:35, gyoza@comcast.net wrote: > >> Art Alexion wrote: > >>>> nameserver 192.168.1.1 > >> > >> I think that is the only line you need. You could change/or add > >> nameserver lines to point to the DNS server(s) that your router was > >> assigned though your ISP's DHCP server. > > > > That's what I was thinking, but would it, in fact, help, or just slow > > things down more? > > I think the servers will be used in sequence. If one fails, it will try > the next. I don't know if it's any more sophisticated than that. -- _____________________________________________________________ Art Alexion Arthur S. Alexion LLC PGP fingerprint: 52A4 B10C AA73 096F A661 92D2 3B65 8EAC ACC5 BA7A The attachment - signature.asc - is my electronic signature; no need for alarm. Info @ http://mysite.verizon.net/art.alexion/encryption/signature.asc.what.html _____________________________________________________________ Attachment:
pgpb2eHBxlQW6.pgp ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|