|
| Bind 9 debian , Unable to add forward map ~ Fra : Glen > |
Dato : 09-04-05 13:16 |
|
Hej
Sidder og kæmper med af få DDNS til at køre,
hvergang en klient får tildelt en adresse får jeg følgende fejl
Unable to add forward map from <fqdn> <ip> timed out
og hverken forward eller rev zone bliver opdateret.
mine zoner og named.conf er blevet kontrolleret med named-checkconf og
named-checkzone og uden at finde nogle fejl.
rev og forward virker fint med statiske rekords
anyone?
/Glen
dhcpd.conf
ddns-update-style interim;
subnet 192.168.1.0 netmask 255.255.255.0 {
ignore client-updates;
log-facility local7;
authoritative;
# default gateway
option routers 192.168.1.10;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.0;
# dynamic updates
ddns-updates on;
ddns-domainname "home.mitdom.dk";
ddns-rev-domainname "1.168.192.in-addr.arpa";
option domain-name "home.mitdom.dk";
option domain-name-servers 192.168.1.10;
range dynamic-bootp 192.168.1.200 192.168.1.250;
default-lease-time 86400 ;
max-lease-time 172800;
#create your own secret with the dnssec-keygen command from
# the bind package
key mykey {
algorithm hmac-md5;
secret "nøgle";
}
zone home.mitdom.dk. {
primary 127.0.0.1;
key mykey;
}
zone 1.168.192.in-addr.arpa. {
primary 127.0.0.1;
key mykey; }
Named.conf
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in
/etc/bind/named.conf.local
key mykey {
algorithm hmac-md5;
secret "nøgle";
};
controls {
inet 127.0.0.1 allow { localhost; } keys { mykey; };
};
include "/etc/bind/named.conf.options";
// 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";
};
// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };
// From the release notes:
// Because many of our users are uncomfortable receiving undelegated
answers
// from root or top level domains, other than a few for whom that behaviour
// has been trusted and expected for quite some length of time, we have now
// introduced the "root-delegations-only" feature which applies
delegation-only
// logic to all top level domains, and to the root domain. An
exception list
// should be specified, including "MUSEUM" and "DE", and any other top
level
// domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };
include "/etc/bind/named.conf.local";
| |
Glen > (09-04-2005)
| Kommentar Fra : Glen > |
Dato : 09-04-05 19:12 |
|
Glen > > wrote:
> Hej
>
> Sidder og kæmper med af få DDNS til at køre,
>
> hvergang en klient får tildelt en adresse får jeg følgende fejl
>
> Unable to add forward map from <fqdn> <ip> timed out
>
> og hverken forward eller rev zone bliver opdateret.
>
> mine zoner og named.conf er blevet kontrolleret med named-checkconf og
> named-checkzone og uden at finde nogle fejl.
>
> rev og forward virker fint med statiske rekords
>
> anyone?
manglede at sige at bind skulle lytte på loopback adressen, som var den
adresse som jeg havde defineret at opdateringen skulle ske på, ups
options {
directory "/var/cache/bind";
listen-on {127.0.0.1; 192.168.1.10;};
/Glen
| |
|
|