31–40 of 96 posts
What a bizarre response from Google, a couple hours after this was posted: > @Reporter: As we are not very clear about the issue being faced by you, could you please elaborate on the same by providing detailed manual repro steps to reproduce the issue from our end. > Also requesting you to share the expected, actual behaviours along with screen-cast for better understanding of the issue. > *Note: Requesting you to co…
probably just an ai or unskilled triage tech responding?
Earlier quoted context omitted.
Isn't .local specific to 'rendezvous' tech anyway? I forget the generic name but it was Apple that put it on the map under this name. But I mean that serverless broadcast protocol. What I do is I just bought a domain and use that together with DNS-based SSL. It's a bit hard to set up with every different SSL server but it's doable.
The non Apple name is multicast DNS or mDNS. mDNS is exclusive to .local, but not necessarily the other way around. From its Wikipedia entry: "By default, mDNS exclusively resolves hostnames ending with the .local top-level domain. This can cause problems if .local includes hosts that do not implement mDNS but that can be found via a conventional unicast DNS server. Resolving such conflicts requires network-configura…
I notice .alt. now exists.
Can’t you usually force it to skip the search by prefixing with the schema? Certainly if I type in http://example.internal and press enter, I would be very displeased to have that turn into a Google search regardless of whether the part after the // fits some regex or whatever else internal to the browser.
Can’t you usually force it to skip the search by prefixing with the schema? Certainly if I type in http://example.internal and press enter, I would be very displeased to have that turn into a Google search regardless of whether the part after the // fits some regex or whatever else internal to the browser.
Publish a zone file for the domain as authoritative master and secondary on an internet facing DNS server, but have basically no records in the zone (no useful A or CNAME or anything else).
Host the actual DNS for your internal services on your internally-accessible-only DNS server.
Earlier quoted context omitted.
We had them separated once upon a time. UX was arguably worse.
Personally I like them separate. But I’ve been working with folks who are not very computer literate at all and I think I agree with you. If one doesn’t know what a URL is in the first place, how would one distinguish which box to type in?
Earlier quoted context omitted.
We had them separated once upon a time. UX was arguably worse.
I have them separated in firefox because i find it superior.
Also a good argument for, if you run internal-network only resources, to purchase and use an actual domain for it (such as companyname.us or whatever). Publish a zone file for the domain as authoritative master and secondary on an internet facing DNS server, but have basically no records in the zone (no useful A or CNAME or anything else). Host the actual DNS for your internal services on your internally-accessible-o…
Is the motivation known for this change? Any clue from commit history?
There has not been a change, it's always worked like this. ICANN only reserved *.internal for use in internal networks a few months ago.