View previous topic :: View next topic |
Author |
Message |
Michoun n00b
Joined: 30 Jan 2003 Posts: 34 Location: France
|
Posted: Fri Mar 14, 2003 2:36 pm Post subject: named & dhcpd dynamic config |
|
|
I'm trying to set up named and dhcpd to allow dhcpd to dynamically update named's zones using an MD5 key.
first, here is my conf :
1 - dhcpd.conf
Code: | # required for dynamic update
ddns-update-style interim;
key "gloomy-wks_key" {
algorithm hmac-md5;
secret "######################";
};
# defining local network
subnet 192.168.10.0 netmask 255.255.255.0 {
# allowing just 1 non local machine.
range 192.168.10.2 192.168.10.5;
# Domain name
option domain-name "gloomy-wks.homelinux.org";
# DNS for my LAN
option domain-name-servers 192.168.10.1;
option routers 192.168.10.1;
option broadcast-address 192.168.10.255;
option subnet-mask 255.255.255.0;
# 24H by default
default-lease-time 86400;
# 48H Max
max-lease-time 172800;
}
zone gloomy-wks.homelinux.org. {
key gloomy-wks_key;
}
zone 10.168.192.in-addr.arpa. {
key gloomy-wks_key;
}
|
2 - named.conf
Code: |
key "gloomy-wks_key" {
algorithm hmac-md5;
secret "######################";
};
options {
directory "/var/bind";
// Turns on DNS forwarding,
forward first;
forwarders {
212.30.96.108;
212.30.96.123;
};
listen-on-v6 { none; };
listen-on {
192.168.10.1;
127.0.0.1;
};
// if you have problems and are behind a firewall:
//query-source address * port 53;
pid-file "/var/run/named/named.pid";
};
zone "gloomy-wks.homelinux.org." IN {
type master;
file "pri/gloomy-wks.homelinux.org";
allow-update { key "gloomy-wks_key"; };
notify no;
};
zone "10.168.192.in-addr.arpa." IN {
type master;
file "pri/10.168.192";
allow-update { key "gloomy-wks_key"; };
notify no;
};
|
3 - gloomy-wks.homelinux.org zone
Code: |
$TTL 1W
@ IN SOA Asthurion.gloomy-wks.homelinux.org. root.localhost. (
2002081601 ; Serial
28800 ; Refresh
14400 ; Retry
604800 ; Expire - 1 week
86400 ) ; Minimum
IN NS Asthurion.gloomy-wks.homelinux.org.
Asthurion IN A 192.168.10.1
Medusa IN A 192.168.10.5
Belzebuth IN A 192.168.10.4
Balsagoth IN A 192.168.10.3
|
4 - 10.168.192 zone
Code: |
$ORIGIN 10.168.192.in-addr.arpa.
$TTL 1W
@ 1D IN SOA Asthurion.gloomy-wks.homelinux.org. root.localhost. (
2002081601 ; serial
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum
IN NS Asthurion.gloomy-wks.homelinux.org.
0 IN A 255.255.255.0
1 IN PTR Asthurion.gloomy-wks.homelinux.org.
5 IN PTR Medusa.gloomy-wks.homelinux.org.
4 IN PTR Belzebuth.gloomy-wks.homelinux.org.
3 IN PTR Balsagoth.gloomy-wks.homelinux.org.
|
The problem is that zone are never updated.
here is a piece of log i have once a computer on my lan request an IP :
Code: |
Mar 14 14:18:28 [dhcpd] DHCPREQUEST for 192.168.10.5 from 00:04:75:81:b5:12 (medusa) via eth0
Mar 14 14:18:28 [dhcpd] DHCPACK on 192.168.10.5 to 00:04:75:81:b5:12 (medusa) via eth0
Mar 14 14:18:29 [named] client 192.168.10.1#32772: updating zone 'gloomy-wks.homelinux.org/IN': update failed: 'name not in use' prerequisite not satisfied (YXDOMAIN)
Mar 14 14:18:29 [dhcpd] if IN A medusa.gloomy-wks.homelinux.org domain doesn't exist add 43200 IN A medusa.gloomy-wks.homelinux.org 192.168.10.5 add 43200 IN TXT medusa.gloomy-wks.homelinux.org "318256c4cf39af9674ab1650f90acfc184": domain already exists.
Mar 14 14:18:29 [named] client 192.168.10.1#32772: updating zone 'gloomy-wks.homelinux.org/IN': update failed: 'RRset exists (value dependent)' prerequisite not satisfied (NXRRSET)Mar 14 14:18:29 [dhcpd] if IN TXT medusa.gloomy-wks.homelinux.org "318256c4cf39af9674ab1650f90acfc184" rrset exists delete IN A medusa.gloomy-wks.homelinux.org add 43200 IN A medusa.gloomy-wks.homelinux.org 192.168.10.5: no such RRset.
|
Does anybody could help to fix this ?
thanks _________________ ICQ/AIM Java library - http://sourceforge.net/projects/ooimlib/ |
|
Back to top |
|
|
Michoun n00b
Joined: 30 Jan 2003 Posts: 34 Location: France
|
Posted: Sat Mar 15, 2003 2:04 pm Post subject: |
|
|
Guys, i really hate to do so , but i really need your help on this problem...
I'm sure some of you could fix it really quickly...
so please .... HELP _________________ ICQ/AIM Java library - http://sourceforge.net/projects/ooimlib/ |
|
Back to top |
|
|
nx12 Apprentice
Joined: 14 Jan 2004 Posts: 193
|
Posted: Fri Jul 30, 2004 11:32 pm Post subject: |
|
|
I have exactly the same problem. Anyone knows a solution? _________________ signature sucks |
|
Back to top |
|
|
neomatrix35 n00b
Joined: 05 Jul 2004 Posts: 53
|
Posted: Sat Jul 31, 2004 12:40 am Post subject: |
|
|
first off .. make sure your names are the same... it might just be finicky on capitalization... i notice its lookins for medusa.**** but in your zone info its Medusa.****
next if you have made changes since your restart of your bind server ... you must increment your serial #... then retsart the bind server again.
might be the reason why the name isnt in use.
i'm no expert but these are just things you might want to try. |
|
Back to top |
|
|
nx12 Apprentice
Joined: 14 Jan 2004 Posts: 193
|
Posted: Sat Jul 31, 2004 4:41 am Post subject: |
|
|
Ok. I've found the solution, though I don't know if it's correct , but I'm a bit tired of all those RFC papers...
I simply removed all the names with dynamic IPs from the corresponding zone files. They apper only in dhcpd.conf now. _________________ signature sucks |
|
Back to top |
|
|
|