Sponsored Content
Special Forums UNIX and Linux Applications BIND (Name Server & Resolver) Post 302227620 by Sandia_man on Thursday 21st of August 2008 03:53:30 PM
Old 08-21-2008
BIND (Name Server & Resolver)

Hi, i'm looking information about how BIND (Name Server & Resolver) works... And how Server/Client communicates...
I found a lot of information of what BIND is and how to configure it, but nothing about how it works, does anybody know where i can found something useful??
I don't need code, just the ideas...

thank you very much!!!
 

9 More Discussions You Might Find Interesting

1. IP Networking

the bind server can't start

I use the "rndc start" to start the bind server . but the server can't be started. it says "connection refused" I don't know what happened,and how to resolve it. Would somebody can help me? (2 Replies)
Discussion started by: cnyifeng
2 Replies

2. UNIX for Dummies Questions & Answers

nslookup *** Can't initialize resolver

Has anyone seen this message before? I have a DNS problem. Recently DNS has been moved to two new servers, which I can ping. I changed the /etc/resolv.conf to point to these boxes but now I get the *** Can't initialize resolver message. Any ideas? (2 Replies)
Discussion started by: korfnz
2 Replies

3. UNIX for Dummies Questions & Answers

FTP, DNS & BIND

Hi GURUs, I have two queries. 1)I know I can use FTP clients for my File transfer needs, but I want to learn FTP thru command line, any one can point me to some good online resource available to learn FTP command line with examples, of course free except UNIX man pages. 2) Our company has... (4 Replies)
Discussion started by: patras
4 Replies

4. Solaris

How to bind from a NIS slave server

Hi All, I have a client already binded with a NIS master server. Now, I want to bind this particular client to one of NIS slave. How to do it? Thanks, Deepak (2 Replies)
Discussion started by: naw_deepak
2 Replies

5. Debian

nss_ldap failed to bind to LDAP server

Hi every body! I have an debian lenny server with samba and openldap on it. 1. Problem: i can not login ldap user auth.log: nss_ldap: could not connect to any LDAP server as cn=admin,dc=innsbruck,dc=sti,dc=at - Can't contact LDAP server 2. Problem: auth.log: nss_ldap: failed to bind to... (1 Reply)
Discussion started by: magge
1 Replies

6. IP Networking

Freebsd Bind DNS server - multiple subnets

Hello all, I have configured Freebsd 8.1 Bind DNS as DNS server for intrenal domain and clients on one subnet 192.168.10.0/24 . What do I have to change in zone file and in in-addr.arpa zone file if I have two additional subsets 192.168.20.0/24 and 192.168.30.0/24? Do I have to create another... (0 Replies)
Discussion started by: kreno
0 Replies

7. Red Hat

Reporting and administration tool for bind server

Hi Friends, I have two DNS (bind 9) servers (master and slave) running in my network. I want to impliment one reporting and administration tool for these DNS servers. Please suggest me which one is good for this. Regards, Arumon (2 Replies)
Discussion started by: arumon
2 Replies

8. Solaris

BIND DNS Server issue on Solaris 10

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. Ubuntu

Bind dns server zone file

I have a couple of zone conf files for the BIND server. There are some records that contains the "IN" statement and some do not. But anyway this works. So my question is what this "IN" is intended for? Here is the zone file example: ORIGIN . $ttl 60 example.com. IN SOA ... (4 Replies)
Discussion started by: andriesh
4 Replies
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)
All times are GMT -4. The time now is 08:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy