PTR Records in ISPConfig 3
I've authority over of my ip block (example: 192.168.1.0/28)
I'm trying to create my own PTR records in ISPConfig.
This is a example of PTR Zone using bind9:
In ISPConfig I'm trying to create a new zone with name 1-220.127.116.11.in-addr.arpa. and next, will create a NS record and PTR record. Example:
You missed to add the dot at the end of ns1.domain.com, ns2.domain.com
and test.domain.com. It must be:
It's added.. And when I try to resolve my IP, I get
Another zone may be required
I believe you need another reverse DNS zone for the whole subnet, 1.168.192.in-addr.arpa.
In this zone, add NS records:
NS 1-30 ns1.yourserver.com.
NS 1-30 ns2.yourserver.com.
and a CNAM for each record you have control over, pointing to your 1-18.104.22.168 zone:
CNAME 1 1.1-30 (no trailingperiods, the full zone name is appended)
CNAME 2 2.1-30
CNAME 30 30.1-30
Therefore, given a lookup for 192.168.1.5, it will look for 22.214.171.124... which returns 5.1-30 (no period, so really equal to 5.1-126.96.36.199.in-addr.arpa) which will then look in your 1-188.8.131.52... zone and find the PTR record for 5.
Note the 1-30 zone prefix is arbitrary and can be anything really, but it helps with identication.
I create a new zone with name: 1.168.192.in-addr.arpa.
And I create a records:
NS 1-30 ns1.domain.com.
NS 1-30 ns2.domain.com.
CNAME 1 1-30
But it not works..
The CNAME records should be like:
Here is a full briefing I have for users of ISPConfig:
1. Create a new zone for the block of IPs and assign the new zone to the client
Example: Customer has 192.168.10.8/29, create zone 8-184.108.40.206.in-addr.arpa
(Note: the "8-29" zone prefix is arbitrary but helps us with identification of subnet)
2. Move the records (Example: hosts 8 through 15) manually or via database to new zone
3. In old zone (10.168.192.in-addr.arpa), add NS records for the new zone prefix
Example: NS 8-29 dns1.example.com.
NS 8-29 dns2.example.com.
4. In old zone, add CNAME records for each host in customer's range pointing to the new zone
in the form of CNAME [host] [host].[new zone prefix]
Example: CNAME 9 9.8-29
CNAME 10 10.8-29
5. Refresh the zones.
Now a PTR lookup will for 192.168.10.11 will query 220.127.116.11.in-addr.arpa and get a CNAME
of 11.8-18.104.22.168.in-addr.arpa which will return the proper value for host 11 in the newly
(Note: This procedure can be applied to a single record and non-continous ranges)
|All times are GMT +2. The time now is 14:16.|
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.