Describe the Bug
Specifying a variable as type Stdlib::Fqdn allows ipv4 addresses. This issue is compounded when using Stdlib::Host as with the inclusion of Fqdn it allows truncated ipv4 addresses such as 10.10.10.10.10.
Expected Behavior
IPv4 addresses should be validated when using Stdlib::Host and not accepted within the Stdlib:Fqdn type
Steps to Reproduce
Steps to reproduce the behavior:
-
Create a variable with type Stdlib::Fqdn
-
Submit valid or truncated ipv4 address, which passes (the regex)
-
Create a variable with type Stdlib::Host
-
Submit a truncated ipv4 address, which passes (the regex)
Environment
Additional Context
Unsure if this is a flaw in catering for numerical fqdn's, and how it can be addressed. TL:DR is that using Stdlib::Host does not ensure ipv4 addresses are valid
Describe the Bug
Specifying a variable as type
Stdlib::Fqdnallows ipv4 addresses. This issue is compounded when usingStdlib::Hostas with the inclusion ofFqdnit allows truncated ipv4 addresses such as10.10.10.10.10.Expected Behavior
IPv4 addresses should be validated when using
Stdlib::Hostand not accepted within theStdlib:FqdntypeSteps to Reproduce
Steps to reproduce the behavior:
Create a variable with type
Stdlib::FqdnSubmit valid or truncated ipv4 address, which passes (the regex)
Create a variable with type
Stdlib::HostSubmit a truncated ipv4 address, which passes (the regex)
Environment
Additional Context
Unsure if this is a flaw in catering for numerical fqdn's, and how it can be addressed. TL:DR is that using
Stdlib::Hostdoes not ensure ipv4 addresses are valid