Tranquil IT Forum

Good morning,

We are currently testing WAPT enterprise, and I am currently working on OS deployment (Win11 and Ubuntu 24.04).
The WAPT Server version is: 2.6.0.17293.

I am encountering a problem when trying to deploy Windows 11 on a test machine.
In the WinPE section, on the 3rd command prompt I get a DNS resolution error:

DNS resolution has failed for: wapt.polytech.sorbonne-universite.fr

I have no problem pinging the machine in question; DNS resolution seems to be working fine.

Note that I had no problems until now, but I am working on setting up a Samba AD* domain and automatically integrating the machine into the domain, which led me to change the DNS of my test machine to point to the DNS integrated into the DC.

When I point my test machine to the default DNS (that of the University I depend on), I do not encounter the problem, but as a result this does not allow me to integrate the machine into our local AD.

I don't see what the problem could be, as the ping is working fine, thank you for your help.





*: [HS] (and we would be interested in support/assistance from Tranqui'IT on SambaAD, by the way) [/HS]

Good evening Julien,

there was indeed a bug in the mORMot DNS cache management section which was recently fixed internally. We'll look into backporting the fix to version 2.6 so it's included in the next release.

Regards,

Denis

Hello,

Yes, thank you for your feedback.

I confirm that the issue only occurs when I point my client machine to the DNS server of my Samba DC (whether using the internal DNS or bind9), not when using the usual DNS, at the time of execution of wgetwads64.exe.

Regards

Hello,

I updated WAPT Enterprise to the latest version, as well as my administration console.

WAPT Server version: 2.6.0.17392
WAPT Agent version: 2.6.0.17392
WAPT Setup version: 2.6.0.17392
WAPT Deploy version: 2.6.0.17392
DB status: OK

I saw the fix (DNS cache) in the changelog; however, the problem persists when I try to deploy a Windows machine.

Regards

After reviewing the code:

https://github.com/synopse/mORMot2/blob ... s.pas#L827

, it seems the function only tests A records. Is it a CNAME or an A record on your end?

Simon

Hello,

it was a CNAME record (wapt -> pc5079 -> IP), I just changed it to only an A record (wapt -> IP).

I tried clearing the bind DNS cache, but the problem persists.

Hello

, I'd like to reproduce the problem here.

Is the machine's DNS server directly your Samba server?

If so, what version is it?

Hello again,

a few more questions: if using Samba, internal DNS or bind-dlz.
If bind-dlz, with or without the minimal-responses option?

Regards,

Denis

sfonteneau wrote: ↑August 6, 2025 - 3:09 PM Hello

, I'd like to be able to reproduce the problem here.

Is the machine's DNS server directly your Samba server?

If so, what version is it?

Good morning,

Yes, the machine I am deploying specifically points to the DNS of the Samba domain controller.

I specify it at the machine's dhcp configuration level, so that I can perform tests on it without touching the global dhcp setting (so that other machines continue to use the global dns provided by our university).

The version is BIND 9.18.33-1~deb12u2-Debian.

Hello

, but I didn't understand.

In which cases does it not work (internal bind9 or forward)?

And in which cases does it work?