[NTLUG:Discuss] Messed up Named.conf file

[Jack Snodgrass]

pdnsd is pretty slick. You can set it up to be a DNS. 
it will use your /etc/hosts file for local stuff
and use your ISPs DNSes for non-local stuff. You can 
define DNSes that aren't always connected and it will 
use them when they are there and not use them when they 
aren't there. You can say that some dnses will 
handle a domain like private.net and that other dnses
should not hanlde that domain. 

Sounds like it might help in your situation. 

look for the latest version on freshmeat. 

jack 


On Mon, 2002-07-29 at 20:15, Stephen Davidson wrote:
> Greetings.
> 
> I seem to have messed up my named.conf file (Bind 9).
> I am trying to set up a name server on my LAN, which has a dialup connect to the internet.
> 
> Initially, it is forwarding to the specified DNS servers ok.  I would prefer the following;
> 1) That it read/used my system's hosts file (something that it is not doing).  The other machines on my network are named in my server's hosts file, and it would be nice if the other machines on my 
> network could access that information.   It did that originally, but then I made a change w/o saving the original file (Stupid User, I know), and broke something.
> 2) My ISP has several different DNS servers on their Dialups.  I would prefer that one of them was used rather than the static ones I have programmed in at the moment.
> 
> Thanks,
> Steve
> 
> 
> -- 
> Java Developer
> Looking for a new job opportunity
> 214-724-7741
> ----
> 

> # Copyright (c) 2001 SuSE GmbH Nuernberg, Germany
> #
> # Author: Frank Bodammer <feedback at suse.de>
> #
> # /etc/named.conf
> #
> # This is a sample configuration file for the name server BIND9.
> # It works as a caching only name server without modification.
> #
> # A sample configuration for setting up your own domain can be
> # found in /usr/share/doc/packages/bind9/sample-config.
> #
> # A description of all available options can be found in
> # /usr/share/doc/packages/bind9/misc/options.
> 
> options {
> 
> 	# The directory statement defines the name server´s
> 	# working directory
> 
> 	directory "/var/named";
> 
> 	# The forwarders record contains a list of servers to
> 	# which queries should be forwarded. Enable this line and
> 	# modify the IP-address to your provider's name server.
> 	# Up to three servers may be listed.
> 
> 	forwarders { 198.6.1.194; 198.6.100.194; };
> 
> 	# Enable the next entry to prefer usage of the name
> 	# server declared in the forwarders section.
> 
> 	forward first;
> 
> 	# The listen-on record contains a list of local network
> 	# interfaces to listen on. Optionally the port can be 
> 	# specified. Default is to listen on all interfaces found
> 	# on your system. The default port is 53.
> 
> 	listen-on port 53 { localhost; 192.168.1.1; };
> 
> 	# The listen-on-v6 record enables or disables listening
> 	# on IPV6 interfaces. Allowed values are 'any' and 'none'
> 	# or a list of addresses. IPv6 can only be used with 
> 	# kernel 2.4 in this release.
> 
> 	listen-on-v6 { any; };
> 
> 	# The next three statements may be needed if a firewall
> 	# stands between the local server and the internet.
> 
> 	#query-source address * port 53;
> 	#transfer-source * port 53;
> 	#notify-source * port 53;
> 
> 	# The allow-query record contains a list of networks or
> 	# IP-addresses to accept and deny queries from. The 
> 	# default is to allow queries from all hosts.
> 
> 	allow-query { 127.0.0.1; 192.168.0.0/16; };
> 
> 	# If notify is set to yes (default), notify messages are
> 	# sent to other name servers when the the zone data is
> 	# changed. Instead of setting a global 'notify' statement
> 	# in the 'options' section, a separate 'notify' can be
> 	# added to each zone definition.
> 
> 	notify no;
> };
> 
> # The following three zone definitions don't need any modification.
> # The first one defines localhost while the second defines the
> # reverse lookup for localhost. The last zone "." is the 
> # definition of the root name servers.
> 
> zone "localhost" in {
> 	type master;
> 	file "localhost.zone";
> };
> 
> #zone "168.192.in-addr.arpa" in {
> #	type master;
> #	file "192.168.zone";
> #};
> 
> zone "0.0.127.in-addr.arpa" in {
> 	type master;
> 	file "127.0.0.zone";
> };
> 
> zone "." in {
> 	type hint;	
> 	file "root.hint";
> };
> 
> # You can insert further zone records for your own domains below.
>