Networking Forums

Networking Forums > Computer Networking > Linux Networking > DHCPD not updating DNS Records for Linux Clients

Reply
Thread Tools Display Modes

DHCPD not updating DNS Records for Linux Clients

 
 
Dirk Sachse
Guest
Posts: n/a

 
      02-17-2004, 05:14 PM
Hi,

I am using ISC DHCPD and Bind 9.2.3 with DDNS.
My Linux Clients dont update their dynamic DNS entries properly.
Only their reverse lookup is updated.

When they request an IP it looks like this:

Feb 17 17:00:21 proxy named[15706]: client 192.168.0.4#42724: updating zone
'0.168.192.in-addr.arpa/IN': adding an RR
Feb 17 17:00:21 proxy dhcpd: delete IN PTR 81.0.168.192.in-addr.arpa. add
1800 IN PTR 81.0.168.192.in-addr.arpa. sachse-linux.sunflowers.de.:
success.
Feb 17 17:00:21 proxy dhcpd: DHCPREQUEST for 192.168.0.81 from
00:02:b3:29:ab:3c via eth0
Feb 17 17:00:21 proxy dhcpd: DHCPACK on 192.168.0.81 to 00:02:b3:29:ab:3c
via eth0

Here is the dhclient.conf of my Linux Client:

timeout 60;
retry 60;
reboot 10;
select-timeout 5;
initial-interval 2;
interface "eth0" {
send host-name "sachse-linux.sunflowers.de";
send dhcp-client-identifier 00:02:B3:29:AB:3C;
send dhcp-lease-time 3600;
supersede domain-name "sunflowers.de";
prepend domain-name-servers 192.168.0.4;
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, host-name;
require subnet-mask, domain-name-servers;
script "/sbin/dhclient-script";
send fqdn.fqdn "sachse-linux.sunflowers.de.";
send fqdn.encoded off;
send fqdn.server-update off;
}



Thanks in advance

Dirk
 
Reply With Quote
 
 
 
 
knocte
Guest
Posts: n/a

 
      02-17-2004, 07:11 PM
Dirk Sachse escribió:
> Hi,
>
> I am using ISC DHCPD and Bind 9.2.3 with DDNS.
> My Linux Clients dont update their dynamic DNS entries properly.
> Only their reverse lookup is updated.
>
> When they request an IP it looks like this:
>
> Feb 17 17:00:21 proxy named[15706]: client 192.168.0.4#42724: updating zone
> '0.168.192.in-addr.arpa/IN': adding an RR
> Feb 17 17:00:21 proxy dhcpd: delete IN PTR 81.0.168.192.in-addr.arpa. add
> 1800 IN PTR 81.0.168.192.in-addr.arpa. sachse-linux.sunflowers.de.:
> success.
> Feb 17 17:00:21 proxy dhcpd: DHCPREQUEST for 192.168.0.81 from
> 00:02:b3:29:ab:3c via eth0
> Feb 17 17:00:21 proxy dhcpd: DHCPACK on 192.168.0.81 to 00:02:b3:29:ab:3c
> via eth0
>
> Here is the dhclient.conf of my Linux Client:
>
> timeout 60;
> retry 60;
> reboot 10;
> select-timeout 5;
> initial-interval 2;
> interface "eth0" {
> send host-name "sachse-linux.sunflowers.de";
> send dhcp-client-identifier 00:02:B3:29:AB:3C;
> send dhcp-lease-time 3600;
> supersede domain-name "sunflowers.de";
> prepend domain-name-servers 192.168.0.4;
> request subnet-mask, broadcast-address, time-offset, routers,
> domain-name, domain-name-servers, host-name;
> require subnet-mask, domain-name-servers;
> script "/sbin/dhclient-script";
> send fqdn.fqdn "sachse-linux.sunflowers.de.";
> send fqdn.encoded off;
> send fqdn.server-update off;
> }
>
>
>
> Thanks in advance
>
> Dirk


First change this line

send host-name "sachse-linux.sunflowers.de";

with this line

send host-name "sachse-linux";

