[Samba] Strange DNS issue...

Ryan Ashley ryana at reachtechfp.com
Thu Sep 18 09:02:02 MDT 2014


Alright, I can try that. Should I remove the existing zones with the DNS 
snap-in? Also, the Samba guides recommend using the snap-ins in most 
cases. In fact, in every case I can recall. Is this an exception?

On 09/18/2014 01:50 AM, Daniel Müller wrote:
> Just do it with the samba-tool. I think this should be the right way. For me
> some features of the snap-in where not working at all.
> So relay on samba-tool.
>
> Greetings
> Daniel
>
>
> EDV Daniel Müller
>
> Leitung EDV
> Tropenklinik Paul-Lechler-Krankenhaus
> Paul-Lechler-Str. 24
> 72076 Tübingen
> Tel.: 07071/206-463, Fax: 07071/206-499
> eMail: mueller at tropenklinik.de
> Internet: www.tropenklinik.de
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] Im
> Auftrag von Ryan Ashley
> Gesendet: Mittwoch, 17. September 2014 17:08
> An: samba at lists.samba.org
> Betreff: Re: [Samba] Strange DNS issue...
>
> I created the zones in the Microsoft DNS snap-in. Could this be the issue?
>
> On 09/16/2014 02:39 AM, Daniel Müller wrote:
>> "if I
>>> take a freshly installed Windows 7 box and join it to Samba 4
>>> domains, I get no reverse-DNS."
>> Did you ,at first create the reverse zone, ex.: samba-tool dns
>> zonecreate yoursambadc  your.reverse.zone.in-addr.arpa, samba-tool dns
>> zonecreate s4master 135.168.192.in-addr.arpa.
>> If you do this in the first run, and of course your dns is working,
>> all your clients that join the domain will be registered in the reverse
> zone also.
>> Greetings
>> Daniel
>>
>>
>> EDV Daniel Müller
>>
>> Leitung EDV
>> Tropenklinik Paul-Lechler-Krankenhaus
>> Paul-Lechler-Str. 24
>> 72076 Tübingen
>> Tel.: 07071/206-463, Fax: 07071/206-499
>> eMail: mueller at tropenklinik.de
>> Internet: www.tropenklinik.de
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: samba-bounces at lists.samba.org
>> [mailto:samba-bounces at lists.samba.org] Im Auftrag von Ryan Ashley
>> Gesendet: Montag, 15. September 2014 23:16
>> An: samba at lists.samba.org
>> Betreff: Re: [Samba] Strange DNS issue...
>>
>> I just wanted to update everybody here. We are building a small domain
>> (Server 2008 R2 server and Windows 7 client) inside VirtualBox to test
> this.
>> If it works with the same settings, I will assume it is a bug.
>> Either way I will post my results here.
>>
>> On 09/12/2014 11:02 AM, Ryan Ashley wrote:
>>> Sorry for the delayed response. We were off yesterday.
>>>
>>> Rowland, this same setup works with reverse-zones on a 2008 R2 domain.
>>> I mean, on a 2008 R2 domain hosted by 2008 R2. We have nothing
>>> special on the Samba 4 domain I am aware of. The client
>>> configurations on both domains are set to DHCP for all workstations.
>>> In other words, if I take a freshly installed Windows 7 box and join
>>> it to Samba 4 domains, I get no reverse-DNS. If I join the same box
>>> to the Windows-hosted domain, I do. Not saying this is not a Windows
>>> issue as it may well be but I was making note of that test, which I
>>> did attempt prior to posting here.
>>>
>>> Here is a dump from syslog with dhcpd filtered.
>>>
>>> Actually, that has a lot of MAC addresses in it. Suffice to say I see
>>> DHCPREQUEST, DHCPACK, DHCPINFORM, DHCPACK, DHCPINFORM, and DHCPACK
>>> again for loads of MACs/addresses. No errors. If you still want to
>>> see it, may I send it to you off-list to protect the MACs?
>>>
>>> Here is the dump from my dhcpd.leases file.
>>>
>>> lease 172.16.2.12 {
>>>     starts 5 2014/09/12 14:44:22;
>>>     ends 5 2014/09/12 14:54:22;
>>>     cltt 5 2014/09/12 14:44:22;
>>>     binding state active;
>>>     next binding state free;
>>>     rewind binding state free;
>>>     hardware ethernet ;
>>>     uid "\001\340i\225\303\260\332";
>>>     client-hostname "youthpastor01";
>>> }
>>> lease 172.16.2.9 {
>>>     starts 5 2014/09/12 14:47:26;
>>>     ends 5 2014/09/12 14:57:26;
>>>     cltt 5 2014/09/12 14:47:26;
>>>     binding state active;
>>>     next binding state free;
>>>     rewind binding state free;
>>>     hardware ethernet ;
>>>     uid "\0018`w\033:\200";
>>>     client-hostname "jcenter";
>>> }
>>> lease 172.16.2.13 {
>>>     starts 5 2014/09/12 14:47:54;
>>>     ends 5 2014/09/12 14:57:54;
>>>     cltt 5 2014/09/12 14:47:54;
>>>     binding state active;
>>>     next binding state free;
>>>     rewind binding state free;
>>>     hardware ethernet ;
>>>     uid "\0018`w\265w<";
>>>     client-hostname "av01";
>>> }
>>> lease 172.16.2.47 {
>>>     starts 5 2014/09/12 14:48:53;
>>>     ends 5 2014/09/12 14:58:53;
>>>     cltt 5 2014/09/12 14:48:53;
>>>     binding state active;
>>>     next binding state free;
>>>     rewind binding state free;
>>>     hardware ethernet ;
>>>     uid "\001\004}{\027\362\237";
>>>     client-hostname "budget";
>>> }
>>> lease 172.16.2.11 {
>>>     starts 5 2014/09/12 14:48:54;
>>>     ends 5 2014/09/12 14:58:54;
>>>     cltt 5 2014/09/12 14:48:54;
>>>     binding state active;
>>>     next binding state free;
>>>     rewind binding state free;
>>>     hardware ethernet ;
>>>     uid "\0018`w\033\206\367";
>>>     client-hostname "admin01";
>>> }
>>> lease 172.16.2.12 {
>>>     starts 5 2014/09/12 14:49:22;
>>>     ends 5 2014/09/12 14:59:22;
>>>     cltt 5 2014/09/12 14:49:22;
>>>     binding state active;
>>>     next binding state free;
>>>     rewind binding state free;
>>>     hardware ethernet ;
>>>     uid "\001\340i\225\303\260\332";
>>>     client-hostname "youthpastor01";
>>> }
>>> lease 172.16.2.9 {
>>>     starts 5 2014/09/12 14:52:26;
>>>     ends 5 2014/09/12 15:02:26;
>>>     cltt 5 2014/09/12 14:52:26;
>>>     binding state active;
>>>     next binding state free;
>>>     rewind binding state free;
>>>     hardware ethernet ;
>>>     uid "\0018`w\033:\200";
>>>     client-hostname "jcenter";
>>> }
>>> lease 172.16.2.13 {
>>>     starts 5 2014/09/12 14:52:54;
>>>     ends 5 2014/09/12 15:02:54;
>>>     cltt 5 2014/09/12 14:52:54;
>>>     binding state active;
>>>     next binding state free;
>>>     rewind binding state free;
>>>     hardware ethernet ;
>>>     uid "\0018`w\265w<";
>>>     client-hostname "av01";
>>> }
>>>
>>> I edited the MACs out here, and there were more, but I lost some of
>>> my scrollback buffer.
>>>
>>> On 09/11/2014 09:02 AM, L.P.H. van Belle wrote:
>>>> and as tip why you revers is not working.
>>>>
>>>> check the info in /var/lib/dhcpd/
>>>> and look what you clients where getting..
>>>> this is how i solved my rev problem ;-)
>>>>
>>>>
>>>>> -----Oorspronkelijk bericht-----
>>>>> Van: ryana at reachtechfp.com
>>>>> [mailto:samba-bounces at lists.samba.org] Namens Ryan Ashley
>>>>> Verzonden: donderdag 11 september 2014 1:14
>>>>> Aan: samba at lists.samba.org
>>>>> Onderwerp: Re: [Samba] Strange DNS issue...
>>>>>
>>>>> 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
>>>>>
>>>>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>



More information about the samba mailing list