> SJM> This is my config on my home machine (I'm not really a ampr.org
> SJM> primary, but I've told my pc I am, and have a copy of the
> SJM> ampr.org domain on the local disk.
>
> Don't set yourself up as primary when you're not. Otherwise, you will
> furnish authoritative answers to others if they query you, and they will be
> wrong.
Yes, being pedantic you're right. However, I've not told anyone I'm acting
as a nameserver, and the use is purely internal, between my 2 pcs. I
could even setup named to only allow queries from my 2 PCs, this being a
useful new feature.
I prefer to have a good source of the ampr.org domain to resolve Spanish
ampr.org addresses, and the best source is, I guess, the ucsd.edu DNS
server.
> If you really want to have the whole AMPR.ORG zone file on your disk, then
> set yourself up as secondary so you can't hurt anything. If you don't want
> your secondary server to update the zone file automatically, supply a fake
> address in your own named.boot file for the zone master. At least this way,
> when your unrefreshed zone file does eventually expire, you will stop
> setting the authoritative answer bit.
Again true, but for me more bother than it's worth.
> On the other hand, why bother to have the AMPR.ORG zone file on your disk if
> you are not going to operate as a real secondary and update it? You are
> never going to need the vast majority of the file, and your server will
> cache whatever it gets from the real servers.
True, assuming you query a real Internet DNS server, and are permanently
connected to the Internet. A caching server in this case is not much use
if my daily connection time to the Internet is very limited.
Nevertheless, as you state, doing things properly, people should be aware
of the consequences of settting up a nameserver.
-- regards,Simon J Mudd, Madrid SPAIN +34-1-559 2854 e-mail: terhi.victor@logonet.com [short messages - from radio hams] ----> ucdvdca@aknt.co.za