{"changed": true, "msg": "failed to join domain: Computer 'castelblack' failed to join domain 'north.sevenkingdoms.local'

[Argonx21]

I am facing the below issue during the installation process. Can anyone suggest a possible fix for this issue?

fatal: [srv02]: FAILED! => {"changed": true, "msg": "failed to join domain: Computer 'castelblack' failed to join domain 'north.sevenkingdoms.local' from its current workgroup 'WORKGROUP' with following error message: The specified domain either does not exist or could not be contacted.", "reboot_required": false}

[mueller]

I got the same problem. At first I tried adding north.sevenkingdoms.local manually to the hosts file and re-running the goad.sh script (as suggested in https://github.com/Orange-Cyberdefense/GOAD/issues/97#issuecomment-1693988273).

However, that didn't work and it seems like the root cause is that the north domain is not created:

[CalfCrusher]

Same problem here

[shoxxdj]

Same here :/

[Thangart]

Check. i got the same problem. looks like DC02 lost all its connection with the parent DC and demotes. I'll have a look at it once i have some more spare time

[Thangart]

Hmm it looks like the NAT interface is interfering with setting up the north domain. Curiously by looking at the ansible config to set up the child domain in the file: "ansible/roles/child_domain/tasks/main.yml" we cna see that there are some commented out blocks at line 27 and 87 that refer to disabling the NAT interface and enabling it later in the playbook.

Reenabling this code by removing the # and 1 space, and running the install gives me a working "north." subdomain and continues the installation as it should.

Just for quick reference. Which provider are you using and which version of it? For me it was Virtualbox version 7.1.2

[shoxxdj]

Finally works like a charm with @Thangart tips.

I'm using virtualbox 7.1.4-1

[mueller]

Reenabling this code by removing the # and 1 space, and running the install gives me a working "north." subdomain and continues the installation as it should.

Worked for me as well, thank you very much! :slightly_smiling_face:

[Mayfly277]

subdomain dns issues should have been fixed now in v3, so i close.