02-06-2012
DNS Bind Upgradation in Solaris 10
Hi All ,
My current Bind version is BIND 9.6.1 and I want upgrade the same to BIND 9.8.1-P1 ,Can any one provide the steps to do the same ?
Solaris Version : 5.10 Generic_144488-11 sun4v sparc
Thanks ,
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a RedHat 7.1 box that we use for DNS in our System Engineering lab. We have a Windows 2000 box that handles DNS in our main office. The Microsoft Admin and I have been given the task of making both of our domains accessible to each other. I had originally made his domain my forwarder, so... (5 Replies)
Discussion started by: Jody
5 Replies
2. Solaris
Currently we are using Oracle9i Enterprise Edition Release 9.2.0.4.0 in sun solaris 5.9 server.
We wnt to upgrade the oracle database to 10.2g.
My doubt is that " what are the implications of this database upgradation in sun solaris server"
"whether we need to upgrade the sunsolaris 5.9... (3 Replies)
Discussion started by: vamshikrishnab
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Does anyone know anything about DNS/BIND? I need to tell my dns for every sub-domain foward on to my main domain....
so *.example.com gets sent to exmaple.com.
Any ideas. I've looked at bind on my machine and theres about 10 files....i just don't know where to put the rule or exactly... (2 Replies)
Discussion started by: elduderino
2 Replies
4. Solaris
Hi,
Can anybody help me to upgrade my machinne from solaris 8 to solaris 10
Regards,
ravich (1 Reply)
Discussion started by: ravich
1 Replies
5. Solaris
hi all
forgive my ignorance, but when IVe set up DNS Ive put in the various server details in the /etc/resolv.conf and away I go. Suddenly Ive been reading about DNS, and I need to created a /etc/named.conf file.
so, my question is this. DNS, what part does the /etc/resolv.conf play in... (3 Replies)
Discussion started by: sbk1972
3 Replies
6. UNIX for Advanced & Expert Users
Hello,
I have a question about dns file zone.
Every zone file begins like:
@ 86400 IN SOA ns1.website.com. admin@website.com. (
It means that name server ns1 is responsible for this zone.
At the ending I can add the records like
mysite.com IN A 1.2.3.4
So it will... (2 Replies)
Discussion started by: mirusnet
2 Replies
7. UNIX for Advanced & Expert Users
I'd like to get some opnions on choosing DNS server:
Windows DNS vs Linux BIND comparrsion:
1) managment, easy of use
2) Security
3) features
4) peformance
5) ??
I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies
8. Solaris
Hi all,
I have some sort of problem with BIND DNS server my environment as follows.
bash-3.00# cat /etc/release
Solaris 10 6/06 s10s_u2wos_09a SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to... (3 Replies)
Discussion started by: h@foorsa.biz
3 Replies
9. Red Hat
Gurus
I have configured bind 9 on Red hat EL 6.4, it can resolve from hostname i.e from domain name (like cnn.com, bbc.com)but through IP its shows following error. Need your expert opinion to solve it.
error
84.23.97.31
Server: 192.168.31.24
Address: 192.168.31.24#53
** server can't... (1 Reply)
Discussion started by: smazshah
1 Replies
LEARN ABOUT DEBIAN
isc-hmac-fixup
ISC-HMAC-FIXUP(1) BIND9 ISC-HMAC-FIXUP(1)
NAME
isc-hmac-fixup - fixes HMAC keys generated by older versions of BIND
SYNOPSIS
isc-hmac-fixup {algorithm} {secret}
DESCRIPTION
Versions of BIND 9 up to and including BIND 9.6 had a bug causing HMAC-SHA* TSIG keys which were longer than the digest length of the hash
algorithm (i.e., SHA1 keys longer than 160 bits, SHA256 keys longer than 256 bits, etc) to be used incorrectly, generating a message
authentication code that was incompatible with other DNS implementations.
This bug has been fixed in BIND 9.7. However, the fix may cause incompatibility between older and newer versions of BIND, when using long
keys. isc-hmac-fixup modifies those keys to restore compatibility.
To modify a key, run isc-hmac-fixup and specify the key's algorithm and secret on the command line. If the secret is longer than the digest
length of the algorithm (64 bytes for SHA1 through SHA256, or 128 bytes for SHA384 and SHA512), then a new secret will be generated
consisting of a hash digest of the old secret. (If the secret did not require conversion, then it will be printed without modification.)
SECURITY CONSIDERATIONS
Secrets that have been converted by isc-hmac-fixup are shortened, but as this is how the HMAC protocol works in operation anyway, it does
not affect security. RFC 2104 notes, "Keys longer than [the digest length] are acceptable but the extra length would not significantly
increase the function strength."
SEE ALSO
BIND 9 Administrator Reference Manual, RFC 2104.
AUTHOR
Internet Systems Consortium
COPYRIGHT
Copyright (C) 2010 Internet Systems Consortium, Inc. ("ISC")
BIND9 January 5, 2010 ISC-HMAC-FIXUP(1)