Tried to implement DDNS using SUSE 7.3 without success. Who can help?
Kevin Darcy
kcd at daimlerchrysler.com
Mon Feb 18 23:10:28 UTC 2002
Look at the logs. If a Dynamic Update is being attempted and failing,
then there should be a "denied update" log message from named and
possibly something from the DHCP server as well. If a Dynamic Update is
not even being attempted, then this is presumably a DHCP server problem.
You should probably ask a DHCP list about that.
- Kevin
P.S. Why did you create a TSIG key and then not use it?
Nicholas Reuter wrote:
> Hi everybody.
>
> I want to implement a dynamic DNS with SUSE 7.3, DHCP 3.0 and BIND
> 9.1.3-43.
>
> I have created a key for the TSIG authentication. I have made an
> ddns-update-style ad-hoc entry in dhcpd.conf as well as the
> allow-update {DHCP-server} entries in the named.conf file. But if I
> want to add a new client to the domain, it will get an IP, but the DNS
> doesn't notice it. I'm not sure where the problem is. Who can help me?
>
> Thanks in advance,
>
> Nick
>
> Here's an exerpt from dhcpd.conf and named.conf:
>
> DHCPD.CONF
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> ddns-updates on;
> ddns-hostname "ux-02";
> ddns-domainname "domain";
> option domain-name-servers 10.2.0.202;
> # dhcpd.conf
> #
> # Sample configuration file for ISC dhcpd
> #
>
> # option definitions common to all supported networks...
> option domain-name "domain";
>
> default-lease-time 3600;
> max-lease-time 7200;
> ddns-update-style ad-hoc;
>
> log-facility local7;
>
> class "foo" {
> match if substring (option vendor-class-identifier, 0, 4) =3D "SUNW";
> }
>
> shared-network domain {
> ddns-updates on;
> subnet 10.2.4.0 netmask 255.255.255.0 {
> option routers 10.2.0.202;
> option domain-name-servers 10.2.0.202;
> ddns-hostname "10.2.0.202";
> ddns-domainname "domain";
> ddns-updates on;
> range 10.2.4.100 10.2.4.150;
> option subnet-mask 255.255.224.0;
> option domain-name "domain";
> }
> subnet 10.2.0.0 netmask 255.255.0.0 {
> ddns-hostname "ux-02";
> ddns-updates on;
> ddns-domainname "domain";
> }
> }
>
> -----------------------------------------------------------------
>
> NAMED.CONF
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> ...
> # /usr/share/doc/packages/bind9/misc/options.
>
> options {
>
> # The directory statement defines the name server=B4s
> # working directory
>
> directory "/var/named";
>
> #forward first;
> # listen-on port 53 { 127.0.0.1; };
> # listen-on-v6 { any; };
> #query-source port 53;
> #transfer-source * port 53;
> #notify-source * port 53;
> #allow-query { 127.0.0.1; };
> notify no;
> # multiple-cnames no;
> # forward first;
> };
> #################Key zum rndc
> controls {
> inet 127.0.0.1 allow
> { localhost; } keys { localkey; };
> };
> key localkey {
> algorithm "hmac-md5";
> secret "n7N...=3D";
> };
> ###############End key###########################################
> # The following three zone definitions don't need any modification.
> # The first one defines localhost while the second defines the
> # reverse lookup for localhost. The last zone "." is the
> # definition of the root name servers.
>
> zone "localhost" in {
> type master;
> file "localhost.zone";
> allow-update {
> 127.0.0.1;
> 10.2.0.202;
> };
> check-names warn;
> };
>
> zone "0.0.127.in-addr.arpa" in {
> type master;
> file "127.0.0.zone";
> allow-update {
> 127.0.0.1;
> 10.2.0.202;
> };
> check-names warn;
> };
>
> zone "." in {
> type hint;
> file "root.hint";
> };
>
> # You can insert further zone records for your own domains below.
>
> zone "domain" {
> type master;
> file "/var/named/local.zone";
> allow-update {
> 127.0.0.1/32;
> 10.2.0.202/32;
> };
> };
>
> zone "2.10.in-addr.arpa" {
> type master;
> file "/var/named/local.zone.rev";
> allow-update {
> 127.0.0.1/32;
> 10.2.0.202/32;
> };
> };
>
> logging {
> category update {
> default_syslog;
> };
> category security {
> default_syslog;
> };
> category config {
> default_syslog;
> };
> };
More information about the bind-users
mailing list