I should have noted: The /56's and /64's sections are relative to
the zone file itself, which is for /48.
Jesse DuPont
Network Architect
email: jesse.dup...@celeritycorp.net
Celerity Networks LLC
Celerity Broadband LLC
Like us!
facebook.com/celeritynetworksllc
Like us!
facebook.com/celeritybroadband
![]()
On 1/17/19 4:09 PM, Jesse DuPont wrote:
Here's what I do for PTP links (/126's) and statics:
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.0.0.0.c.f.7.0.6.2.ip6.arpa.
IN PTR sdpb-ccr-sfp11.celerityinternet.com.
2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.0.0.0.c.f.7.0.6.2.ip6.arpa.
IN PTR belle-ccr-sfp1.celerityinternet.com.
Here's what I do for /56's at each tower (using wildcards):
; *.x.x would be for
/56s (i.e. *.1.0 would be 2607:fc00:2:100::/56)
*.1.0 IN PTR
sub-dhcpv6-sprf-sdpb.celerityinternet.com.
*.2.0 IN PTR
sub-dhcpv6-sprf-chkncrk.celerityinternet.com.
*.3.0 IN PTR
sub-dhcpv6-sprf-brkvw.celerityinternet.com.
*.4.0 IN PTR
sub-dhcpv6-sprf-bckdlt.celerityinternet.com.
Here's for /64's (using wildcards):
; *.x.x.x.x would be
for /64s (i.e. *.0.0.7.1 would be 2607:fc00:2:1700::/64)
*.0.0.7.1 IN PTR
sub-slaac-sprf-bckdlt.celerityinternet.com.
*.1.0.7.1 IN PTR sub-slaac-blfr.celerityinternet.com.
*.2.0.7.1 IN PTR
sub-slaac-stng-fglsng.celerityinternet.com.
*.3.0.7.1 IN PTR
sub-slaac-blah-rancha.celerityinternet.com.
Jesse DuPont
Network Architect
email: jesse.dup...@celeritycorp.net
Celerity Networks LLC
Celerity Broadband LLC
Like us!
facebook.com/celeritynetworksllc
Like us!
facebook.com/celeritybroadband
![]()
On 1/17/19 3:43 PM, Matt wrote:
Centos 7 running bind/named in a VM. Reverse and
forward dns for ipv4 works fine and has been for many years.
Not super pressing issue.
|
--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com