@RickJones maybe .mil does not get recognized as valid TLD? No problem to create on the appliance though. Maybe some NSM wiz can chime in here, @Larry@TKWITS
But this problem is worse than described or what you might think. In Version 2.3.3-7-R35 of NSM it is not possible to create ANY FQDN! I tried www.google.com and got:
I'm thinking the Quality Assurance team for this product offering is MIA. Pretty disgraceful, really.
@RickJones if you've got the stomach for it, please open up a Support Case. Based on past issues I've raised, if you are very lucky, you might see this fixed in about three or four months.
Answers
@RickJones maybe .mil does not get recognized as valid TLD? No problem to create on the appliance though. Maybe some NSM wiz can chime in here, @Larry @TKWITS
--Michael@BWC
That was my test of @RickJones value
But this problem is worse than described or what you might think. In Version 2.3.3-7-R35 of NSM it is not possible to create ANY FQDN! I tried www.google.com and got:
I'm thinking the Quality Assurance team for this product offering is MIA. Pretty disgraceful, really.
@RickJones if you've got the stomach for it, please open up a Support Case. Based on past issues I've raised, if you are very lucky, you might see this fixed in about three or four months.
@Larry ,
Thank you for the confirmation. @shiprasahu93, is there already a Jira case for this issue on the SonicWall engineering side?
Thank You,
Rick Jones
Sr. Network Security Engineer