When I provisioned a new AD domain, I used the wrong network interface in the provisioning command. samba-tool domain provision --option="interfaces=lo eth2" --option="bind interfaces only=yes" --use-rfc2307 --use-xattrs=yes --interactive I should have used eth1 instead of eth2. The latter had no IP address attached to it so that there is no (correct) A record in the internal DNS for the DC. At any rate host -t A dc.samdom.domain.com is returning an error (Host not found: 3(NXDOMAIN)). How can I correct this *without* MS Windows RSAT? Can I just run the same command again and it will overwrite the previous config?
Hello Viktor, Am 27.12.2015 um 19:41 schrieb Viktor Trojanovic:> When I provisioned a new AD domain, I used the wrong network interface > in the provisioning command. > > samba-tool domain provision --option="interfaces=lo eth2" --option="bind > interfaces only=yes" --use-rfc2307 --use-xattrs=yes --interactive > > I should have used eth1 instead of eth2. The latter had no IP address > attached to it so that there is no (correct) A record in the internal > DNS for the DC. At any rate host -t A dc.samdom.domain.com is returning > an error (Host not found: 3(NXDOMAIN)). > > How can I correct this *without* MS Windows RSAT? Can I just run the > same command again and it will overwrite the previous config?* Remove the smb.conf. Otherwise, you have to fix the 'interfaces' option values manually. * Remove all databases (/usr/local/samba/var/ and /usr/local/samba/private/). Not all files will be overwritten, so it's better to remove all, instead to mixup something. * re-run the command. Warning: You will loose you entire domain! Everything has to be re-created (users, groups, machines need to be rejoined, etc.). Regards, Marc
On 27/12/15 18:41, Viktor Trojanovic wrote:> When I provisioned a new AD domain, I used the wrong network interface > in the provisioning command. > > samba-tool domain provision --option="interfaces=lo eth2" > --option="bind interfaces only=yes" --use-rfc2307 --use-xattrs=yes > --interactive > > I should have used eth1 instead of eth2. The latter had no IP address > attached to it so that there is no (correct) A record in the internal > DNS for the DC. At any rate host -t A dc.samdom.domain.com is > returning an error (Host not found: 3(NXDOMAIN)). > > How can I correct this *without* MS Windows RSAT? Can I just run the > same command again and it will overwrite the previous config? >Remove smb.conf and then re-provision Rowland
On 27.12.2015 20:48, Marc Muehlfeld wrote:> Hello Viktor, > > Am 27.12.2015 um 19:41 schrieb Viktor Trojanovic: >> When I provisioned a new AD domain, I used the wrong network interface >> in the provisioning command. >> >> samba-tool domain provision --option="interfaces=lo eth2" --option="bind >> interfaces only=yes" --use-rfc2307 --use-xattrs=yes --interactive >> >> I should have used eth1 instead of eth2. The latter had no IP address >> attached to it so that there is no (correct) A record in the internal >> DNS for the DC. At any rate host -t A dc.samdom.domain.com is returning >> an error (Host not found: 3(NXDOMAIN)). >> >> How can I correct this *without* MS Windows RSAT? Can I just run the >> same command again and it will overwrite the previous config? > * Remove the smb.conf. Otherwise, you have to fix the 'interfaces' > option values manually. > > * Remove all databases (/usr/local/samba/var/ and > /usr/local/samba/private/). Not all files will be overwritten, so it's > better to remove all, instead to mixup something. > > * re-run the command. > > Warning: You will loose you entire domain! Everything has to be > re-created (users, groups, machines need to be rejoined, etc.). > > > Regards, > MarcThat's what I was looking for. Thanks.