That's actually how it's supposed to be done:
http://www.dns-sd.org/TrailingDotsInDomainNames.html
"It's a little-known fact, but fully-qualified (unambiguous) DNS domain names have a dot at the end. People running DNS servers usually know this (if you miss the trailing dots out, your DNS configuration is unlikely to work) but the general public usually doesn't. A domain name that doesn't have a dot at the end is not fully-qualified and is potentially ambiguous. This was documented in the DNS specification, RFC 1034, way back in 1987 ..."
but the site works just fine without the trailing dot as well.
In your current environment! And probably in all the environments connected to the Internet. But potentially without the dot it would be perfect valid for this to route elsewhere in someone's environment. :)
EDIT: I learned something new today, adding the trailing dot can be a good idea:
http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/we...
Chrome doesn't accept the certificate when the trailing dot is in the request.
I bet if you configured your site to redirect to a URL with a trailing dot, it would break a lot of badly written robots. I'd be interested to hear about how it affects the major search engines before I'd want to implement it on any important sites.