• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

RDNS server failure

F

filipersimoes

Guest
Hi, I’m having some trouble to add RDNS into my server. I'm using Windows 2003 with Bind 9.
My ISP had delegated the reverse records to my server but my server gives the "server failure" at dnsstuff tool.

How I am searching:
Asking d.root-servers.net for 130.32.195.200.in-addr.arpa PTR record:
d.root-servers.net says to go to ns-sec.ripe.net. (zone: 200.in-addr.arpa.)
Asking ns-sec.ripe.net. for 130.32.195.200.in-addr.arpa PTR record:
ns-sec.ripe.net [193.0.0.196] says to go to C.DNS.BR. (zone: 195.200.in-addr.arpa.)
Asking C.DNS.BR. for 130.32.195.200.in-addr.arpa PTR record:
c.dns.br [200.192.232.10] says to go to ns4.telemar.net.br. (zone: 32.195.200.in-addr.arpa.)
Asking ns4.telemar.net.br. for 130.32.195.200.in-addr.arpa PTR record: Got CNAME referral to 130.128-255.32.195.200.in-addr.arpa. at server losangeles.iconecta.com.br. (zone 128-255.32.195.200.in-addr.arpa.) [from 200.222.0.35]
Asking c.root-servers.net for 130.128-255.32.195.200.in-addr.arpa. PTR record:
c.root-servers.net [192.33.4.12] says to go to TINNIE.ARIN.NET. (zone: 200.in-addr.arpa.)
Asking TINNIE.ARIN.NET. for 130.128-255.32.195.200.in-addr.arpa. PTR record:
tinnie.arin.net [168.143.101.18] says to go to E.DNS.BR. (zone: 195.200.in-addr.arpa.)
Asking E.DNS.BR. for 130.128-255.32.195.200.in-addr.arpa. PTR record:
e.dns.br [200.229.248.10] says to go to ns2.telemar.net.br. (zone: 32.195.200.in-addr.arpa.)
Asking ns2.telemar.net.br. for 130.128-255.32.195.200.in-addr.arpa. PTR record:
ns2.telemar.net.br [200.202.193.76] says to go to losangeles.iconecta.com.br. (zone: 128-255.32.195.200.in-addr.arpa.)
Asking losangeles.iconecta.com.br. for 130.128-255.32.195.200.in-addr.arpa. PTR record: Error: losangeles.iconecta.com.br [200.195.32.131] reports a SERVER FAILURE.

Answer:
An error occurred: Server losangeles.iconecta.com.br is reporting a server failure (it is probably broken).
 
What is reply from you server when you perform
nslookup somedomain.com you.dns.server.ip?

John S.G.
 
Back
Top