[dns-operations] bug in Apache handling of real FQDNs

[Eli Heady]

Since learning what 'fully qualified' really means, I've assumed this falls
into an area of arcane trivia that many, if not most of the applications
built atop the DNS probably don't implement correctly. Nearly every time
this topic comes up at work it's due to a junior admin publishing
something.tld.something.tld in our DNS, and I mostly get blank stares when
I talk about the trailing dot and implied root in what's commonly thought
to be FQDN's.

At the same time, $WORK website fails to load when requested with the
trailing dot (also running Apache). Maybe time to address that.

A couple other funny examples:

Apache: https://www.cio.gov./
Nginx (cloudflare): https://www.ietf.org./

(the cloudflare example just be them caching the response from IETF's
apache backend servers - https://ietf.org./ yeilds a 400 response from
Apache)

Eli

On Sat, Jun 6, 2015 at 3:13 PM, Fred Morris <m3047 at m3047.net> wrote:
> On Saturday 06 June 2015 09:56, Fred Morris wrote:
>> [...]
>> Thoughts? Comments? Worth reporting?
>
> Somebody thought so. ;-) Bug 58007 has been filed.
>
> --
>
> Fred Morris
>
> _______________________________________________
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> dns-jobs mailing list
> https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20150606/def6c88a/attachment.html>