If it still doesn't work, post here also the contents of files
dhcpd.conf and named.conf.

Regards,
knocte

 
Reply With Quote
 
Dirk Sachse
Guest
Posts: n/a

 
      02-18-2004, 12:44 PM
knocte wrote:

> First change this line
>
> send host-name "sachse-linux.sunflowers.de";
>
> with this line
>
> send host-name "sachse-linux";
>
> If it still doesn't work, post here also the contents of files
> dhcpd.conf and named.conf.


I changed the line, but it didnt help.

Here is the dhcpd.conf:

erver-identifier 192.168.0.4;
server-name "dns1.sunflowers.de";
ddns-update-style interim;
ddns-updates on;
update-static-leases true;
ddns-rev-domainname "in-addr.arpa.";
ddns-domainname "sunflowers.de";
option domain-name-servers 192.168.0.4, 192.168.0.6;
option domain-name "sunflowers.de";
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
authoritative;
allow unknown-clients;

zone sunflowers.de {
primary 192.168.0.4;
}
# Lan
subnet 192.168.0.0 netmask 255.255.255.0 {
ddns-domainname "sunflowers.de";
ddns-updates on;
range 192.168.0.70 192.168.0.79;
allow unknown-clients;
authoritative;
host gw-clan.sunflowers.de {
hardware ethernet 00:02:b3:2c:7c:86;
fixed-address 192.168.0.1;
}

And here is my named.conf:


key "key" {
algorithm hmac-md5;
secret
"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" ;
};

controls {
inet 127.0.0.1 allow { any; } keys { "key"; };
};


options {
pid-file "/var/run/named/named.pid";
directory "/var/named";
/*
* 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 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
forward only;
forwarders {
195.63.181.97;
192.168.0.1;
};
allow-transfer {
secondaries;
local-network;
};
notify yes;
};

zone "sunflowers.de" {
type master;
file "/var/named/master/named.sunflowers.de";
allow-update {adservers;};
};



 
Reply With Quote
 
knocte
Guest
Posts: n/a

 
      02-18-2004, 02:18 PM
Dirk Sachse escribió:
> knocte wrote:
>
>
>>First change this line
>>
>>send host-name "sachse-linux.sunflowers.de";
>>
>>with this line
>>
>>send host-name "sachse-linux";
>>
>>If it still doesn't work, post here also the contents of files
>>dhcpd.conf and named.conf.

>
>
> I changed the line, but it didnt help.
>
> Here is the dhcpd.conf:
>
> erver-identifier 192.168.0.4;
> server-name "dns1.sunflowers.de";
> ddns-update-style interim;
> ddns-updates on;
> update-static-leases true;
> ddns-rev-domainname "in-addr.arpa.";
> ddns-domainname "sunflowers.de";
> option domain-name-servers 192.168.0.4, 192.168.0.6;
> option domain-name "sunflowers.de";
> option broadcast-address 192.168.0.255;
> option routers 192.168.0.1;
> authoritative;
> allow unknown-clients;
>
> zone sunflowers.de {
> primary 192.168.0.4;
> }
> # Lan
> subnet 192.168.0.0 netmask 255.255.255.0 {
> ddns-domainname "sunflowers.de";
> ddns-updates on;
> range 192.168.0.70 192.168.0.79;
> allow unknown-clients;
> authoritative;
> host gw-clan.sunflowers.de {
> hardware ethernet 00:02:b3:2c:7c:86;
> fixed-address 192.168.0.1;
> }
>
> And here is my named.conf:
>
>
> key "key" {
> algorithm hmac-md5;
> secret
> "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" ;
> };
>
> controls {
> inet 127.0.0.1 allow { any; } keys { "key"; };
> };
>
>
> options {
> pid-file "/var/run/named/named.pid";
> directory "/var/named";
> /*
> * 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 uses an unprivileged
> * port by default.
> */
> // query-source address * port 53;
> forward only;
> forwarders {
> 195.63.181.97;
> 192.168.0.1;
> };
> allow-transfer {
> secondaries;
> local-network;
> };
> notify yes;
> };
>
> zone "sunflowers.de" {
> type master;
> file "/var/named/master/named.sunflowers.de";
> allow-update {adservers;};
> };
>


I would do this changes:

- [dhcpd.conf] Delete the line: ddns-rev-domainname "in-addr.arpa.";
- [named.conf] You have the line: allow-update {adservers;}; But you
haven't defined the ACL list "adservers", haven't you? I would change
this line to: allow-update { 192.168.0.4; 127.0.0.1; };

And make sure that all zone files (in /var/named/) have 644 permissions
and are owned by the user named and the group named.

If it still doesn't work, post the information that dhcpd gives when
offering a DHCP lease; this info is logged in /var/log/messages and can
be seen on CTRL+ALT+F12 (at least on Mandrake).

Regards,

knocte
 
Reply With Quote
 
Dirk Sachse
Guest
Posts: n/a

 
      02-19-2004, 10:04 AM
knocte wrote:

> I would do this changes:
>
> - [dhcpd.conf] Delete the line: ddns-rev-domainname "in-addr.arpa.";
> - [named.conf] You have the line: allow-update {adservers;}; But you
> haven't defined the ACL list "adservers", haven't you? I would change
> this line to: allow-update { 192.168.0.4; 127.0.0.1; };


The ACL List "adservers" exists. I havent posted the whole config file.

> And make sure that all zone files (in /var/named/) have 644 permissions
> and are owned by the user named and the group named.
> If it still doesn't work, post the information that dhcpd gives when
> offering a DHCP lease; this info is logged in /var/log/messages and can
> be seen on CTRL+ALT+F12 (at least on Mandrake).


I did everything like you said,
but nothing has changed at all.

Here is the info from /var/log/messages:

Feb 19 12:00:30 proxy named[16697]: client 192.168.0.4#42773: updating zone
'0.168.192.in-addr.arpa/IN': deleting an rrset
Feb 19 12:00:30 proxy named[16697]: client 192.168.0.4#42773: updating zone
'0.168.192.in-addr.arpa/IN': adding an RR
Feb 19 12:00:30 proxy dhcpd: delete IN PTR 81.0.168.192.in-addr.arpa. add
1800 IN PTR 81.0.168.192.in-addr.arpa. sachse-linux.sunflowers.de.:
success.
Feb 19 12:00:30 proxy dhcpd: DHCPREQUEST for 192.168.0.81 from
00:02:b3:29:ab:3c via eth0
Feb 19 12:00:30 proxy dhcpd: DHCPACK on 192.168.0.81 to 00:02:b3:29:ab:3c
via eth0

Reverse lookups work, but the forwards still dont.

Thanks for your help so far.

Dirk
 
Reply With Quote
 
Dirk Sachse
Guest
Posts: n/a

 
      02-19-2004, 01:21 PM
knocte wrote:

> I would do this changes:
>
> - [dhcpd.conf] Delete the line: ddns-rev-domainname "in-addr.arpa.";
> - [named.conf] You have the line: allow-update {adservers;}; But you
> haven't defined the ACL list "adservers", haven't you? I would change
> this line to: allow-update { 192.168.0.4; 127.0.0.1; };
>
> And make sure that all zone files (in /var/named/) have 644 permissions
> and are owned by the user named and the group named.


It finally works now.

I forgot to add a new line at the end of the config file.

Thanks anyways!

Dirk
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
DHCP not updating DNS when renewing records modo Windows Networking 1 12-20-2007 10:18 PM
How to troubleshoot DHCP updating DNS records Sandy Wood Windows Networking 0 05-18-2007 09:15 PM
Updating DNS records using dnscmd kawahee@gmail.com Windows Networking 1 11-28-2005 07:27 AM
2000 Server, CName records and XP Clients Azriphale Windows Networking 6 08-23-2005 08:34 PM
Desktops are no longer autmatically updating DNS records Fredrick A. Zilz Windows Networking 1 07-11-2005 05:19 PM



1 2 3 4 5 6 7 8 9 10 11