Sponsored Content
Top Forums UNIX for Advanced & Expert Users best solution for managing many nameservers Post 33504 by RTM on Tuesday 7th of January 2003 02:32:31 PM
Old 01-07-2003
You didn't mention what OS....so I'll try to cover different ones:

One option - Webmin.

It's a web-based interface for system administration - good point: it's free. Whether it will be what you want I'm not sure. I only know about it because there was one person asking for help in administration of DNS utilizing it Matt's webmin problems.

If you are looking to pay some $$$...
DNS Boss
For NT or 2000 - DeEnesse DNS

Just do a search on Google for DNS GUI administration and you should find lots of choices. I've been fortunate that I can still use CVS and vi for the sites I have to admin.
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

managing users

I need to setup several accounts on a solaris system. (passwd,shadow,group) My question is : How can I create a group which can access a machine, but only in certain directories? (4 Replies)
Discussion started by: SmartJuniorUnix
4 Replies

2. UNIX for Advanced & Expert Users

Managing nodes???

Does anyone know something about this? I have no idea what it means and how to do it. but if anyone can give me and explanation and also point me to a website, i'd really appreciate it (5 Replies)
Discussion started by: TRUEST
5 Replies

3. UNIX for Advanced & Expert Users

Different Nameservers for Different Domains?

I have a system that is connected to a private network with its own DNS (call it "privnet."), and is also connected to the Internet on a separate interface. Is it possible to convince this server to query the private nameserver for the private network's domain (e.g. "host foo.privnet."), and the... (2 Replies)
Discussion started by: vertigo23
2 Replies

4. What is on Your Mind?

Managing Geeks

Hi, I recently found this article in computerworld and I think it is very true - at least in my company ... what do you guys think - is the author right? Is it ignorant management that makes us IT people seem to be anti-social and weird? Please share your thoughts Kind regards zxmaus (5 Replies)
Discussion started by: zxmaus
5 Replies

5. Programming

Managing and using PTSes

Hello. I need to simulate a few serial links (doing a simulation of an application for a robot) and found socat which, at least with minicom, is working flawlessly. I would really like to make pts static: ie same numbers between reboots, and automatic (not me opening terminals and leaving... (2 Replies)
Discussion started by: erupter
2 Replies
RESOLVCONF.CONF(5)					      System Manager's Manual						RESOLVCONF.CONF(5)

NAME
resolvconf.conf -- resolvconf configuration file DESCRIPTION
resolvconf.conf is the configuration file for resolvconf(8). The resolvconf.conf file is a shell script that is sourced by resolvconf(8), meaning that resolvconf.conf must contain valid shell commands. Listed below are the standard resolvconf.conf variables that may be set. After updating this file, you may wish to run resolvconf -u to apply the new configuration. RESOLVCONF OPTIONS
interface_order These interfaces will always be processed first. If unset, defaults to the following:- lo lo[0-9]* dynamic_order These interfaces will be processed next, unless they have a metric. If unset, defaults to the following:- tap[0-9]* tun[0-9]* vpn vpn[0-9]* ppp[0-9]* ippp[0-9]* search_domains Prepend search domains to the dynamically generated list. search_domains_append Append search domains to the dynamically generated list. domain_blacklist A list of domains to be removed from consideration. To remove a domain, you can use foo.* To remove a sub domain, you can use *.bar name_servers Prepend name servers to the dynamically generated list. You should set this to 127.0.0.1 if you use a local name server other than libc. name_servers_append Append name servers to the dynamically generated list. name_server_blacklist A list of name servers to be removed from consideration. The default is 0.0.0.0 as some faulty routers send it via DHCP. To remove a block, you can use 192.168.* private_interfaces These interfaces name servers will only be queried for the domains listed in their resolv.conf. Useful for VPN domains. This is equivalent to the resolvconf -p option. state_dir Override the default state directory of /run/resolvconf. This should not be changed once resolvconf is in use unless the old direc- tory is copied to the new one. LIBC OPTIONS
The following variables affect resolv.conf(5) directly:- resolv_conf Defaults to /etc/resolv.conf if not set. resolv_conf_options A list of libc resolver options, as specified in resolv.conf(5). resolv_conf_passthrough When set to YES the latest resolv.conf is written to resolv_conf without any alteration. resolv_conf_sortlist A libc resolver sortlist, as specified in resolv.conf(5). resolv_conf_local_only If a local nameserver is configured then the default is just to specify that and ignore all other entries as they will be configured for the local nameserver. Set this to YES to list them instead, if you need working DNS and the local nameserver stops functioning at the expense of duplicated server queries. SUBSCRIBER OPTIONS
openresolv ships with subscribers for the name servers dnsmasq(8), named(8), pdnsd(8) and unbound(8). Each subscriber can create configura- tion files which should be included in in the subscribers main configuration file. dnsmasq_conf This file tells dnsmasq which nameservers to use for specific domains. dnsmasq_resolv This file tells dnsmasq which nameservers to use for global lookups. Example resolvconf.conf for dnsmasq: nameservers=127.0.0.1 dnsmasq_conf=/etc/dnsmasq-conf.conf dnsmasq_resolv=/etc/dnsmasq-resolv.conf Example dnsmasq.conf: listen-address=127.0.0.1 conf-file=/etc/dnsmasq-conf.conf resolv-file=/etc/dnsmasq-resolv.conf named_options Include this file in the named options block. This file tells named which nameservers to use for global lookups. named_zones Include this file in the named global scope, after the options block. This file tells named which nameservers to use for specific domains. Example resolvconf.conf for named: nameservers=127.0.0.1 named_options=/etc/named-options.conf named_zones=/etc/named-zones.conf Example named.conf: options { listen-on { 127.0.0.1; }; include /etc/named-options.conf; }; include /etc/named-zones.conf; pdnsd_conf This is the main pdnsd configuration file which we modify to add our forward domains to. If this variable is not set then we rely on the pdnsd configuration file setup to read pdnsd_resolv as documented below. pdnsd_resolv This file tells pdnsd about global nameservers. If this variable is not set then it's written to pdnsd_conf. Example resolvconf.conf for pdnsd: nameservers=127.0.0.1 pdnsd_conf=/etc/pdnsd.conf # pdnsd_resolv=/etc/pdnsd-resolv.conf Example pdnsd.conf: global { server_ip = 127.0.0.1; status_ctl = on; } server { # A server definition is required, even if emtpy. label="empty"; proxy_only=on; # file="/etc/pdnsd-resolv.conf"; } unbound_conf This file tells unbound about specific and global nameservers. Example resolvconf.conf for unbound: nameservers=127.0.0.1 unbound_conf=/etc/unbound-resolvconf.conf Example unbound.conf: include: /etc/unbound-resolvconf.conf SEE ALSO
resolv.conf(5) and resolvconf(8). AUTHORS
Roy Marples <roy@marples.name> BUGS
Please report them to http://roy.marples.name/projects/openresolv BSD
March 19, 2012 BSD
All times are GMT -4. The time now is 09:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy