Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems installing xDnsServer module: No match was found for the specified search criteria and module name 'xDnsServer' #260

Open
gusechuisheng opened this issue Aug 7, 2024 · 2 comments

Comments

@gusechuisheng
Copy link

TASK [domain_controller : Check for xDnsServer Powershell module] **************
fatal: [dc03]: FAILED! => {"changed": false, "msg": "Problems installing xDnsServer module: No match was found for the specified search criteria and module name 'xDnsServer'. Try Get-PSRepository to see all available registered module repositories.", "nuget_changed": false, "output": "", "repository_changed": false}
fatal: [dc01]: FAILED! => {"changed": false, "msg": "Problems installing xDnsServer module: No match was found for the specified search criteria and module name 'xDnsServer'. Try Get-PSRepository to see all available registered module repositories.", "nuget_changed": false, "output": "", "repository_changed": false}

PLAY RECAP *********************************************************************
dc01 : ok=24 changed=5 unreachable=0 failed=1 skipped=6 rescued=0 ignored=0
dc02 : ok=19 changed=4 unreachable=0 failed=0 skipped=4 rescued=0 ignored=0
dc03 : ok=24 changed=5 unreachable=0 failed=1 skipped=6 rescued=0 ignored=0
srv02 : ok=18 changed=3 unreachable=0 failed=0 skipped=4 rescued=0 ignored=0
srv03 : ok=19 changed=4 unreachable=0 failed=0 skipped=4 rescued=0 ignored=0

@gusechuisheng
Copy link
Author

How to handle this error

@braaqwesi
Copy link

on the all affected DC. check connectivity to powershell source
Test-NetConnection -ComputerName www.powershellgallery.com

if result =] true. then proceed with the command below.
Install-Module -Name xDnsServer -Force -AllowClobber

Else

you will need to fix network dns issue by manually configuration secondary DNS 8.8.8.8 on the NAT NIC with internet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants