Well, when my headbone finally cracked open enough to realize just
exactly what I'm supposed to expect a caching name server to do, it
took about 30 seconds to check and see that it was already set up.

What I had been looking for was a way for the Doze boxen to,
for example, "ping abi-quality" - or see them in "network neigh..."
without going into Doze hosts files.

This is not what a caching name server does, duh.

I think what does what I want done is "WINS."

Everything else is hunky-dory, except that
# dig -x 127.0.0.1

on Ops returns:
---------------------------------------------------
rich@Ops:~$ dig -x 127.0.0.1

; <<>> DiG 9.2.2-P3 <<>> -x 127.0.0.1
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 23929
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;1.0.0.127.in-addr.arpa. IN PTR

;; Query time: 14 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Apr 21 17:55:15 2004
;; MSG SIZE rcvd: 40

rich@Ops:~$
-----------------------------------

But I'm not too terribly concerned about the "REFUSED" -
all I've got for a firewall is this:
-------------------------------------------------
oot@Ops:~# iptables -L
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere state NEW
ACCEPT tcp -- anywhere anywhere tcp dpt:http
ACCEPT tcp -- anywhere anywhere tcp dpt:https

Chain FORWARD (policy ACCEPT)
target prot opt source destination
REJECT all -- anywhere anywhere reject-with icmp-port-unreachable

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
root@Ops:~#
------------------------------------------------------------
But I'm sure as I continue to read with my new-found context, it'll
jump out at me.

Unless there's something vitally important that I fix, then please,
feel free to enlighten me and the group. :-)

Thanks!
Rich

On Thu, 22 Apr 2004 01:02:28 +0000, Rich Grise wrote:

> What I had been looking for was a way for the Doze boxen to,
> for example, "ping abi-quality"

That can be done using DNS fine.

> - or see them in "network neigh..."

For that you need Samba.

> without going into Doze hosts files.

There are a cople of ways you might go about doing that.
Either use DNS for the IP<->name mapping, and Samba for the
"network neigh..." or use Samba for both.

> This is not what a caching name server does, duh.

Indeed, it just caches mappings.

But instead of just for caching, you can setup records in a zone file on
the "named" DNS server. Or use "dnsmesq" and maintain one global "hosts"
file for that to use. In either case point your clients to your server.
Or, better yet: automate the whole lot via DHCP and DDNS. Both "dnsmesq"
and "named" can do that. When used together with "dhcpd". (The 'A' and
'PTR' DNS records would be created for the host, upon getting a lease.)

> I think what does what I want done is "WINS."

You could use that, yes.
There are four modes a node in SMB can can opperate in:
http://support.microsoft.com/support.../Q160/1/77.asp

If you don't care for a lot of (needless) broadcast trafic, setup Samba as
a NBNS (WINS) server. And point your clients there:
http://www.google.nl/groups?selm=pan...0deskt op.lan

As discribed in that post, should you use "dhcpd" allong with it: you can
automate pointing your clients to the NBNS. (Otherwise, you need to either
use broadcast, or edit the "wins server" directive on the clients for them
to know where to look.)

I have a qestion about your setup though:
Are your clients setup with static IP-adressing, or do you use DHCP?

> Everything else is hunky-dory, except that
> # dig -x 127.0.0.1
>
> on Ops returns:

[ Snip, output - missing stuff. ]

> But I'm not too terribly concerned about the "REFUSED" -

Have a look at the output of "tail /var/log/messages" after restarting
"named". If you don't get enough info add the "-d1" flag to it.
(And/or try "tcpdump -i lo" to see what's going on, at the network level.)

I have posted my (working) setup here before, but that was with 9.0 IIRC :
http://www.google.nl/groups?selm=pan...eskto p.local

As i reread it now, the "chmod -R named:named /var/run/named" should be:
chown -R named:named /var/run/named

With Slackware 9.1 - the stuff about /etc/rc.d/rc.inet2 is deprecated.
However, i edit the following in /etc/rc.d/rc.bind

bind_start() {
if [ -x /usr/sbin/named ]; then
echo "Starting BIND: /usr/sbin/named -u named"
/usr/sbin/named -u named
fi
}

--
-Menno.