Skip to content

FQDN resolution not using existing cached IP's on DNS Lookup failure #55

Description

@King98ax

Hi, We have come across an issue with Version 5.3.0 where DPC will fail to add routes into the VPN for FQDN resolved IP's if they fail to resolve with "Error: No such host is known". DPC has these FQDN's already cached in the registry under the "DNSRouteList", however it appears not to use them for when this error occurs.

Event log

Profile ... may be inaccurate due to the following Warnings:
- Failed to resolve DNS - ers.nhs.uk Error. No such host is known

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions