10-09-2025 08:46 AM
We're trying to add in some firewall rules to allow access to some microsoft servers from an extremely limited vlan. one of the URLs is crl.microsoft.com. When adding it in, everything looks fine until the url is completed then it gives an error that it must be valid input. changing it to crd.microsoft.com is fine, crl.microsoft.co shows fine, but crl.microsoft.com shows an error. Any ideas what would cause this?
10-09-2025 08:59 AM
Are you sure that it's a valid domain?
10-09-2025 09:02 AM
it does :
;QUESTION crl.microsoft.co. IN A ;ANSWER crl.microsoft.co. 3600 IN A 104.215.95.187 crl.microsoft.co. 3600 IN A 52.164.206.56
I just tested it in my lab and it works.
No idea how you are getting this error, that's curious
10-09-2025 09:19 AM
yeah, .co works, .com does not
10-09-2025 10:10 AM
That's odd since I already have 2 these in my firewall rules. I deleted them and re-added without problems.
10-09-2025 09:02 AM
I would suspect perhaps the dashboard is having a dns validation issue. This is speculative but The URL is valid, so my thought is maybe the dashboard validates added urls somehow and something intermittent is causing a failure?
Regardless, I think support is going to be your best bet for a resolution.
10-09-2025 11:36 AM
When you get an invalid input error, it usually means there is an illegal character is in the input. I have been caught out before with either a leading or trailing space.
Copy and paste the text to something like notepad. Save it with an encoding of ANSI (or ASCII, depending on your editor) to strip out unicode charcaters.
Double-check there are no trailing spaces, and then copy and paste it back in again.
10-09-2025 11:41 AM
I'm not copying and pasting to begin with so there is no invalid characters.
if i type it in then change the 'l' to a 'd' it's fine, if I just remove the 'l' it's fine, but as soon as I complete the url it turns red saying there is an issue. no spaces, nothing extra.
10-09-2025 11:37 AM
This screenshot seems to suggest a top level domain of co was used instead of com.
10-09-2025 11:43 AM
that was me showing that while typing the url everything is fine and it shows it as a domain until i finish typing. kind of a during and after
10-09-2025 11:51 AM
It seems to work for me.
Is this an ordinary outbound L3 firewall rule, or something else?
10-09-2025 12:12 PM
It's an outbound L3 firewall rule that is being added to a template.
10-09-2025 12:27 PM
I too have no problem configuring that URL in a L3 firewall rule for a standalone or template bound network.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide