[196124] in North American Network Operators' Group
Re: Anyone from AT&T DNS?
daemon@ATHENA.MIT.EDU (Matt Peterman)
Fri Oct 6 03:12:54 2017
X-Original-To: nanog@nanog.org
From: Matt Peterman <mpeterman@apple.com>
Date: Wed, 04 Oct 2017 23:03:38 -0400
In-reply-to: <CAL9jLaa6ETkBCHmpEwWA9nJd5EzC7p6rVkPqAnxnHBBEihDphg@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
The correct format is as shown below (this is from another /25 I have =
from AT&T that has DNS setup correctly)=20
$ dig +short CNAME 1.120.232.108.in-addr.arpa
1.0.120.232.108.in-addr.arpa.
So for the block I am having an issue with the CNAME records should be=20=
For 107.207.168.128 should be 128.128.168.207.107.in-addr.arpa (it =
shouldn't have =E2=80=9C/25=E2=80=9D in the middle of it - you can=E2=80=99=
t even have =E2=80=9C/=E2=80=9C in a DNS entry AFAIK)
If I do another address from my block I get $ dig +short CNAME =
191.168.207.107.in-addr.arpa
191.128/25.168.207.107.in-addr.arpa.
Again that would should be 191.128.168.207.107in-addr.arpa.=20
Somehow AT&T DNS got the =E2=80=9C/25=E2=80=9D prefix length in all of =
the DNS entries=E2=80=A6
Matt
> On Oct 4, 2017, at 10:53 PM, Christopher Morrow =
<morrowc.lists@gmail.com> wrote:
>=20
>=20
>=20
> On Wed, Oct 4, 2017 at 10:43 PM, Matt Peterman <mpeterman@apple.com =
<mailto:mpeterman@apple.com>> wrote:
> The PTR record CNAMEs for my /25 allocated prefix are all messed up. =
They are returning as
> $ dig +short CNAME 128.168.207.107.in-addr.arpa
> 128.128/25.168.207.107.in-addr.arpa.
>=20
> Which is obviously a completely invalid DNS entry. I have opened a =
ticket through the web portal for =E2=80=9Cprov-dns=E2=80=9D but =
Haven=E2=80=99t gotten a response for 7 days.
>=20
> If anyone from AT&T DNS or knows anyone from AT&T DNS that can help it =
would be appreciated!
>=20
>=20
> isn't this one of the proper forms of reverse delegation in CIDR land?=20=
>=20
> like:
> =
http://support.simpledns.com/kb/a146/how-to-sub-delegate-a-reverse-zone.as=
px =
<http://support.simpledns.com/kb/a146/how-to-sub-delegate-a-reverse-zone.a=
spx>
>=20
> describes, or in a (perhaps more wordy fashion) in RFC2317?
> http://tools.ietf.org/html/rfc2317 =
<http://tools.ietf.org/html/rfc2317>
>=20
> I think it may be the case that the NS hosts are not prepared for such =
a domain/record mapping though... the nameservers that would need to to =
be authoritative for a zone like:
>=20
>=20
> 128/25.168.207.107.in-addr.arpa.
>=20
> and have a bunch of PTR records like:
>=20
> 128 IN PTR foo.you.com <http://foo.you.com/>.
> 129 IN PTR bar.you.com <http://bar.you.com/>.
>=20
> etc...
>=20
>=20
