On Thursday 01 August 2002 08:57, Trevor Fraser wrote: >Hi, thanks. > >I've followed your advise to the point of nslookup, I get a > correct reply for the IP, but for the name 'merlin', I get: >Server: 192.168.0.1 (which is our DNS server address) >Address: 192.168.0.1#53 > >** server can't find merlin: NXDOMAIN > >What does this mean/where should I look for problems?
Hummm, [root@coyote named]# nslookup gene 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.1.1 Address: 192.168.1.1#53 ** server can't find gene: NXDOMAIN Which is *almost* exaclty what I get here. But as noted above, be aware that nslookup is a deprecated utility, and that dig or host has replaced it. In my checks here just this instant, 'dig gene' returns the ip address of the machine gene, and 'dig coyote' similarly returns the ip of that machine. I did a cat * on the contents of the /var/named dir on my firewall machine and no local records returned any ip numbers, so my hosts file is doing it all. Oddly, the 'host gene', etc, returns the NXDOMAIN error as above. OTOH, I'm NOT a bind expert, I'm home and haven't carried a briefcase in months. (based on an expert being someone who is at least 50 miles from home and carrying a briefcase :) [...] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.09% setiathome rank, not too shabby for a WV hillbilly
