Yes, it seems like.
http://technet.microsoft.com/en-us/library/cc961817.aspx suggests:
"To investigate further, run nltest /dsgetdc:<domain-name> and examine the output. If you still receive errors, either the domain really does not exist or there is a transient net error that is preventing domain controller discovery. By running Netdiag.exe and examining the output, you usually can determine the cause. A "Failure to connect to a domain controller" message usually means that transient net errors or insufficient credentials are the cause."
Could you try to put something like that into pre-customization script? Also any other troubleshooting things like ping or even "netdom join" just to see if that works.
prost-customization script is executed after network is fully reconfigured, so that's why "netdom join" in there has higher chances to succeed.
/Andrii