Freebsd Bind DNS server - multiple subnets


 
Thread Tools Search this Thread
Special Forums IP Networking Freebsd Bind DNS server - multiple subnets
# 1  
Old 08-26-2010
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 zone file for every subnet or I can just add additional subnets to existing files?

Thank you in advanced and kind regards,
Mark
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. IP Networking

DNS and two subnets

Hi guys I started to work in a small company which doesn't have infrastructure and I need to built it. My problem is: I am a student with theoretical knowledge but without practical one so I don't have any ideas how to solve my problem. I installed on CentOS 6.4 DNS and DHCP. This... (1 Reply)
Discussion started by: solaris_user
1 Replies

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

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

4. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

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

5. UNIX for Advanced & Expert Users

DNS Bind

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

6. Solaris

solaris - BIND / DNS

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

7. Solaris

Jumpstart server over Multiple subnets

Hi, I need some recommendations as to how I can create a single jumpstart server over multiple subnets and what would be the best physical server for this purpose. Thanks . (1 Reply)
Discussion started by: gunnervarma
1 Replies

8. UNIX for Dummies Questions & Answers

Dns/bind

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

9. IP Networking

New DNS Server on FreeBSD 7.0

Hope I can explain my problem well enough. I have a DNS server that I'm wanting to replace with an older system. I configured this system exactly the same way as an older system running FreeBSD 6.3. Here's the problem. Within the network, its working perfectly: performing queries, all the... (2 Replies)
Discussion started by: Alpha_Harblo
2 Replies
Login or Register to Ask a Question
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)