the solution is simple.
https://secure.bazuin.nl/scripts/
get the README-DHCP-setup.txt and the debian-dhcpd-ddns.zip
and adapt it to you ip range.
working set, based on Rowland's script and other suggestions.
or.. use it to compair it with your config.
Louis
>-----Oorspronkelijk bericht-----
>Van: ryana at reachtechfp.com
>[mailto:samba-bounces at lists.samba.org] Namens Ryan Ashley
>Verzonden: donderdag 11 september 2014 1:51
>Aan: samba at lists.samba.org
>Onderwerp: Re: [Samba] Strange DNS issue...
>
>I solved half of my problem. Disabling updates from
>isc-dhcp-server and
>rebooting removed those zones which were named after hostnames of
>workstations. I had enabled those in an attempt to get the
>reverse zones
>working. My static zones are fine (172.16.0, 172.16.1, and
>172.16.3) but
>the one DHCP serves (172.16.2) does not create any PTR records
>when the
>workstations (Windows) request and receive an IP address. Is there
>anything special I need to do here? Both the reverse zones and the
>forward zone have the same permissions according to the
>Windows DNS snap-in.
>
>On 09/10/2014 07:14 PM, Ryan Ashley wrote:
>> Anybody? This is very strange and I cannot figure out why it is
>> happening or why my reverse-DNS zones are not populating.
>>
>> On 09/09/2014 06:51 PM, Ryan Ashley wrote:
>>> Alright, things have been fine since the sharing issue, but
>I finally
>>> decided to dig into why my reverse-DNS zones are empty, save one
>>> single entry at the client location. What I found was very strange
>>> indeed. I have some type of grayed out records I cannot delete that
>>> are named after the hostnames of devices on my network.
>This one has
>>> me. Here's a screenshot linked below, and my BIND/DHCP
>configurations.
>>>
>>> http://dhta.oesm.org/dns.jpeg
>>>
>>> root at dc01:~# cat /etc/bind/named.conf
>>> # Required for SAMBA4
>>> include "/var/lib/samba/private/named.conf";
>>>
>>> # Global options
>>> options {
>>> auth-nxdomain yes;
>>> directory "/var/cache/bind";
>>>
>>> forwarders {
>>> 8.8.8.8;
>>> 8.8.4.4;
>>> };
>>>
>>> allow-transfer { none; };
>>> notify no;
>>> empty-zones-enable no;
>>>
>>> allow-query {
>>> 127.0.0.1;
>>> 172.16.0.0/22;
>>> };
>>>
>>> allow-recursion {
>>> 127.0.0.1;
>>> 172.16.0.0/22;
>>> };
>>>
>>> tkey-gssapi-keytab "/var/lib/samba/private/dns.keytab";
>>> };
>>>
>>> # Root servers (required zone for recursive queries)
>>> zone "." {
>>> type hint;
>>> file "named.root";
>>> };
>>>
>>> # Required localhost forward/reverse zones
>>> zone "localhost" {
>>> type master;
>>> file "master/localhost.zone";
>>> };
>>>
>>> zone "0.0.127.in-addr.arpa" {
>>> type master;
>>> file "master/0.0.127.zone";
>>> };
>>>
>>> root at dc01:~# cat /etc/dhcp/dhcpd.conf
>>> ddns-update-style none;
>>> option domain-name "truevine.lan";
>>> option domain-name-servers 172.16.0.1,172.16.0.2;
>>> default-lease-time 600;
>>> max-lease-time 7200;
>>> authoritative;
>>> log-facility local7;
>>>
>>> subnet 172.16.0.0 netmask 255.255.252.0 {
>>> range 172.16.2.1 172.16.2.100;
>>> option routers 172.16.0.254;
>>> option broadcast-address 172.16.3.255;
>>> ddns-updates on;
>>> ddns-update-style interim;
>>> update-static-leases on;
>>> }
>>>
>>> That's it. Have I done something that would cause such an odd thing
>>> to happen? Also, how do I remove those things?
>>
>
>--
>To unsubscribe from this list go to the following URL and read the
>instructions: https://lists.samba.org/mailman/options/samba
>
>