fqdn-template parameter generates DNS entry for ingress name

[nphmuller]

I noticed that ExternalDNS (v0.5.0) with the fqdn-template parameter also generates DNS records for the Name metadata field on Ingress resources. Does this actually have any benefit? Because I think this will always simply trigger the fallback route when browsing to it. Of course this behavior is useful for (External) Service resources, but I don't think it's actually useful on Ingress resources and will create 2 additional (A and TXT record) DNS entries per Ingress resource.

So what I'm basically asking is if this is a bug, or if it's the intended behavior which is actually useful for a reason I missed.

[linki]

It was added in response to #143.

Indeed, the use case is for Ingresses without any rules. Adding the hostname annotation or the fqdn-template flag allows you to generate DNS names for the default backend in this case.

[nphmuller]

Okay. Thanks for taking the time to explain it to me. :)