Isc Bind 9 for windows


Replacing ms dns with bind9 is an better idea here is why:
1.It's really faster (noticed when i run first query on that machine and had lower latency)
2.Better security (windows2k is not supported with patches in future)
3.You can migrate easily to linux after that ;)

Download from isc.org unzip it and run the installer (bindinstaller.exe) from inside directory

http://www.isc.org/sw/dl/?pkg=bind/contrib/ntbind-9.3.1/
BIND9.3.1.zip&name=BIND%209.3.1%20Windows%20Binaries


Install the package as service (there is an setup inside zip)

create etc/named.conf with folowing content

zone "." {
type hint;
file "named.root";
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" {
type master;
file "named.local";
};

#isc bind is installed in this dir c:\winnt\system32\dns

include "d:\winnt\system32\dns\named.zones";

options
{
directory "c:\windows\system32\dns\etc";
};

download root dns server list "named.ca" from FTP.RS.INTERNIC.NET (anonymous ftp)


create localhost.zone with following content

$TTL 86400
$ORIGIN localhost.
@ 1D IN SOA @ root (
44 ; serial (d. adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum

1D IN NS @
1D IN A 127.0.0.1
localhost.localdomain. IN A 127.0.0.1


create named.local
@ IN SOA localhost. root.localhost. (
19 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
IN NS localhost.

1 IN PTR localhost.

Is time now for named.zones that will contain (shock) zone files

zone "example.com" IN {
type master;
file "example.com.db";
};

Where example.com.db will be created like this (with this content)

example.com. IN SOA ns1.example.com. hostmaster.example.com. (
200509121 ; Serial
30800 ; Refresh
7200 ; Retry
604800 ; Expire
300 ) ; Minimum
example.com. IN NS ns1.example.com.
example.com. IN NS ns2.example.com.
example.com. IN MX 10 mail.example.com.
www.example.com. IN A 192.168.0.3
example.com. IN A 192.168.0.3
mail.example.com. IN A 192.168.0.3
ftp.example.com. IN A 192.168.0.3



Start the server with this command (to see if any errors )
bin/named -g -f -d 5

If server responds to queries

try dig example.com @localhost

next step is to enable it as service and remove ms dns server (it's that easy to replace monopoly ;))

Share this page:

7 Comment(s)

Add comment

Comments

From: Anonymous at: 2005-11-01 17:25:19

How about some GUI tool, for those lazy admins, or unexperienced users, who might want to try BIND? Maybe they're not so keen on manually editing the configuration files.

From: Anonymous at: 2005-11-06 22:26:03

Lazy, inexperienced folks shouldn't be administering servers.

From: Anonymous at: 2005-12-06 03:07:36

Try http://www.webmin.com/ (webmin) is an excellent tool to administer you server from a remote location .... :)

From: mariuz at: 2005-12-12 19:31:20

you can write one very easy in lazarus or wxwidgets

From: Anonymous at: 2005-11-08 22:16:22

I replaced ours this year with ISC DHCP and ISC Bind. You'll want to make sure you properly handle the "_" zones that Windows AD servers use. We just use IP based auth to allow them (Domain Member Servers) to make their dynamic updates into those zones. We use dynamic updates throughout and have written simple commmand line tools that allow us to add/del entries.


Seems to be much more reliable/predictable than Windows AD stuff (we run ours on Linux of course).

From: mariuz at: 2006-02-07 15:51:48

We move dns from w2k dns server to windows Bind9 server

the we will move it to linux bind9 (that is the most easy step)

You can skip the w2k dns to windows bind9 migration and copy the zone files to linux and then configure them manually (create the configuration for zone files as in example)

From: Anonymous at: 2006-02-04 13:20:10

Hi

Is i posible to migrate current w2k dns server to Isc Bind 9 on linux?

tks