failed reverse dns on slingshot...

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › failed reverse dns on slingshot...

malco

4 posts

Wannabe Geek

#55305 29-Dec-2009 13:53

203-184-52-xx.callplus.net.nz is the reverse for 203.184.52.xx for example

But it is not a vaild dns record, which causes problem with some IRC servers.

An attempt at logging a fault via the call center was met with the usual frustrations and ignorance.

Can someone from slingshot please advice if this is going to be resolved soon?

Detruire

1788 posts

Uber Geek
+1 received by user: 84

#285835 29-Dec-2009 14:39

Have you posted this on the Slingshot forums?

You'll probably get a quicker and more useful response there.

rm *

malco

4 posts

Wannabe Geek

#285841 29-Dec-2009 15:06

No, am not joined up to it and really cant be bothered with registering for their forums since what I have read on it is just purile teenage bull to be honest.

rscole86

4999 posts

Uber Geek
+1 received by user: 462

Moderator

Trusted

Lifetime subscriber

#285853 29-Dec-2009 16:02

So you want support from Slingshot, yet you do not want to use their official forums?
Geekzone do not host their official forums, this is just a place to discuss Slingshot, their products, service etc.

Detruire

1788 posts

Uber Geek
+1 received by user: 84

#285864 29-Dec-2009 16:53

As far as I am aware, the user "Slingshot" on these forums works in marketing, whereas there are a couple of users on the 'official' forums who works in network operations.

rm *

hellonearthisman

1819 posts

Uber Geek
+1 received by user: 52

Trusted

#285966 29-Dec-2009 23:31

The Slingshot forums are not an Official support system, but do have great support for Tech questions.

I would say, try and disable the Slingshot caching (via my account settings on Slingshot homepage) and see if the fixes your issue.

Detruire

1788 posts

Uber Geek
+1 received by user: 84

#285974 30-Dec-2009 00:21

Nah, this isn't anything to do with cache or access, but the way SS have set up RDNS entries.
While they do have RDNS entries for the IP addresses that they're allocating, there is no record pointing the RDNS entry at the IP.

Example: 119.224.30.0 has an RDNS record of 119-224-30-0.callplus.net.nz.
However, if I was to try to traceroute to 119-224-30-0.callplus.net.nz, it won't get anywhere (since 119-224-30-0 is not a valid subdomain of callplus.net.nz)

rm *

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

hellonearthisman

1819 posts

Uber Geek
+1 received by user: 52

Trusted

#285993 30-Dec-2009 04:21

Wow that beyond my level of geekness. I've asked the question on the Slingshot forums, to see if anyone there can help. http://forums.slingshot.co.nz/viewtopic.php?f=15&t=3255

hellonearthisman

1819 posts

Uber Geek
+1 received by user: 52

Trusted

#286085 30-Dec-2009 15:32

BevinS from Slingshot replied.

Our reverse DNS does NOT have forward DNS to match this this.
I'm guessing this is what IRC will be blocking on.

How ever I see that guy IP address is in the static IP range, if he has his own domain name he could log a ticket with the help desk to have his reverse DNS changed to what he wishes.