Fix reverse DNS situation for 172.22.119.0/24

This removes inetnum/172.22.119.0_24, which was added as a hack
ages ago by Fritz to add reverse DNS for 172.22.119.128/26, before
it was possible to have reverse DNS for networks smaller than /24.

This also removes dns/fritz.dn42, which I added a while ago to
point ns[34].fritz.dn42 at my nameservers to have working RDNS.
This commit is contained in:
Lukas Martini 2017-11-11 18:12:13 +01:00
parent 9ef8c23168
commit 53910128f9
No known key found for this signature in database
GPG Key ID: F828A0C8C9E1BD2C
2 changed files with 0 additions and 18 deletions

View File

@ -1,9 +0,0 @@
domain: fritz.dn42
remarks: Workaround to unbreak reverse DNS for my subnet,
remarks: which has its nameservers hardcoded to ns[34].fritz.dn42
admin-c: LUTOMA-DN42
tech-c: LUTOMA-DN42
mnt-by: LUTOMA-MNT
mnt-by: FRITZ-MNT
nserver: ns1.lutoma.dn42
status: EVALPEND 1507027029

View File

@ -1,9 +0,0 @@
inetnum: 172.22.119.0 - 172.22.119.255
netname: REALLOCATED-NET-172-22-119-0-24-DNS
descr: Workaround DNS limitation of delegating nets </24
status: ASSIGNED
nserver: ns3.fritz.dn42
nserver: ns4.fritz.dn42
bgp-status: active
cidr: 172.22.119.0/24
mnt-by: DUMMY-MNT