Help. DDNS setup problem ??
Mark Andrews
Mark_Andrews at isc.org
Tue Jan 10 23:34:03 UTC 2006
> I don't have a clue what's going wrong with my damn ddns setup. I set
> everything right, I hope, but the forward zone is not updatet. Who can
> help me to get it work. Why does named give me a update denied message
> ?? I set the keyfiles identical in dhcpd.conf and named.conf ? I wan't
> that winxp clients are automatically update their names in the dns
> database. The reverse zone is updated, but the forward zone sucks ?
>
> /var/log/massages
>
>
> Jan 10 20:10:29 gateway named[3806]: client 192.168.1.1#32836: updating
> zone '1.168.192.in-addr.arpa/IN': deleting an rrset
> Jan 10 20:10:29 gateway named[3806]: client 192.168.1.1#32836: updating
> zone '1.168.192.in-addr.arpa/IN': adding an RR
This is your dhcp server.
> Jan 10 20:10:29 gateway dhcpd: added reverse map from
> 30.1.168.192.in-addr.arpa. to duke.apollo.lokal
> Jan 10 20:10:29 gateway dhcpd: DHCPREQUEST for 192.168.1.30 from
> 00:0c:6e:2b:84:bb via eth0
> Jan 10 20:10:29 gateway dhcpd: DHCPACK on 192.168.1.30 to
> 00:0c:6e:2b:84:bb via eth0
> Jan 10 20:10:29 gateway named[3806]: client 192.168.1.30#1143: update
> 'apollo.lokal/IN' denied
This is not your dhcp server.
You have to tell dhcpd that it is to update the forward zone.
> /etc/named.conf
>
> acl apollo {
> 192.168.1.0/24; 127.0.0.1/8;
> };
>
> # Section to allow rndc connection from localhost
>
> controls {
> inet 127.0.0.1 allow { localhost; } keys {
> keyfile; };
> };
>
>
> options {
>
> # The directory statement defines the name server's working
> directory
>
> directory "/var/lib/named";
>
> # Write dump and statistics file to the log subdirectory. The
> # pathenames are relative to the chroot jail.
>
> dump-file "/var/log/named_dump.db";
> statistics-file "/var/log/named.stats";
>
> # The forwarders record contains a list of servers to which
> queries
> # should be forwarded. Enable this line and modify the IP
> address to
> # your provider's name server. Up to three servers may be
> listed.
> # Condor Nameserver : 194.120.164.22
>
> forwarders { 194.120.164.22; 194.25.2.129; };
>
> # Enable the next entry to prefer usage of the name server
> declared in
> # the forwarders section.
>
> #forward first;
> forward only;
>
> # The listen-on record contains a list of local network
> interfaces to
> # listen on. Optionally the port can be specified. Default is
> to
> # listen on all interfaces found on your system. The default
> port is
> # 53.
>
> listen-on port 53 { 192.168.1.1; };
>
> # The listen-on-v6 record enables or disables listening on IPv6
> # interfaces. Allowed values are 'any' and 'none' or a list of
> # addresses.
>
> listen-on-v6 { none; };
>
> # The next three statements may be needed if a firewall stands
> between
> # the local server and the internet.
>
> query-source address * port 53;
> # transfer-source * port 53;
> # notify-source * port 53;
>
> # The allow-query record contains a list of networks or IP
> addresses
> # to accept and deny queries from. The default is to allow
> queries
> # from all hosts.
>
> allow-query { apollo; };
>
> # If notify is set to yes (default), notify messages are sent
> to other
> # name servers when the the zone data is changed. Instead of
> setting
> # a global 'notify' statement in the 'options' section, a
> separate
> # 'notify' can be added to each zone definition.
>
> notify no;
> #
> #
> auth-nxdomain yes;
>
> };
>
> # To configure named's logging remove the leading '#' characters of the
> # following examples.
> #logging {
> # # Log queries to a file limited to a size of 100 MB.
> # channel query_logging {
> # file "/var/log/named_querylog"
> # versions 3 size 100M;
> # print-time yes; // timestamp log
> entries
> # };
> # category queries {
> # query_logging;
> # };
> #
> # # Or log this kind alternatively to syslog.
> # channel syslog_queries {
> # syslog user;
> # severity info;
> # };
> # category queries { syslog_queries; };
> #
> # # Log general name server errors to syslog.
> # channel syslog_errors {
> # syslog user;
> # severity error;
> # };
> # category default { syslog_errors; };
> #
> # # Don't log lame server messages.
> # category lame-servers { null; };
> #};
>
> # The following zone definitions don't need any modification. The
> first one
> # is the definition of the root name servers. The second one defines
> # localhost while the third defines the reverse lookup for localhost.
>
> key keyfile {
> algorithm HMAC-MD5.SIG-ALG.REG.INT;
> secret "xxxxxxxxxx==";
> };
>
> zone "." in {
> type hint;
> file "root.hint";
> };
>
> zone "localhost" in {
> type master;
> file "localhost.zone";
> };
>
> zone "0.0.127.in-addr.arpa" in {
> type master;
> file "127.0.0.zone";
> };
>
> # Include the meta include file generated by SuSEconfig.named. This
> includes
> # all files as configured in NAMED_CONF_INCLUDE_FILES from
> # /etc/sysconfig/named
>
> # include "/etc/named.conf.include";
>
> # You can insert further zone records for your own domains below or
> create
> # single files in /etc/named.d/ and add the file names to
> # NAMED_CONF_INCLUDE_FILES.
> # See /usr/share/doc/packages/bind/README.SuSE for more details.
>
>
> zone "apollo.lokal" in {
> allow-update { key keyfile; };
> type master;
> file "dyn/apollo.lokal.zone";
> notify yes;
> };
> zone "1.168.192.in-addr.arpa" in {
> allow-update { key keyfile; };
> type master;
> file "dyn/1.168.192.in-addr.arpa.zone";
> notify yes;
> };
> # dhcpd.conf
> #
> # Sample configuration file for ISC dhcpd
> #
> # if you want to use dynamical DNS updates, you should first read
> # read /usr/share/doc/packages/dhcp-server/DDNS-howto.txt
> #
> ddns-update-style interim;
> #
> update-static-leases true;
> #
> ddns-domainname "apollo.lokal";
>
>
> key keyfile {
> algorithm HMAC-MD5.SIG-ALG.REG.INT;
> secret "xxxxxxxxxx==";
> };
>
> # If this DHCP server is the official DHCP server for the local
> # network, the authoritative directive should be uncommented.
>
> authoritative ;
>
> # Use this to send dhcp log messages to a different log file (you also
> # have to hack syslog.conf to complete the redirection).
>
> log-facility local7;
>
> # This is a very basic subnet declaration.
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
> range 192.168.1.110 192.168.1.150;
> option routers 192.168.1.1;
> option domain-name "apollo.lokal";
> option domain-name-servers 192.168.1.1;
> default-lease-time 43200;
> max-lease-time 86400;
> }
>
> zone apollo.lokal. {
> primary 192.168.1.1;
> key keyfile;
> }
> zone 1.168.192.in-addr.arpa. {
> primary 192.168.1.1;
> key keyfile;
> }
>
> # This declaration allows BOOTP clients to get dynamic addresses,
> # which we don't really recommend.
> #subnet 10.254.239.32 netmask 255.255.255.224 {
> # range dynamic-bootp 10.254.239.40 10.254.239.60;
> # option broadcast-address 10.254.239.31;
> # option routers rtr-239-32-1.example.org;
> #}
> # Hosts which require special configuration options can be listed in
> # host statements. If no address is specified, the address will be
> # allocated dynamically (if possible), but the host-specific
> information
> # will still come from the host declaration.
>
>
> /etc/dhcpd.conf
>
>
>
> permissions from /var/lib/named/dyn4 drwxr-xr-x 3 named named 4096 Jan
> 10 19:58 .
> 4 drwxr-xr-x 9 named named 4096 Dec 7 00:12 ..
> 8 -rw------- 1 named named 571 Jan 10 19:56
> 1.168.192.in-addr.arpa.zone
> 8 -rw-r--r-- 1 named named 854 Jan 10 19:58
> 1.168.192.in-addr.arpa.zone.jnl
> 8 -rw------- 1 named named 535 Jan 10 19:49 apollo.lokal.zone
> 8 drwxr-xr-x 2 named named 4096 Jan 10 07:59 save
>
>
>
> There is no *.jnl for created for the apollo.lokal.zone ? I tried
> everything, but nothing helps. It will not work. I get crazy. Who can
> help ??
>
> Thanks in advance
>
> Frank
>
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list