dsccommunity / dsccommunity/NetworkingDsc
xHostsFile: won't let me have identical hostnames with different adresses
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 235
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Details of the scenario you tried and the problem that is occurring:
The DSC configuration that is using the resource (as detailed as possible):
Hi
I am trying to run this:
xHostsFile pool01
{
HostName = 'sfbpool1.domain.com'
IPAddress = '10.0.5.210'
Ensure = 'Present'
}
xHostsFile pool02
{
HostName = 'sfbpool1.domain.com'
IPAddress = '10.0.5.211'
Ensure = 'Present'
}
Meant to simulate round robin DNS. But xHostsFile fails with this message:
Test-ConflictingResources : A conflict was detected between resources '[xHostsFile]pool01 (C:\Script\dsc\SkypeForBusinessDSC.ps1::292::9::xHostsFile)' and '[xHostsFile]pool02 (C:\Script\dsc\SkypeForBusinessDSC.ps1::299::9::xHostsFile)' in node 'Edge01.domain.com'. Resources have identical key properties but there are differences in the following non-key properties: 'IPAddress'. Values '10.0.5.210' don't match values '10.0.5.211'. Please update these property values so that they are identical in both cases.
Version of the Operating System and PowerShell the DSC Target Node is running:
Windows Server 2016 Standard 1607
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
5.4.0.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the provided xHostsFile configuration on the stated Windows Server 2016 and PowerShell DSC versions. Inspect how xHostsFile identifies key properties and how DSC reports the conflicting resources; done means identical hostnames can be configured with different IPAddress values without this conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100