3 ms·
Do you have a practical example where that matters? Because I've never seen anyone link to a page with a trailing . in the domain.
by francislavoie 6y ago
Do you have a practical example where that matters? Because I've never seen anyone link to a page with a trailing . in the domain.
- kuschku 6y agoIf you have a situation where due to your search domain, e.g. corp.com, both exampleA.tld and exampleA.tld.corp.com would be valid DNS resolutions. If you’re already using something like kubernetes, which does such resolutions, this can actually become an issue. e.g. in the cluster ServiceA can call ServiceB by navigating to http://serviceb/ http://serviceb/, and if the name of serviceb overlaps with an actual real-world domain, you need to use http://serviceb./ http://serviceb./ to ensure you call the outside-world site.
- francislavoie 6y agoOkay. As far as I can tell, Caddy can be configured to handle that, you just need to tell it to. Have you tried to configure Caddy to accept requests to hostnames with a trailing dot recently?
- kuschku 6y agoWell that’s the issue. I need to access external websites that way. You could imagine it as a user entering a URL, and a service fetching that URL. To ensure this service doesn’t accidentally fetch an internal site, it transforms the URL to one with a . at the end. So, I need all websites intended to be fetched this way to support the proper DNS RFCs. Ever since Caddy and Traefik became a thing my tool has stopped working for more and more non-standard webpages. Even caddyserver.com itself is broken. In the end, I’ve simply chosen not to use caddy or traefik based websites.