cool find.

On Sunday, January 26, 2003, at 08:59 AM, pete(a)dunnington.u-net.com wrote: I cat'ed the files and commands, and transferred them through the network to another machine. /etc/resolv.conf ---------------- nameserver 24.92.33.2 nameserver 24.92.33.3 nameserver 192.168.0.1 /etc/config/static-route.options -------------------------------- # static-route.options # # The network startup script, /etc/init.d/network, invokes this # script to set static routes. Site-dependent static routes should # be put here. # # Because name services are not active when this file is invoked, any # names used here should be defined in /etc/hosts. # # Read `man route`. # # Since $ROUTE and $QUIET are set in /etc/init.d/network, it is convenient # to use `route` commands similar to the following here: # # $ROUTE $QUIET add -net 10 192.0.2.3 # or # $ROUTE $QUIET add 192.168.1.1 192.0.2.5 $ROUTE $QUIET add net default 192.168.0.1 output of netstat -ia --------------------- Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ec0 1500 192.168 sgi_indigo2 122 0 43 0 9 224.0.0.1 08:00:69:09:26:f7 lo0 8304 loopback 127.0.0.1 2790 0 2790 0 0 224.0.0.1 output of netstat -rn --------------------- Routing tables Internet: Destination Gateway Netmask Flags Refs Use Interface default 192.168.0.1 UGS 0 0 ec0 127.0.0.1 127.0.0.1 UH 19 2 lo0 192.168 link#1 0xffffff00 UC 0 0 ec0 192.168.0.44 127.0.0.1 UGHS 0 0 lo0 192.233.228 link#1 0xffffff00 UCS 0 0 ec0 192.233.229 link#1 0xffffff00 UCS 0 0 ec0 192.233.230 link#1 0xffffff00 UCS 0 0 ec0 192.233.231 link#1 0xffffff80 UCS 0 0 ec0 192.233.231.128 link#1 0xffffffc0 UCS 0 0 ec0 192.233.231.192 link#1 0xffffffe0 UCS 0 0 ec0 224 link#1 0xf0000000 UCS 0 0 ec0 255.255.255.255 192.168.0.255 UGHS 0 0 ec0 output of ifconfig -a --------------------- ec0: flags=400c43<UP,BROADCAST,RUNNING,FILTMULTI,MULTICAST,IPALIAS> inet 192.168.0.44 netmask 0xffffff00 broadcast 192.168.0.255 lo0: flags=1849<UP,LOOPBACK,RUNNING,MULTICAST,CKSUM> inet 127.0.0.1 netmask 0xff000000 My router is a Netgear RT-311. It's set up to be used as a DNS, and really doesn't do much routing, other than to route incoming traffic on port 80 to my webserver (when it's actually running) I can communicate with machines on the local network via their IP addresses, and I can also access remote servers if I manually enter the IP address into a ping command or a netscape window. I cannot ping an address directly, for example "ping www.google.com" yields "ping: Cannot resolve "www.google.com"(Unknown host)" I have tried nslookup, and it doesn't work. For some reason, nslookup does work on all the machines on my network. On the Indigo2, it hangs for a while, then eventually returns: *** Can't find server name for address 24.92.33.2; Timed out *** Can't find server name for address 24.92.33.3; Timed out *** Can't find server name for address 192.168.0.1; Non-existent host/domain *** Default servers are not available On my PowerMac G4 (Mac OS X) I get: *** Can't find server name for address 192.168.0.1: Non-existent host/domain *** Default servers are not available On my old Linux box (Slackware 8.0 on a K6-233), I get: Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing. Server: 192.168.0.1 Address: 192.168.0.1#53 Non-authoritative answer: Name: www.google.com Address: 216.239.53.100 The odd thing is that I really didn't give the Linux box any different information than the Mac. I just assigned an IP address, punched in "192.168.0.1" for a DNS server, and assigned some arbitrary host name. In the case of the Linux box I jokingly called it "mainframe", even though it it only used to shuffle files around and for IRC via an old Wyse terminal. The mac is called "SarkMac" (OK, so I'm not that creative) I am rather confused about what to use for a domain name on a small local network. For a while I used 'home' or something. Does it really matter? Does it have to be uniform? The ironic thing is that I know a lot about networking and the associated technology, but there are just a couple little areas I'm fuzzy in, or where the concepts never quite clicked. This is further complicated by the fact that I use so many different platforms - a couple flavors of Unix, different versions of Mac OS and one Windows machine. Everything is called something different in every system, and some systems have more options and settings than others. Any help would be appreciated. This is a good excuse to finally learn these little things I have been ignoring until now <grin> Thanks for your help! Ian Primus ian_primus(a)yahoo.com