[196184] in North American Network Operators' Group
Re: Anyone from AT&T DNS?
daemon@ATHENA.MIT.EDU (Mark Andrews)
Tue Oct 10 20:57:57 2017
X-Original-To: nanog@nanog.org
To: Jay Farrell <jayfar@jayfar.com>
From: Mark Andrews <marka@isc.org>
In-reply-to: Your message of "Thu, 05 Oct 2017 04:12:30 -0400."
<CAN414UfOQH-rOsJ4V_idiv-2UQi0jVM=w5AOs6HmnA-NkDvESg@mail.gmail.com>
Date: Mon, 09 Oct 2017 12:42:48 +1100
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
In message <CAN414UfOQH-rOsJ4V_idiv-2UQi0jVM=w5AOs6HmnA-NkDvESg@mail.gmail.com>, Jay Farrell via NANOG writes:
> Yep, the notation with the slash used to be ATT's standard method. At my
> job (where we had some customers with ATT MIS T1 circuits) we transitioned
> to a web front end for our DNS that didn't allow for the slash, so we had
> to nudge ATT to allow us to use a dash notation instead for delegations.
>
> As far as to what can appear in a DNS entry, you'd be amazed. I encountered
> a PTR record containing a full URL, http:// and everything; it didn't
> actually work of course, but bind allowed it to exist. When I tracked down
> the cow-orker who had entered it, he said he knew it wasn't valid, but he
> did it that way when the customer insisted it had to be thus. :-D
DNS labels can be octet string [0..63] with the zero length octet
string being being reserved or the root label and '*' for the
wildcard label (there is no way to turn this off).
Hostnames on the other hand are restricted to LDH.
Unfortunately many tools are not written by people who understand
the difference. Additionally lots of administrators also don't
know the difference. They also often don't understand why hostnames
are restricted to LDH.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
