logo       

Re: DDNS: help updates timing out.: msg#00334

network.dhcp.isc.dhcp-server

Subject: Re: DDNS: help updates timing out.

*** From dhcp-server -- To unsubscribe, see the end of this message. ***


You've got 'zone blazebox.db' in the bind and dhcp config files, but
you use a domainname of 'blazebox.homeip.net'. So dhcpd is trying to
update a non-existant zone - bind just ignores the request hence the
timeout.

regards,
-glenn

> X-Original-To: dhcp-server@xxxxxxx
> Date: Sun, 26 Jan 2003 17:59:49 -0500 (EST)
> Subject: DDNS: help updates timing out.
> From: paul@xxxxxxxxxxxxxxxxxxx
> To: dhcp-server@xxxxxxx
> X-Priority: 3
> Importance: Normal
> X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.10; AVE: 6.17.0.2;
VDF: 6.17.0.19; host: blazebox.homeip.net)
> X-ecartis-version: Ecartis v1.0.0
> X-original-sender: paul@xxxxxxxxxxxxxxxxxxx
> X-List-ID: <dhcp-server.isc.org>
>
> *** From dhcp-server -- To unsubscribe, see the end of this message. ***
>
>
> Hello folks,
>
> I am running FreeBSD 5.0 with latest ISC bind/dhcpd servers.
>
> I have a problem with DDNS updates which are timing out and i can't seem
> to find the cause of those timeouts.
>
> I belive my config files are setup properly because DDNS works partialy
> when adding reverse maps.The clients are Win2000 and WinXP.
>
> This is what my logs say:
>
> Jan 26 17:01:54 blazebox dhcpd: Unable to add forward map from
> blaze.blazebox.homeip.net to 192.168.0.43: timed out
> Jan 26 17:03:20 blazebox dhcpd: Unable to add forward map from
> dellbox.blazebox.homeip.net to 192.168.0.254: timed out
> Jan 26 17:23:27 blazebox dhcpd: Internet Software Consortium DHCP Server
> V3.0.1rc11
> Jan 26 17:23:27 blazebox dhcpd: Copyright 1995-2003 Internet Software
> Consortium.
> Jan 26 17:23:27 blazebox dhcpd: All rights reserved.
> Jan 26 17:23:27 blazebox dhcpd: For info, please visit
> http://www.isc.org/products/DHCP
> Jan 26 17:23:27 blazebox dhcpd: Wrote 2 leases to leases file.
> Jan 26 17:23:42 blazebox dhcpd: added reverse map from
> 43.0.168.192.in-addr.arpa to blaze.blazebox.homeip.net
> Jan 26 17:23:42 blazebox dhcpd: DHCPREQUEST for 192.168.0.43 from
> 00:a0:cc:32:81:44 (blaze) via fxp0
> Jan 26 17:23:42 blazebox dhcpd: DHCPACK on 192.168.0.43 to
> 00:a0:cc:32:81:44 (blaze) via fxp0
> Jan 26 17:23:51 blazebox dhcpd: added reverse map from
> 43.0.168.192.in-addr.arpa to blaze.homeip.net
> Jan 26 17:23:51 blazebox dhcpd: DHCPREQUEST for 192.168.0.43 from
> 00:a0:cc:32:81:44 (blaze) via fxp0
> Jan 26 17:23:51 blazebox dhcpd: DHCPACK on 192.168.0.43 to
> 00:a0:cc:32:81:44 (blaze) via fxp0
> Jan 26 17:24:06 blazebox dhcpd: Unable to add forward map from
> blaze.blazebox.homeip.net to 192.168.0.43: timed out
> Jan 26 17:24:06 blazebox dhcpd: DHCPREQUEST for 192.168.0.43 from
> 00:a0:cc:32:81:44 (blaze) via fxp0
> Jan 26 17:24:06 blazebox dhcpd: DHCPACK on 192.168.0.43 to
> 00:a0:cc:32:81:44 (blaze) via fxp0
>
>
> Here is my config files:
>
> named.conf (just the relevant bits):
>
> key rndc_key {
> algorithm HMAC-MD5;
> secret
>
"p5zOSCo1BacMdKkmB9D2kDh7ndgCWtWNjuBJFBfE3cd1cl2bhIKzxIdSZe7sPgC4nmlFPMNGsb1f4cC
hlKAWrw==";
> };
>
> controls { inet 127.0.0.1 allow { localhost; } keys { rndc_key; };
> inet 192.168.0.1 allow { blazebox; } keys { rndc_key; };
> };
>
> // zone for access to domain
> zone "blazebox.db" in {
> type master;
> notify yes;
> allow-update { key rndc_key; 192.168.0.1; };
> file "blazebox.db";
> };
>
> // zone for access to domain using ip
> zone "0.168.192.in-addr.arpa" in {
> type master;
> notify yes;
> allow-update { key rndc_key; 192.168.0.1; };
> file "db.192.168.0";
> };
>
> dhcpd.conf
>
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.0.255;
> option netbios-name-servers 192.168.0.1;
> server-identifier blazebox;
> ddns-update-style interim;
> allow client-updates;
> one-lease-per-client on;
> ddns-updates on;
> ddns-ttl 3600;
> use-host-decl-names on;
>
> key rndc_key {
> algorithm hmac-md5;
> secret
>
"p5zOSCo1BacMdKkmB9D2kDh7ndgCWtWNjuBJFBfE3cd1cl2bhIKzxIdSZe7sPgC4nmlFPMNGsb1f4cC
hlKAWrw==";
> };
>
> zone blazebox.db. {
> primary 192.168.0.1;
> key rndc_key;
> }
>
> zone 0.168.192.in-addr.arpa. {
> primary 192.168.0.1;
> key rndc_key;
> }
>
> option domain-name "blazebox.homeip.net";
> option domain-name-servers 192.168.0.1
>
> default-lease-time 7200;
> max-lease-time 36000;
> authoritative;
> log-facility local7;
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
> }
>
> subnet 192.168.0.0 netmask 255.255.255.0 {
> range 192.168.0.2 192.168.0.254;
> option routers 192.168.0.1;
> ddns-domainname = "blazebox.homeip.net";
> ddns-rev-domainname = "in-addr.arpa";
> }
>
> bind has debug enabled and this is what i get from the log:
>
> Jan 26 07:40:12.860 update: info: client 192.168.0.1#54363: updating zone
> '0.168.192.in-addr.arpa/IN': deleting an rrset
> Jan 26 07:40:12.860 update: info: client 192.168.0.1#54363: updating zone
> '0.168.192.in-addr.arpa/IN': adding an RR
>
>
> The db.192.168.0 file:
>
> $ORIGIN .
> $TTL 604800 ; 1 week
> 0.168.192.in-addr.arpa IN SOA blazebox.homeip.net.
> postmaster.blazebox.homeip.net. (
> 2002111427 ; serial
> 28800 ; refresh (8 hours)
> 14400 ; retry (4 hours)
> 604800 ; expire (1 week)
> 86400 ; minimum (1 day)
> )
> NS blazebox.homeip.net.
> $ORIGIN 0.168.192.in-addr.arpa.
> 1 PTR blazebox.homeip.net.
> $TTL 3600 ; 1 hour
> 254 PTR dellbox.blazebox.homeip.net.
> 43 PTR blaze.homeip.net.
>
> The reverse map gets set and the journal file is created for the client
>
> The blazebox.db file:
>
> $TTL 3D
> @ IN SOA blazebox.homeip.net.
> postmaster.blazebox.homeip.net. (
> 2002111401 ; serial number
> 28800 ; rafresh
> 14400 ;
> 604800 ; expiration
> 86400 );
>
> @ IN NS blazebox
> @ IN NS blazebox.homeip.net.
>
> @ IN MX 10 blazebox
> @ IN MX 10 blazebox.homeip.net.
> @ IN MX 20 blaze.homeip.net.
>
> @ IN A 127.0.0.1
> @ IN A 192.168.0.1
>
> localhost IN A 127.0.0.1
> blazebox IN A 192.168.0.1
> www IN A 192.168.0.1
> ftp IN A 192.168.0.1
> mail IN MX 10 192.168.0.1
> ns IN A 192.168.0.1
> router IN A 192.168.0.1
> proxy IN A 192.168.0.1
> blaze IN A 192.168.0.43
> stonebox IN A 192.168.0.253
> dellbox IN A 192.168.0.254
>
> #www IN CNAME blazebox
> #ftp IN CNAME blazebox
> #mail IN CNAME blazebox
> #cvs IN CNAME blazebox
> #router IN CNAME blazebox
> #proxy IN CNAME blazebox
>
> this does not get updated
>
> Finally dhcpd.leases file:
>
> lease 192.168.0.43 {
> starts 0 2003/01/26 22:22:58;
> ends 1 2003/01/27 00:22:58;
> tstp 1 2003/01/27 00:22:58;
> binding state active;
> next binding state free;
> hardware ethernet 00:a0:cc:32:81:44;
> uid "\001\000\240\3142\201D";
> set ddns-rev-name = "43.0.168.192.in-addr.arpa";
> set ddns-client-fqdn = "blaze.homeip.net";
> client-hostname "blaze";
> }
> lease 192.168.0.254 {
> starts 0 2003/01/26 22:03:20;
> ends 1 2003/01/27 00:03:20;
> tstp 1 2003/01/27 00:03:20;
> binding state active;
> next binding state free;
> hardware ethernet 00:08:74:4c:72:7c;
> uid "\001\000\010tLr|";
> client-hostname "dellbox";
> }
>
> The first client runs Win2000 and the second one WinXP.
>
> In addition i use ipfilter but have udp ports 67,68 and 953 open on the lan.
>
> I just don't seem to get DDNS fully working no matter what options and
> configurations files i tried from the mailling list.
>
> I would greatly apprecite any help with properly setting up DDNS updates
> and bind.
>
> Thank you,
>
> Paul B.
>
>
>
>
> -----------------------------------------------------------------------
> List Archives : http://www.isc.org/ml-archives/dhcp-server/
> Unsubscribe : http://www.isc.org/dhcp-lists.html
> -or- : mailto:dhcp-server-request@xxxxxxx?Subject=unsubscribe
> -----------------------------------------------------------------------
>


-----------------------------------------------------------------------
List Archives : http://www.isc.org/ml-archives/dhcp-server/
Unsubscribe : http://www.isc.org/dhcp-lists.html
-or- : mailto:dhcp-server-request@xxxxxxx?Subject=unsubscribe
-----------------------------------------------------------------------




<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise