[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Dynamisches DNS



Ich habe erste Erfolge erreicht:

Hier die modifizierten Dateien:

/etc/bind/debian-edu/named.conf.options

#include "/etc/bind/ddns.key";

options {

//ddns

directory "/var/cache/bind";

// If there is a firewall between you and nameservers you want

// to talk to, you might need to uncomment the query-source

// directive below. Previous versions of BIND always asked

// questions using port 53, but BIND 8.1 and later use an unprivileged

// port by default.

// query-source address * port 53;

// If your ISP provided one or more IP addresses for stable

// nameservers, you probably want to use them as forwarders.

// Uncomment the following block, and insert the addresses replacing

// the all-0's placeholder.

// forwarders {

// By special request from the good people inside Skoleetaten i

// Oslo:

// 193.156.192.40;

// 193.156.192.50;

// Skoleetaten i Oslo end of block

// 0.0.0.0;

// };

// Limiting access to skolelinux hosts

allow-recursion {

skolelinux;

};

allow-transfer {

skolelinux;

};

allow-query {

skolelinux;

};

version "BIND (Skolelinux)";

auth-nxdomain no; # conform to RFC1035

provide-ixfr yes;

};

/etc/bind/debian-edu/named-bind9.conf

// This is the primary configuration file for the BIND DNS server named.

//

// Please read /usr/share/doc/bind/README.Debian for information on the

// structure of BIND configuration files in Debian for BIND versions 8.2.1

// and later, *BEFORE* you customize this configuration file.

//

key DHCP_UPDATER {

algorithm HMAC-MD5.SIG-ALG.REG.INT;

secret hDK4lw3Y2QpJ1XdxDKKLHg==;

};

acl skolelinux {

// Adding the entire 10.0.0.0/8 even if only a small fraction of

// it is used

10.0.0.0/8;

// Ditto for 192.168.0.0/16

192.168.0.0/16;

// localhost

127.0.0.0/8;

};

include "/etc/bind/debian-edu/named.conf.options";

#include "/var/run/bind/named-debian-edu.options";

include "/etc/bind/rndc.key";

// control where to allow rndc from

controls {

inet 127.0.0.1 allow { 127.0.0.1; } keys { "rndc-key"; };

};

// reduce log verbosity on issues outside our control

logging {

category lame-servers { null; };

};

// prime the server with knowledge of the root servers

zone "." {

type hint;

file "/etc/bind/db.root";

};

// be authoritative for the localhost forward and reverse zones, and for

// broadcast zones as per RFC 1912

zone "localhost" {

type master;

file "/etc/bind/db.local";

};

zone "127.in-addr.arpa" {

type master;

file "/etc/bind/db.127";

};

zone "0.in-addr.arpa" {

type master;

file "/etc/bind/db.0";

};

zone "255.in-addr.arpa" {

type master;

file "/etc/bind/db.255";

};

// Skolelinux zones

zone "0.10.in-addr.arpa" {

type master;

file "/etc/bind/debian-edu/db.10";

allow-update { key DHCP_UPDATER; };

};

zone "0.168.192.in-addr.arpa" {

type master;

file "/etc/bind/debian-edu/db.192.168";

};

zone "intern" {

type master;

file "/etc/bind/debian-edu/db.intern";

allow-update { key DHCP_UPDATER; };

};

// add entries for other zones below here

In /etc/dhcp3/dhcpd.conf habe ich folgende Zeilen eingefügt

include "/etc/dhcp3/ddns.key";

ddns-update-style interim;

ddns-domainname "0.10.in-addr.arpa";

#ddns-domainname "intern";

#ignore client-updates;

update-static-leases true;

zone 0.10.in-addr.arpa.{ primary 127.0.0.1;key DHCP_UPDATER;}

authorative;

Und die Datei /etc/dhcp3/ddns.key;

key DHCP_UPDATER {

algorithm HMAC-MD5.SIG-ALG.REG.INT;

secret hDK4lw3Y2QpJ1XdxDKKLHg==;

};

Ich kann da sicherlich noch einiges verbessern, aber was mich momentan stört ist, dass ich die Clients nur mit Namen der Art <hostname>.0.10.in-addr.arpa ansprechen kann.

Hat jemand eine Idee, wie ich die Konfiguration verbessern kann, so dass <hostname> reicht?

Könnte man die Verknüpfung von Bind und DHCP nicht als Standart einbauen, oder besser, direkt auf dnsmasq umsteigen?

MfG

E. Aysal


Reply to: