If I look for a non existent name on the internet I see that the name does no exist which is just fine
PS C:\> Resolve-DnsName -Name abc.abc.co.uk -Type A -DnssecOk -DnsOnly -NoHostsFile Resolve-DnsName: abc.abc.co.uk : DNS name does not exist. PS C:\> Resolve-DnsName -Name abc.abc.co.uk -Type AAAA -DnssecOk -DnsOnly -NoHostsFile Resolve-DnsName: abc.abc.co.uk : DNS name does not exist. PS C:\ Resolve-DnsName -Name abc.abc.com -Type A -DnssecOk -DnsOnly -NoHostsFile Resolve-DnsName: abc.abc.com : DNS name does not exist. PS C:\ Resolve-DnsName -Name abc.abc.com -Type AAAA -DnssecOk -DnsOnly -NoHostsFile Resolve-DnsName: abc.abc.com : DNS name does not exist. If I do the same thing on my local network I see the "Not enough memory..." error PS C:\ Resolve-DnsName -Name abc.abc.home -Type A -DnssecOk -DnsOnly -NoHostsFile Resolve-DnsName: abc.abc.home : Not enough memory resources are available to complete this operation. PS C:\ Resolve-DnsName -Name abc.abc.home -Type AAAA -DnssecOk -DnsOnly -NoHostsFile Resolve-DnsName: abc.abc.home : Not enough memory resources are available to complete this operation. The IPV4 name that resolves is configured as part of the local network when unbound starts PS C:\ Resolve-DnsName -Name test.home -Type A -DnssecOk -DnsOnly -NoHostsFile Name Type TTL Section IPAddress ---- ---- --- ------- --------- test.home A 3600 Answer 192.168.1.63 No IPV6 is configured on the local network PS C:\ Resolve-DnsName -Name test.home -Type AAAA -DnssecOk -DnsOnly -NoHostsFile Resolve-DnsName: test.home : Not enough memory resources are available to complete this operation. If I remove the -DnsSecOK switch then I get the result I would expect. PS C:\ Resolve-DnsName -Name abc.abc.home -Type A -DnsOnly -NoHostsFile Resolve-DnsName: abc.abc.home : DNS name does not exist. PS C:\ Resolve-DnsName -Name abc.abc.home -Type AAAA -DnsOnly -NoHostsFile Resolve-DnsName: abc.abc.home : DNS name does not exist. So is this a PowerShell issue or is it something that Unbound is doing/returning to PowerShell? RayG
