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:
Hi,
I have a primary/slave Bind 9 setup running on a Solaris 10 platform. Everything is hunky dorey, except for when I make a zone file change and up the serial the file that is transferred to the slave looses all its comments, and the entries are place in alphabetical order.
I administer many... (1 Reply)
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)
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)
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)
Hy guys, I've a problem configuring my Name Server (using bind 9) which is I'ts always necessary to put all slave Name Server for a zone in the zone resource record file or db (as you prefer)?
I've this scenario:
A - my domain which is son of some TLD and I delegated into two new domains B... (1 Reply)
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)
We are currently using the famous script H2N to create our DNS zone files from a host file. However, we are moving to IPV6 soon and this script doesnt support IPV6. Is there another script/solution to creating DNS zones via a host file input? (0 Replies)
We are currently using the famous script H2N to create our DNS zone files from a host file. However, we are moving to IPV6 soon and this script doesnt support IPV6. Is there another script/solution to creating DNS zones via a host file input? Is there another solution or way to do things that I may... (0 Replies)
Discussion started by: jpolachak
0 Replies
LEARN ABOUT CENTOS
zone2ldap
zone2ldap(1) General Commands Manual zone2ldap(1)NAME
zone2ldap /- Load BIND 9 Zone files into LDAP Directory
SYNOPSIS
zone2ldap [-D Bind DN] [-w Bind Password] [-b Base DN] [-z Zone] [-f Zone File ] [-h Ldap Host] [-cd] [-v]
DESCRIPTION
zone2ldap will parse a complete BIND 9 format DNS zone file, and load the contents into an LDAP directory, for use with the LDAP sdb back-
end.
If the zone already exists, zone2ldap will exit succesfully. If the zone does not exists, or partially exists, zone2ldap will attempt to
add all/missing zone data.
Options
-b LDAP Base DN. LDAP systems require a "base dn", which is generally considered the LDAP Directory root. If the zone you are loading
is different from the base, then you will need to tell zone2ldap what your LDAP base is.
-v Print version information, and immediatly exit.
-f Zone file. Bind 9.1 compatible zone file, from which zone information will be read.
-d Dump debug information to standard out.
-w LDAP Bind password, corresponding the the value of "-b".
-h LDAP Directory host. This is the hostname of the LDAP system you wish to store zone information on. An LDAP server should be lis-
tening on port 389 of the target system. This may be ommited, and will default to "localhost".
-c This will create the zone portion of the DN you are importing. For instance, if you are creating a domain.com zone, zone2ldap should
first create "dc=domain,dc=com". This is useful if you are creating multiple domains.
-z This is the name of the zone specified in the SOA record.
EXAMPLES
Following are brief examples of how to import a zone file into your LDAP DIT.
Loading zone domain.com, with an LDAP Base DN of dc=domain,dc=com
zone2ldap -D dc=root -w secret -h localhost -z domain.com -f domain.com.zone
This will add Resource Records into an ALREADY EXISTING dc=domain,dc=com. The final SOA DN in this case, will be dc=@,dc=domain,dc=com
Loading customer.com, if your LDAP Base DN is dc=provider,dc=net.
zone2ldap -D dc=root -w secret -h localhost -z customer.com -b dc=provider,dc=net -f customer.com.zone -c
This will create dc=customer,dc=com under dc=provider,dc=net, and add all necessary Resource Records. The final root DN to the SOA will be
dc=@,dc=customer,dc=com,dc=provider,dc=net.
SEE ALSO named(8)ldap(3) http://www.venaas.no/ldap/bind-sdb/
BUGS
Send all bug reports to Jeff McNeil <jeff@snapcase.g-rock.net>
AUTHOR
Jeff McNeil <jeff@snapcase.g-rock.net>
8 March 2001 zone2ldap(1)