ICANN has said they will never delegate .internal and it should be used for these kinds of private uses.
I'm a coauthor on this Internet draft so I'm ofc rather biased.
ICANN has said they will never delegate .internal and it should be used for these kinds of private uses.
I'm a coauthor on this Internet draft so I'm ofc rather biased.
That is how I feel about the takeover of the .local domain for mDNS. Why step in and take a widely used suffix that is shorter for something that will almost always be automated, instead of taking something longer to leave us alone with our .local setups. I will not forgive, I will not forget!
Yeah, not sure why that got approved in the first place. Sure, it wasn't officially part of any of the protected/reserved names or whatever when it got bought, but Google shouldn't have been allowed to purchase it at all since it was in use already for non-public stuff. That they also require HTST just in order to break existing setups is just salt on the wounds.
Does reusing it cause any problem for the mDNS, or does mDNS usage cause problem for the internal-domains usage?
And then when you reconfigure it, depending on the stack it won't bother querying mDNS at all if a DNS resolver responds.