We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
How-to create PTR records in Vesta?
How-to create PTR records in Vesta?
Hello.
First of all, i searched the forums and i didn't found an answer for my question. All answers i got is to contact my provider.
Something that doesn't apply to me.
I have /22 IP range that i got from the RTR. And i configured properly the reverse domain for in-addr.arpa.
My question is: How damn will i add the PTR record for ip's?
I tried to add the PTR record for xxx.xxx.xxx.0 and Vesta doesn't accept it.
Does that mean that i can never configure a PTR for the 0 ip?
Note 1: If i add it manually on the .db dns file and restart bind, it works perfectly!
Note 2: If i add the ip finishing in 1 or 2 or etc... it also works perfectly. Only the ip ending in 0 (zero) doesn't work.
Any advice?
First of all, i searched the forums and i didn't found an answer for my question. All answers i got is to contact my provider.
Something that doesn't apply to me.
I have /22 IP range that i got from the RTR. And i configured properly the reverse domain for in-addr.arpa.
My question is: How damn will i add the PTR record for ip's?
I tried to add the PTR record for xxx.xxx.xxx.0 and Vesta doesn't accept it.
Does that mean that i can never configure a PTR for the 0 ip?
Note 1: If i add it manually on the .db dns file and restart bind, it works perfectly!
Note 2: If i add the ip finishing in 1 or 2 or etc... it also works perfectly. Only the ip ending in 0 (zero) doesn't work.
Any advice?
Re: How-to create PTR records in Vesta?
This problem has not been solved yet.
Re: How-to create PTR records in Vesta?
you can't add ptr from vesta ask your server provider to set it up. Ensure the hostname which you're going to use have a valid A record DNS
Re: How-to create PTR records in Vesta?
You CAN add ptr records to vesta! But you've to ensure, that the name servers are also added to your ipv4 block. We work also with a /22 subnet and ptr records over vesta as dns server.
For that we've splitted our subnet to 4x/24 and add for every subnet a dns zone:
For example your network is 10.11.12.0/24, add a zone with the address: 12.11.10.in-addr.arpa
Then add a record, set type to ptr, the record to 1 and the value to your valid hostname.
So the address 10.11.12.1 will now lookup properly to your.hostname.tld.
-
- Posts: 2
- Joined: Tue Nov 13, 2018 1:54 am
- Os: CentOS 6x
- Web: apache + nginx
Re: How-to create PTR records in Vesta?
Hi ScIT,
I was fascinated to explore the idea of setting up the reverse DNS as per your last reply and i tried to follow your instructions, but I don't think I could get it to work. I think perhaps I did not fully understand your instructions and was hoping on a more detailed response from you. Which would be very much appreciated.
Eg, forward IP is 122.147.188.89
What I tried was:
1. create a new domain with 188.147.122.in-addr.arpa
2. create a PTR record in that domain with record number 89 and value my.domain.com
3. have NS records pointing to ns1.my.domain.com and ns2.my.domain.com
4. have ns1 A records pointing to 122.147.188.89 and ns2 A records pointing to (in my case the same ) 122.147.188.89
Can you please shed some more light on this ?
Thank you.
I was fascinated to explore the idea of setting up the reverse DNS as per your last reply and i tried to follow your instructions, but I don't think I could get it to work. I think perhaps I did not fully understand your instructions and was hoping on a more detailed response from you. Which would be very much appreciated.
Eg, forward IP is 122.147.188.89
What I tried was:
1. create a new domain with 188.147.122.in-addr.arpa
2. create a PTR record in that domain with record number 89 and value my.domain.com
3. have NS records pointing to ns1.my.domain.com and ns2.my.domain.com
4. have ns1 A records pointing to 122.147.188.89 and ns2 A records pointing to (in my case the same ) 122.147.188.89
Can you please shed some more light on this ?
Thank you.