samba - Nov 2013 - vestigial DNS entries

I am running samba 4.2.0 as an AD with internal DNS.

I had an earlier version of Samba4 that was running old code and the system
had gotten cluttered up from my learning process.  I chose to replace it by
bringing up a new Samba4 DC, letting them sync, then promote the new, and
demote the old.  That all worked flawlessly.  Eventually I destroyed the
old Samba4 system.

Today I tried to play around with SWAT and I see my samba log is full of
failed attempts to connect to 192.168.0.13 -- that was my old Samba4 AD,
now destroyed.  The only place I can find any reference to that IP address
is when I do "samba-tool dns query ... @", it shows:

  Name=, Records=2, Children=0
    A: 192.168.0.13 (flags=600000f0, serial=1, ttl=900)
    A: 192.168.0.5 (flags=600000f0, serial=110, ttl=900)

That is, a null name, and the IP addresses of my old/defunct AD (.13) and
my current/operational AD (.5).

How can I get rid of the 0.13 record?  Are both of these records incorrect?

Thanks.

Lee

On Tue, Nov 26, 2013 at 03:34:22PM -0500, Lee Allen
wrote:
> I am running samba 4.2.0 as an AD with internal DNS.
 
> Today I tried to play around with SWAT and I see my samba log is full of
> failed attempts to connect to 192.168.0.13 -- that was my old Samba4 AD,
> now destroyed.  The only place I can find any reference to that IP address
> is when I do "samba-tool dns query ... @", it shows:
> 
>   Name=, Records=2, Children=0
>     A: 192.168.0.13 (flags=600000f0, serial=1, ttl=900)
>     A: 192.168.0.5 (flags=600000f0, serial=110, ttl=900)
> 
> That is, a null name, and the IP addresses of my old/defunct AD (.13) and
> my current/operational AD (.5).
> 
> How can I get rid of the 0.13 record?  
This should do it:
    samba-tool dns delete 192.168.0.5 $zone @ A 192.168.0.13
(where $zone stands for whatever zone name you are using in your query).

(I did a quick test that samba-tool won't delete the other A record for 
Name= and won't delete other A records with the same IP address but
other names under that zone, and samba-tool did what I meant.)

Or you could use something like Microsoft Management Console to manage
Samba DNS if you are more comfortable with MMC.
> Are both of these records incorrect?
I don't think they are necessary, unless someone or something uses
that zone name as if it was a host name (for example http://$zone
or ping $zone or \\$zone\$share or password server=$zone).  But the
fact that your samba logs have lots of failed attempts to connect 
to 192.168.0.13 suggests that perhaps something in your samba *is*
referring to $zone (or 192.168.0.13 directly) like a host name.

-- 
___________________________________________________________________________
  David Keegel <djk-samba at cyber.com.au>      Cyber IT Solutions Pty.
Ltd.
   http://www.cyber.com.au/~djk/     Linux & Unix Systems Administration