On Tue, Apr 17, 2001 at 03:50:17PM -0500, Rich Puhek wrote: > Will, > > A few questions, mostly to ask yourself, that may help you find what's > going on. > > Why mess with bind on the internal machines? Why not just populate > /etc/hosts and be done with it?
will that help win.* and mac.* machines use dns? on the mac i should be able to ping (via mac software, of course) "win" or "duo" and have it work just like on a linux command line. > Regardless, which machines are entered into /etc/hosts on duo? <fix solved=yes>okay, fine. thakyouVERYmuch for pointing out how dweebie i'm being.</fix> thanks! :) > Does an nslookup or a dig against the DNS server jive with the /etc/bind > files? it did. apparently dns and dig use the same resources; the /etc/hosts file is some arbitrary "we'll use it when we damn well feel like it" sort of thing. ? > Shouldn't you have a "$ORIGIN lan." in your first file (after the "@" > sections)? isn't that assumed? or provided for by the named.conf file? > How does your machine show up in the logfiles? (something like "telnetd > ... connect from mac (192.168.1.100)" or "...connect from mac.lan. > (208..."? the conflict was DNS (/etc/bind/*) vs /etc/hosts ... heh. thanks much! -- don't visit this page. it's bad for you. take my expert word for it. http://www.salon.com/people/col/pagl/2001/03/21/spring/index1.html [EMAIL PROTECTED] http://sourceforge.net/projects/newbiedoc -- we need your brain! http://www.dontUthink.com/ -- your brain needs us!
