Reverse Lookup Zone help

[Sir Asvald]

I'm having issues with my Reverse Lookup Zone. I have a VPS (windows 2012 R2) which has an IP of 51.255.6.168. I've creating the Reverse Lookup Zone. When try to point the server to it, it says "A new record cannot be created. The IP Address is invalid"

Please help.  

 

[jj9987]

There's a dot at the end of the IP address.

[Sir Asvald]

1 minute ago, jj9987 said:

There's a dot at the end of the IP address.

That's how it is. It can be removed. I tried to remove it.

[Dujith]

6 minutes ago, Abdul201588 said:

That's how it is. It can be removed. I tried to remove it.

Just checked on server 2008 and 2016. Both do not have that dot at the end. 

Weird.

[leadeater]

Looks like you have configured your reverse zone incorrectly, should only be 3 or less octets in the zone definition so you can enter the final segment of the IP. Also FYI it's easier to create PTR records by going to the A record and ticking automatically create the PTR but the correct zone must exist first.

 

 

[Sir Asvald]

8 minutes ago, leadeater said:

Looks like you have configured your reverse zone incorrectly, should only be 3 or less octets in the zone definition so you can enter the final segment of the IP. Also FYI it's easier to create PTR records by going to the A record and ticking automatically create the PTR but the correct zone must exist first.

 

Okay. I created another zone using 3 octets. It worked when I added the ptr.  When I try to resolve the ptr using online tools it goes back to dns11.ovh.net.

 

does that mean I can do anything?

 

Spoiler

 

[leadeater]

8 minutes ago, Abdul201588 said:

Okay. I created another zone using 3 octets. It worked when I added the ptr.  When I try to resolve the ptr using online tools it goes back to dns11.ovh.net.

 

does that mean I can do anything?

 

  Reveal hidden contents

 

Right I should have noticed that it was a public address. So unfortunately you won't be able to configure PTR records for any public address assigned to you since you are not the authoritative owner of the IP address, your ISP is and the PTR needs to be set by them or forward to your DNS server.

[Sir Asvald]

1 minute ago, leadeater said:

Right I should have noticed that it was a public address. So unfortunately you won't be able to configure PTR records for any public address assigned to you since you are not the authoritative owner of the IP address, you ISP is and the PTR needs to be set by them or forward to your DNS server.

Damnit. I got the VPS so I could use it as a name server..

[leadeater]

5 minutes ago, Abdul201588 said:

Damnit. I got the VPS so I could use it as a name server..

You can, just not for PTR records. A records will work fine etc. Let me guess you want the PTR set correctly due to email spam reputation scores marking you down because the forwards and reverse dns entries for your MX records do not match?

[Sir Asvald]

4 minutes ago, leadeater said:

You can, just not for PTR records. A records will work fine etc. Let me guess you want the PTR set correctly due to email spam reputation scores marking you down because the forwards and reverse dns entries for your MX records do not match?

I wanted a nameserver because my ISP blocks residential IP (SMTP traffic). Anything I send will be marked as spam.

 

[leadeater]

13 minutes ago, Abdul201588 said:

I wanted a nameserver because my ISP blocks residential IP (SMTP traffic). Anything I send will be marked as spam.

An external DNS server won't help with that then, most ISPs block port 25 on residential connections but they usually unblock on request. It's just a smart default due to tons of computers in the past becoming email spam nodes from viruses.

 

If they won't unblock it you'll have to create a VPN to the VPS and configure an SMTP relay on it then configure your local mail server to use the VPS as a mail relay agent by using the private IP of the VPN connection.

 

Edit:

Actually forget the VPN just change the port on the VPS SMTP relay then configure your local mail server to relay to that IP:Port

[Sir Asvald]

4 minutes ago, leadeater said:

An external DNS server won't help with that then, most ISPs block port 25 on residential connections but they usually unblock on request. It's just a smart default due to tons of computers in the past becoming email spam nodes from viruses.

 

If they won't unblock it you'll have to create a VPN to the VPS and configure an SMTP relay on it then configure your local mail server to use the VPS as a mail relay agent by using the private IP of the VPN connection.

 

Edit:

Actually forget the VPN just change the port on the VPS SMTP relay then configure you local mail server to relay to that IP:Port

I could've done that. I'll try.