Hello list..:-) i have a little problem and don´t find a solution for it. Some time ago our first DC died and I replaced it with a new one with a different name but the same IP.didn´t want to change the DNS entry in all the clients. Guess since than the dynamic DNS update wasn´t working anymore, so I tried to find out the reason. What I found is that the SOA record was pointing still to the none existing DC. After searching a little bit I was able to change the SOA record for our Forward-lookupzone and the first workstations have been registered in the DNS...till today not enough. But I was only able to change the SOA record for our first "samdom.example.com" zone. For the "_msdcs.samdom.example.com" zone it´s not possible. I use exactely the same syntax...no success. With dig -t SOA _msdcs.samdom.example.com I get every information about. When I try to change it I get only a message "ERROR: Record does not exist" At the moment we´re on 4.4.6, but also in a testsystem with 4.5.1 I get the same result. Has anybody an idea how to fix it ? Thanks Frank
On Thu, 10 Nov 2016 13:21:52 +0100 "Rauer, Frank via samba" <samba at lists.samba.org> wrote:> > Hello list..:-) > > i have a little problem and don´t find a solution for it. > Some time ago our first DC died and I replaced it with a new one with > a different name but the same IP.didn´t want to change the DNS entry > in all the clients. > Guess since than the dynamic DNS update wasn´t working anymore, so I > tried to find out the reason. > > What I found is that the SOA record was pointing still to the none > existing DC. After searching a little bit I was able to change the > SOA record for our Forward-lookupzone and the first workstations have > been registered in the DNS...till today not enough. > > But I was only able to change the SOA record for our first > "samdom.example.com" zone. For the "_msdcs.samdom.example.com" zone > it´s not possible. I use exactely the same syntax...no success. > > With dig -t SOA _msdcs.samdom.example.com I get every information > about. When I try to change it I get only a message "ERROR: Record > does not exist" > > At the moment we´re on 4.4.6, but also in a testsystem with 4.5.1 I > get the same result. > > Has anybody an idea how to fix it ? > > Thanks > > Frank > >How are you trying to add the SOA record ? The command should be something like this: samba-tool dns add 127.0.0.1 _msdcs.samdom.example.com @ NS dc.samdom.example.com You could be missing some records, see here: https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record Rowland
Hi Rowland, I followed this page "https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record" more than once. Everything in here is fine...every test successful. My problem is that the existing SAO record is pointing to dc1.samdom.example.com which doesn´t exist anymore. Now it must be dc01.samdom.example.com. What happens when I try to add ... samba-tool dns add 127.0.0.1 _msdcs.samdom.example.com @ NS dc01.samdom.example.com ... ? will it break something because we still have an entry..even it´s a wrong one ? Frank Am 10.11.2016 um 13:55 schrieb Rowland Penny via samba:> On Thu, 10 Nov 2016 13:21:52 +0100 > "Rauer, Frank via samba" <samba at lists.samba.org> wrote: > >> >> Hello list..:-) >> >> i have a little problem and don´t find a solution for it. >> Some time ago our first DC died and I replaced it with a new one with >> a different name but the same IP.didn´t want to change the DNS entry >> in all the clients. >> Guess since than the dynamic DNS update wasn´t working anymore, so I >> tried to find out the reason. >> >> What I found is that the SOA record was pointing still to the none >> existing DC. After searching a little bit I was able to change the >> SOA record for our Forward-lookupzone and the first workstations have >> been registered in the DNS...till today not enough. >> >> But I was only able to change the SOA record for our first >> "samdom.example.com" zone. For the "_msdcs.samdom.example.com" zone >> it´s not possible. I use exactely the same syntax...no success. >> >> With dig -t SOA _msdcs.samdom.example.com I get every information >> about. When I try to change it I get only a message "ERROR: Record >> does not exist" >> >> At the moment we´re on 4.4.6, but also in a testsystem with 4.5.1 I >> get the same result. >> >> Has anybody an idea how to fix it ? >> >> Thanks >> >> Frank >> >> > > How are you trying to add the SOA record ? > The command should be something like this: > > samba-tool dns add 127.0.0.1 _msdcs.samdom.example.com @ NS > dc.samdom.example.com > > You could be missing some records, see here: > > https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record > > Rowland >