PLESK DNS and GoDaddy

Yes that's the real domain name.
The server isn't down.., I can log on through PLESK, and I can hit the preview of the site.
So you're saying that the custom name server on GoDaddy is wrong?

AIL All nameservers respond ERROR: Some of your nameservers listed at the parent nameservers did not respond. The ones that did not respond are:

72.167.15.85 Error=Port Unreachable
72.167.15.85 Error=Port Unreachable


Note: If you are running a Watchguard Firebox with DNS Proxy enabled, there may be a bug causing port numbers get mixed up -- if this is the case, you can contact Watchguard to see if they have a fix.
PASS Nameserver name validity OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
FAIL Number of nameservers ERROR: You have 2 nameservers, but both are on the same IP! This is not a valid setup. You are required to have at least 2 nameservers, per RFC 1035 section 2.2.
PASS Lame nameservers OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
PASS Missing (stealth) nameservers OK. All 0 of your nameservers (as reported by your nameservers) are also listed at the parent servers.
FAIL Missing nameservers 2 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns2.metrosoccerclub.org.
ns1.metrosoccerclub.org.
 
PASS No CNAMEs for domain OK. There are no CNAMEs for metrosoccerclub.org. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
FAIL No NSs with CNAMEs ERROR: I checked to see if there were any CNAMEs for your NS records (there shouldn't be), but they all timed out. Note: This test checks with our local DNS server (since the NS record hostnames may not be handled by your DNS server), and therefore may be cached.
WARN Nameservers on separate class C's WARNING: All of your nameservers (listed at the parent nameservers) are in the same Class C (technically, /24) address space, which means that they are probably at the same physical location. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.
PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
WARN TCP Allowed WARNING: One or more of your DNS servers does not accept TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems. The problem servers are:

72.167.15.85: Error [Connection refused (10061)]. 72.167.15.85: Error [Connection refused (10061)].  
FAIL Single Point of Failure ERROR: Although you have at least 2 NS records, they both point to the same server, resulting in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.  
INFO Nameservers versions Your nameservers have the following versions:

72.167.15.85: No version info available (timeout on lookup). Could be tinydns 1.00 through 1.04.
72.167.15.85: No version info available (timeout on lookup). Could be tinydns 1.00 through 1.04.
 
PASS Stealth NS record leakage Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.
SOA FAIL SOA Record No valid SOA record came back:
is not metrosoccerclub.org.

OK..,
I pulled this report from the link that Chris-Dent posted.  Chris can you explain this?
Is it saying that because I'm pointed to the same IP address that's what's making it fail?  Once I put another IP address on the ns2 ptr I'll be in business?

Hey,

Is the address like 72.***.***.85 the web server? It's listed as the DNS Server for the Domain, but isn't able to answer DNS requests.

I didn't check much if it was up earlier, just whether or not the DNS portions of your domain name were functional.

Chris

The only bit on DNS Report you really need to worry about for now is this bit:


AIL All nameservers respond ERROR: Some of your nameservers listed at the parent nameservers did not respond. The ones that did not respond are:

72.167.15.85 Error=Port Unreachable
72.167.15.85 Error=Port Unreachable


You need the server there to answer the requests. If that's not the right server it needs changing as soon as absolutely possible as changes to those records will take a while to filter through (varying from a few hours to a day).

One responding server there will get rid of the majority of errors shown by DNS Report.

Chris

That is the right server.., why can't it answer?
Is it something in PLESK?
Have I missed a setting?

I'm not familiar with PLESK so I can't answer directly for that. There are two possibilities (as far as I can see).

Either the DNS Service isn't running (and is supposed to be), or a Firewall is blocking traffic to the DNS Server.

Chris

So I need to check IIS?
Or do I need to check the running services on the virtual server?

This is my first time working with a virtual dedicated server and I can't tell you how frustrated it's making me.  I've never run into this kind of trouble before.

Not IIS, no. That gives you the Web Server part and a few other bits, but not DNS.

I'm not familiar with PLESK, does it give you a full Windows OS there? If so, open Start, Programs, Administrative Tools then DNS (which is hopefully there). That's what we need to be running and configured.

However, if the configuration for that is elsewhere then I'm not quite sure where to tell you to look :-\

Chris

The DNS service was not running.

I tried to ping the domain name, metrosoccerclub.org, but got the same response.  Could not resolve name.

How long will it take to be able to see if that worked?

If you're started the service, pretty much right away if that's the problem.

However, I'm still not able to connect to DNS unfortunately.

Could you verify that your server IP corresponds to ns1.metrosoccerclub.org or ns2.metrosoccerclub.org? Both are listing on 72.167.15.185.

If that IP Address isn't your server we're looking in the wrong place.

Chris

ns1.metrosoccerclub.org is set to 72.167.15.85
ns2.metrosoccerclub.org is set to 72.167.29.109

I set those on GoDaddy and have put them in PLESK as that.
I created both NS and A type.

However the website wasn't uploaded through PLESK.., it was sent up through RDP.  Will that make a difference?

No, don't worry about the Website itself for now, until DNS is up that won't really matter.

Do you have any official support for this at all? It would make sense to ask them as they will be able to answer much more specific questions for your environment than I can.

Chris

They, GoDaddy, are wanting to charge $1k for the vDed support....

Needless to say that isn't in the budget.

Ouch, that's certainly quite excessive. However, I'm at a bit of a loss how you can configure the DNS service on there at the moment (if it's not just the Windows Service).

Chris

OK..,

I went to the services in PLESK and found that the DNS Server showed that it wasn't started or disabled.  I clicked on the Start Service icon, but the indicator icon didn't change.  It did however tell me that the event was successful.

From what I can tell I can't start the DNS server from within PLESK.

Any help here would be greatly appreciated.., I'm pulling my hair out on this one.

You're not going to believe this....

The problem was with GoDaddy not properly configuring the PLESK config file.

Thanks for your help....

That was good of them.... I'm glad you got to the bottom of it in the end.

Chris