10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I've installed Solaris 11.3(live media) and configured DNS. Everytime I reboot the server, resolv.conf got deleted and it created a new nsswitch.conf.
I used below to configure both settings:
# svccfg -s dns/client
svc:/network/dns/client> setprop config/nameserver = (xx.xx.xx.aa... (1 Reply)
Discussion started by: flexihopper18
1 Replies
2. Shell Programming and Scripting
Hello all,
Newbie here.
I'm currently tasked with updating rsyslog.conf and auditd.conf on a large set of servers. I know the exact logging configurations that I want to enable. I have updated both files on on a server and hope to use the updated files as a template for the rest of the... (3 Replies)
Discussion started by: Mide
3 Replies
3. Shell Programming and Scripting
I would really appreciate any assistance that I can get here.
I am fairly new to perl. I am trying to rewrite my shell scripts to perl.
Currently I have a shell script (using sed, awk, grep, etc) that gets a list of all of the zone files in a directory and then looks in named.conf for what... (0 Replies)
Discussion started by: brianjb
0 Replies
4. Red Hat
hello everyone,
I have install centos 5 recently.The file /etc/named.conf not found. I have installed BIND using yum. so now what to do ?? should i create named.conf file manually ???
please help me.
thanks,
sharlin. :) (1 Reply)
Discussion started by: sharlin
1 Replies
5. Red Hat
Hello!
I have a DNS server running named on a RHEL 6.2 for very small development servers/clients network. I see the below logs on /var/named/data/named.run
error (network unreachable) resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 198.41.0.4#53
error (network unreachable) resolving... (2 Replies)
Discussion started by: admin_xor
2 Replies
6. Solaris
Hi,
I can't rememeber what passwd is set for the "named" user in bind.
Is there possibly a default one or anyway to find it ?
I'm worried about changing it and causing other issues, if I did change it
what other files would I need to edit ?
:(
Thanks (1 Reply)
Discussion started by: sysop400
1 Replies
7. Solaris
Hello Guys,
Do we need to configure this file only if we add SAN disk or even if we add local disk, do we need to modify? (4 Replies)
Discussion started by: mokkan
4 Replies
8. Shell Programming and Scripting
Hello,
I am seeking help with someone with perl expertise that can create me a script that will read a named.conf file and create a csv or a text file on each of the zones that the named.conf contains. An excerpt of named.conf looks like:
acl "our_nets" {
127.0.0.1/32; ... (2 Replies)
Discussion started by: richsark
2 Replies
9. Shell Programming and Scripting
Hi there, Im' trying to make a script to parse the BIND configuration file from my slave DNS server and obtain a certain parameter. The named.conf file has this format:
zone "0.170.20.10.in-addr.arpa" {
type slave;
file "0/./db.0.170.20.10.in-addr.arpa.bak";
allow-notify {... (2 Replies)
Discussion started by: Citricut
2 Replies
10. UNIX for Dummies Questions & Answers
Help me!
I have problem.
I can't find named.conf file in /etc (Solaris 5.6,SPRAC)
Please! (1 Reply)
Discussion started by: nghia77
1 Replies
rndc.conf(4) File Formats rndc.conf(4)
NAME
rndc.conf - rndc configuration file
SYNOPSIS
rndc.conf
DESCRIPTION
rndc.conf is the configuration file for rndc, the BIND 9 name server control utility. This file has a similar structure and syntax to
named.conf. Statements are enclosed in braces and terminated with a semi-colon. Clauses in the statements are also semi-colon terminated.
The usual comment styles are supported:
C style /* */
C++ style // to end of line
Unix style # to end of line
rndc.conf is much simpler than named.conf. The file uses three statements: an options statement, a server statement and a key statement.
The options statement contains three clauses. The default-server clause is followed by the name or address of a name server. This host is
used when no name server is provided as an argument to rndc. The default-key clause is followed by the name of a key which is identified by
a key statement. If no keyid is provided on the rndc command line, and no key clause is found in a matching server statement, this default
key will be used to authenticate the server's commands and responses. The default-port clause is followed by the port to connect to on the
remote name server. If no port option is provided on the rndc command line, and no port clause is found in a matching server statement,
this default port will be used to connect.
After the server keyword, the server statement includes a string which is the hostname or address for a name server. The statement has two
possible clauses: key and port. The key name must match the name of a key statement in the file. The port number specifies the port to con-
nect to.
The key statement begins with an identifying string, the name of the key. The statement has two clauses. algorithm identifies the encryp-
tion algorithm for rndc to use; currently only HMAC-MD5 is supported. This is followed by a secret clause which contains the base-64 encod-
ing of the algorithm's encryption key. The base-64 string is enclosed in double quotes.
There are two common ways to generate the base-64 string for the secret. The BIND 9 program rndc-confgen(1M) can be used to generate a ran-
dom key, or the mmencode program, also known as mimencode, can be used to generate a base-64 string from known input. mmencode does not
ship with BIND 9 but is available on many systems. See the EXAMPLES section for sample command lines for each.
EXAMPLES
options {
default-server localhost;
default-key samplekey;
};
server localhost {
key samplekey;
};
key samplekey {
algorithm hmac-md5;
secret
"c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K";
};
In the above example, rndc by default uses the server at localhost (127.0.0.1) and the key called samplekey. Commands to the localhost
server use the samplekey key, which must also be defined in the server's configuration file with the same name and secret. The key state-
ment indicates that samplekey uses the HMAC-MD5 algorithm. Its secret clause contains the base-64 encoding of the HMAC-MD5 secret enclosed
in double quotes.
To generate a random secret with rndc-confgen:
rndc-confgen
A complete rndc.conf file, including the randomly generated key, will be written to the standard output. Commented out key and controls
statements for named.conf are also printed.
To generate a base-64 secret with mmencode:
echo "known plaintext for a secret" | mmencode
NAME SERVER CONFIGURATION
The name server must be configured to accept rndc connections and to recognize the key specified in the rndc.conf file, using the controls
statement in named.conf. See the sections on the controls statement in the BIND 9 Administrator Reference Manual for details.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWbind |
+-----------------------------+-----------------------------+
|Interface Stability |External |
+-----------------------------+-----------------------------+
SEE ALSO
rndc(1M), rndc-confgen(1M), attributes(5)
BIND 9 Administrator Reference Manual
SunOS 5.11 24 Dec 2008 rndc.conf(4)