From non-domain joined machine perspective

[0xJs]

Not possible to request a the records from a non-domain joined machine even though the -domain -credential -domaincontroller parameters are supplied. Please close if this is expected behaviour.

Get-ADIDNSNodeAttribute -Node * -Attribute DNSRecord -DomainController $Server -Domain $Domain -Credential $Creds -Verbose
[-] Exception calling "GetCurrentDomain" with "0" argument(s): "Current security context is not associated with an Active Directory domain or forest."
Exception calling "GetCurrentDomain" with "0" argument(s): "Current security context is not associated with an Active Directory domain or forest."
At C:\Tools\AD\Powermad\Powermad.ps1:1755 char:13
+             $current_domain = [System.DirectoryServices.ActiveDirecto ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : ActiveDirectoryOperationException

[0xe7]

This is a similar issue to the one fixed in PR #12 , it does seem however that Get-ADIDNSNodeAttribute has a -Zone argument but it seems to me unneeded to GetCurrentDomain() if -Domain has been passed

[Kevin-Robertson]

I think I just went with needing to set everything manually for non-domain systems. I likely put the zone parameter there to deal with additional zones stored in AD such as reverse lookup or custom zones.

[0xe7]

Agreed, the -Zone parameter is required, what I'd probably do here is only check for $Domain, if it exists essentially run GetDomain($Domain) instead, then check for the remaining parameters, ie:

if ($PSBoundParameters['Domain'])
{
    $DomainContext = New-Object System.DirectoryServices.ActiveDirectory.DirectoryContext('Domain', $Domain)
    if ($PSBoundParameters['Credential'])
    {
        $DomainContext = New-Object System.DirectoryServices.ActiveDirectory.DirectoryContext('Domain', $Domain, $Credential.UserName, $Credential.GetNetworkCredential().Password)
    }
    try
    {
        $current_domain = [System.DirectoryServices.ActiveDirectory.Domain]::GetDomain($DomainContext)
    }
    catch
    {
        Write-Output "[-] $($_.Exception.Message)"
        throw
    }
}
else
{
    try
    {
        $current_domain = [System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain()
    }
    catch
    {
        Write-Output "[-] $($_.Exception.Message)"
        throw
    }
}

Then check $Zone and $DomainController afterwards.

I can do a PR if you want?