New client to server matrix and slowly (hopefully) moving all servers from ev1 to you guys I was alerted by a reseller of mine about a issue with many failed checks when going to dnsreport.com.

Items such as:



This also shows up for MX and WWW records. After calling tech support they had no clue about it and was stumped as much as I was. The I saw this post at cpanel:

http://forums.cpanel.net/showthread.php?s=...ighlight=public

It appears server matrix needs to contact dnsreports. I have check all my entries and records on the server and all are properly set right. Domains seem to be functioning just fine but the fact this returns many errors is a upset to both me and my clients.


Can anything be done?

It seems that the whois record at ARIN isn't complete or filled out properly. So when an application like this checks to see who owns the IP block, it appears that ARIN owns the block, not ThePlanet or SM -- thus the program thinks it's still unassigned. It's nothing to fret over, I assure you that your IP address is indeed public.

PS - ARIN is the American organization who assigns IP addresses.

...
If it is really a problem at ARIN regarding these IP's showing as unallocated and not simply a problem at dnsreport, as a hosting or server customer I would definitely worry about it too. If there really is some problem with ARIN's records for the IP's, what if they got allocated them to someone else :shock:

I just checked my IP's and they show up fine at ARIN though as registered to the Planet.

This is my major concern but as I said tech support was as clueless as I was to fix the issue.

Never had this issue at ev1..hmmmmm


:shock: :shock:

So as any other company forums I assume this one will be ignored by employees?

I had exactly the same probllme but it's nothing to worry about. Basically when your use new ips ARIN take a bit too long to update their database which is used by dnsreport.com scripts. I have actually confirmed this.

Hi,

How long did it take for your ip's to be mark as public ?



Regards,
Garry

I only noticed this with my new server, so my ip's are still marked as non-public. I should expect another month

Yer, I got the same issue/problems with my first server that is with TP, thought I post and ask, thanks for the reply

Regards,
Garry

As I said, the ip's not showing as public does not affect the funtionality of your server in any way. The report from dnsreport.com is therefore inaccuarte. (Just in case you didn't know this already).

Best of luck with your new server

Also I noticed when I do a dns report I see something wrong with the glue, is this also to do with the IP's being private ?

They bot the same TLD I am checking and I still get this error:

Glue at parent nameservers WARNING.

The parent servers (I checked with e.gtld-servers.net.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.

Same with my new ns's. I wouldn't worry about that. I believe this message will go away once the ips show as public (well, according to ARIN) so the root servers send out the ip's as well as hostnames.

One more thing Garry, If you check domains like microsof.com in dnsreport.com you'll see a few of those yellow warnings. If you want to feel better check your domain in http://www.checkdns.net (must type www).

My server is fully functional and there's no dns issues. All domains can send an receive emails and are fully public and available dispite all those yellow and red warnings.

Cheers

Garry, that error that you are receiving is derived that your name servers have a different TLD then the domain that you lookedup though DNSReport.com. Simply put if your name servers are ns1.domain.com and ns2.domain.com and you lookup domain.org you will receive that. It's a problem with the Hiarchy of how different TLD's lookup the root servers. This is nothing that you should worry about, it just causes one extra DNS lookup to find the actual A Record each time the lookup is cached.

The only way around this would be to make a name server (not just a pointer to another name server) for each TLD that you host on the server.

Cheers,
Robby

Hi,

The domain is the same as the ns, all .com's and get that problem, never had this problem before I came here where the IP's are marked as private, all settings been doubled checked.

Regards,
Garry