search for: 6900600

...taset 'local.domain # 0113600 # # 011SOA 011IN # 011samba.local.domain. hostmaster.local.domain. 5900600 86400 3600 ' Jun 28 17:28:40 samba named [8988]: samba_dlz: added rdataset local.domain 'local.domain # 0113600 # # 011SOA 011IN # 011samba.local.domain.. hostmaster.local.domain. 6900600 86400 3600 ' Jun 28 17:28:40 samba named [8988]: samba_dlz: committed transaction on zone local.domain Any idea ? Thank you

...ain # 0113600 # # 011SOA 011IN # > 011samba.local.domain. hostmaster.local.domain. 5900600 86400 3600 ' > Jun 28 17:28:40 samba named [8988]: samba_dlz: added rdataset > local.domain 'local.domain # 0113600 # # 011SOA 011IN # > 011samba.local.domain.. hostmaster.local.domain. 6900600 86400 3600 ' > Jun 28 17:28:40 samba named [8988]: samba_dlz: committed transaction > on zone local.domain > > This is not your windows server dns being updated, it appears to be > your windows server record being updated on a Samba AD DC running Bind9. > > So, I ask agai...

...# 011SOA 011IN # >> 011samba.local.domain. hostmaster.local.domain. 5900600 86400 3600 ' >> Jun 28 17:28:40 samba named [8988]: samba_dlz: added rdataset >> local.domain 'local.domain # 0113600 # # 011SOA 011IN # >> 011samba.local.domain.. hostmaster.local.domain. 6900600 86400 3600 ' >> Jun 28 17:28:40 samba named [8988]: samba_dlz: committed transaction >> on zone local.domain >> > > This log fragment is only showing the DC updating its own record on a > Samba DC, you will need to look in the logs on the windows DC. > > I tak...

I'm running DNS on Windows too, as it receives the update, and delete it it it also erases the Samba, Windows so I could see are not leaving this I create new entries. Entries in samba via command or RSAT are working. Thanks Em 29-06-2016 12:33, Rowland penny escreveu: > On 29/06/16 14:48, Carlos A. P. Cunha wrote: >> Hello! >> >> >> What DNS server is running

...>>> 011samba.local.domain. hostmaster.local.domain. 5900600 86400 3600 ' >>> Jun 28 17:28:40 samba named [8988]: samba_dlz: added rdataset >>> local.domain 'local.domain # 0113600 # # 011SOA 011IN # >>> 011samba.local.domain.. hostmaster.local.domain. 6900600 86400 3600 ' >>> Jun 28 17:28:40 samba named [8988]: samba_dlz: committed transaction >>> on zone local.domain >>> >>> This is not your windows server dns being updated, it appears to be >>> your windows server record being updated on a Samba AD DC...

...taset 'local.domain # 0113600 # # 011SOA 011IN # 011samba.local.domain. hostmaster.local.domain. 5900600 86400 3600 ' Jun 28 17:28:40 samba named [8988]: samba_dlz: added rdataset local.domain 'local.domain # 0113600 # # 011SOA 011IN # 011samba.local.domain.. hostmaster.local.domain. 6900600 86400 3600 ' Jun 28 17:28:40 samba named [8988]: samba_dlz: committed transaction on zone local.domain This is not your windows server dns being updated, it appears to be your windows server record being updated on a Samba AD DC running Bind9. So, I ask again, WHAT DNS SERVER IS RUNNING ON...

...ain # 0113600 # # 011SOA 011IN # > 011samba.local.domain. hostmaster.local.domain. 5900600 86400 3600 ' > Jun 28 17:28:40 samba named [8988]: samba_dlz: added rdataset > local.domain 'local.domain # 0113600 # # 011SOA 011IN # > 011samba.local.domain.. hostmaster.local.domain. 6900600 86400 3600 ' > Jun 28 17:28:40 samba named [8988]: samba_dlz: committed transaction > on zone local.domain > This log fragment is only showing the DC updating its own record on a Samba DC, you will need to look in the logs on the windows DC. I take it that the windows DC is running...

...# 011SOA 011IN # >> 011samba.local.domain. hostmaster.local.domain. 5900600 86400 3600 ' >> Jun 28 17:28:40 samba named [8988]: samba_dlz: added rdataset >> local.domain 'local.domain # 0113600 # # 011SOA 011IN # >> 011samba.local.domain.. hostmaster.local.domain. 6900600 86400 3600 ' >> Jun 28 17:28:40 samba named [8988]: samba_dlz: committed transaction >> on zone local.domain >> >> This is not your windows server dns being updated, it appears to be >> your windows server record being updated on a Samba AD DC running Bind9. >...

...>>> 011samba.local.domain. hostmaster.local.domain. 5900600 86400 3600 ' >>> Jun 28 17:28:40 samba named [8988]: samba_dlz: added rdataset >>> local.domain 'local.domain # 0113600 # # 011SOA 011IN # >>> 011samba.local.domain.. hostmaster.local.domain. 6900600 86400 3600 ' >>> Jun 28 17:28:40 samba named [8988]: samba_dlz: committed transaction >>> on zone local.domain >>> >> >> This log fragment is only showing the DC updating its own record on a >> Samba DC, you will need to look in the logs on the win...

...al.domain. >>>> hostmaster.local.domain. 5900600 86400 3600 ' >>>> Jun 28 17:28:40 samba named [8988]: samba_dlz: added rdataset >>>> local.domain 'local.domain # 0113600 # # 011SOA 011IN # >>>> 011samba.local.domain.. hostmaster.local.domain. 6900600 86400 3600 ' >>>> Jun 28 17:28:40 samba named [8988]: samba_dlz: committed transaction on >>>> zone local.domain >>>> >>>> This is not your windows server dns being updated, it appears to be >>>> your windows server record being update...

...t; 011samba.local.domain. hostmaster.local.domain. 5900600 86400 3600 ' >>>> Jun 28 17:28:40 samba named [8988]: samba_dlz: added rdataset >>>> local.domain 'local.domain # 0113600 # # 011SOA 011IN # >>>> 011samba.local.domain.. hostmaster.local.domain. 6900600 86400 3600 ' >>>> Jun 28 17:28:40 samba named [8988]: samba_dlz: committed >>>> transaction on zone local.domain >>>> >>> >>> This log fragment is only showing the DC updating its own record on >>> a Samba DC, you will need to loo...