<div dir="ltr"><div>[ Classification Level: <font color="green">PUBLIC</font> ]</div><br>It's not like "speed dialing" consists of prepending a bunch of more-or-less arbitrary area codes and exchanges and hoping that eventually you'll get the right combination of numbers to reach the intended recipient. THAT would be the proper analogy for suffix-searching.<div><br></div><div>A better analogy of "speed dialing", in the TCP/IP context, would be browser bookmarks and the like, i.e. a limited, simplified list of choices, on the frontend, each of which translates to the appropriate protocol- and/or technology-specific identifiers, on the backend.
I don't have a problem with app features that make people's lives more convenient, as long as what ends up in the DNS ecosystem is an unambiguous FQDN.<div><br></div><div>As for addressing coworkers by their short names, that works and sometimes doesn't. I once worked regularly with 5 people who all had the first name "Matt" (now we're down to only 3 in our area :-)</div><div><br></div><div> - Kevin</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 28, 2019 at 6:02 PM Paul Kosinski via bind-users <<a href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">"... long ago adapted to using full numbers, including area codes, for<br>
pretty much *all* phone dialing ..."<br>
<br>
Except that that proved to be so onerous that people often use "speed<br>
dialing" for commonly dialed numbers. (Not to mention the fact that<br>
people usually address their friends and coworkers by short names.)<br>
<br>
<br>
On Mon, 28 Oct 2019 12:19:35 -0400<br>
Kevin Darcy <<a href="mailto:kevin.darcy@fcagroup.com" target="_blank">kevin.darcy@fcagroup.com</a>> wrote:<br>
<br>
> [ Classification Level: PUBLIC ]<br>
> <br>
> My opinion? It's better to wean your users away from shortnames than<br>
> to try to cobble together kludges, on the client side or the BIND<br>
> side, to support a bad habit. Shortnames introduce ambiguity, lead to<br>
> nasty surprises, are inefficient and insecure. Just like we (in the<br>
> U.S. at least) long ago adapted to using full numbers, including area<br>
> codes, for pretty much *all* phone dialing, people can adapt to using<br>
> FQDNs. They've already adapted to it, overwhelmingly, for Internet<br>
> web traffic (notwithstanding some "helpful" browsers that will tack<br>
> on "www" to the front of a shortname, and ".com" at the end, which is<br>
> often *not* what is wanted or safe). Why have a different user<br>
> experience, when on or off the enterprise network, a perimeter that<br>
> is quickly eroding? Just use FQDNs everywhere, keep it consistent.<br>
> <br>
> Anyway, that's my 2-cents, from someone who has been battling the<br>
> "shortname disease" for decades, with a substantial amount of<br>
> (although not perfect) success.<br>
> <br>
> <br>
> - Kevin<br>
> <br>
> On Mon, Oct 28, 2019 at 8:56 AM MEjaz <<a href="mailto:mejaz@cyberia.net.sa" target="_blank">mejaz@cyberia.net.sa</a>> wrote:<br>
> <br>
> > Noxexistent domain error .<br>
> ><br>
> > Here is my configuration.<br>
> > =======================<br>
> ><br>
> > zone "crm365app" {<br>
> > type master;<br>
> > file "<a href="http://crm365app.cyberia.net.sa" target="_blank">crm365app.cyberia.net.sa</a>.hosts";<br>
> > allow-query {any;};<br>
> > };<br>
> ><br>
> ><br>
> > File<br>
> ><br>
> > ========================================<br>
> > [root@ns1 ~]# cat /var/named/crm365app.cyberia.net.sa.hosts<br>
> > $TTL 3600<br>
> > ; Addresses and other host information<br>
> > ;<br>
> > ;<br>
> ><br>
> > @ IN SOA <a href="http://ns1.cyberia.net.sa" rel="noreferrer" target="_blank">ns1.cyberia.net.sa</a>. <a href="http://root.cyberia.net.sa" rel="noreferrer" target="_blank">root.cyberia.net.sa</a>. (<br>
> > 2015034459 ; serial<br>
> > 43200 ; refresh every 12 hours<br>
> > 4320 ; retry after 1 hour<br>
> > 1209600 ; expire after 2 weeks<br>
> > 21600 ) ; minimum<br>
> ><br>
> > ; Define the name servers and mail servers<br>
> ><br>
> > IN NS <a href="http://ns1.cyberia.net.sa" rel="noreferrer" target="_blank">ns1.cyberia.net.sa</a>.<br>
> > IN NS <a href="http://ns2.cyberia.net.sa" rel="noreferrer" target="_blank">ns2.cyberia.net.sa</a>.<br>
> ><br>
> > IN MX 10 <a href="http://smtp.cyberia.net.sa" rel="noreferrer" target="_blank">smtp.cyberia.net.sa</a>.<br>
> ><br>
> > ; Define localhost<br>
> > * IN A 127.0.0.1<br>
> ><br>
> > ; Define hosts in this zone<br>
> ><br>
> ><br>
> > www IN CNAME <a href="http://webhost.cyberia.net.sa" rel="noreferrer" target="_blank">webhost.cyberia.net.sa</a>.<br>
> > crm365app IN A 212.71.33.252<br>
> ><br>
> > =========================================zone file<br>
> > end=============================<br>
> ><br>
> > [root@ns1 named]# host crm365app<br>
> > Host crm365app not found: 3(NXDOMAIN)<br>
> > [root@ns1 named]# named-checkzone crm365app<br>
> > crm365app.cyberia.net.sa.hosts<br>
> > zone crm365app/IN: loaded serial 2015034459<br>
> > OK<br>
> ><br>
> > -----Original Message-----<br>
> > From: bind-users [mailto:<a href="mailto:bind-users-bounces@lists.isc.org" target="_blank">bind-users-bounces@lists.isc.org</a>] On<br>
> > Behalf Of Reindl Harald<br>
> > Sent: Monday, October 28, 2019 1:46 PM<br>
> > To: <a href="mailto:bind-users@lists.isc.org" target="_blank">bind-users@lists.isc.org</a><br>
> > Subject: Re: Zoneformat<br>
> ><br>
> ><br>
> ><br>
> > Am 28.10.19 um 11:01 schrieb MEjaz:<br>
> > > *From:* MEjaz [mailto:<a href="mailto:mejaz@cyberia.net.sa" target="_blank">mejaz@cyberia.net.sa</a>]<br>
> > > *Sent:* Monday, October 28, 2019 10:27 AM<br>
> > > *To:* '<a href="mailto:bind-users-bounces@lists.isc.org" target="_blank">bind-users-bounces@lists.isc.org</a>'<br>
> > > <<a href="mailto:bind-users-bounces@lists.isc.org" target="_blank">bind-users-bounces@lists.isc.org</a>><br>
> > > *Subject:* Zoneformat<br>
> > ><br>
> > > Is ther any way I can create the zone without the (.) I mean non<br>
> > > fully qualified domain name just as "example" instead<br>
> > > "<a href="http://example.com" rel="noreferrer" target="_blank">example.com</a>"'<br>
> ><br>
> ><br>
> > what is the problem you try to solve?<br>
_______________________________________________<br>
Please visit <a href="https://lists.isc.org/mailman/listinfo/bind-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/bind-users</a> to unsubscribe from this list<br>
<br>
bind-users mailing list<br>
<a href="mailto:bind-users@lists.isc.org" target="_blank">bind-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/bind-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/bind-users</a><br>
</blockquote></div>