... ciao:
on "1-20-2004" "daniel@xxxxxxxxxxxxxxxxxxxxxxx" writ:
: in order to have /etc/named.conf you must install the caching-nameserver
: package.
... that is, i think misleading.
by nature of the application, its installation in an overwhelming
majority, would be installed as a caching local server. that aside,
'named.conf' looks awfully "necessary", and not dependent on any
'particular' configuration.
among other things, i have 'named' installed and running under
'/www', and even at that, have an "/etc/named.conf". that seems a
default location.
is it possible the system is running another bind. 'djbdns' comes
immediately to mind as a great alternative to 'named'. i would suggest
something like "socklist | fgrep 53" and see what is calling that port
...
--
... i'm a man, but i can change,
if i have to , i guess ...
-
: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
