Results 1 to 14 of 14
-
05-01-2007, 05:09 PM #1WHT Addict
- Join Date
- Jan 2006
- Posts
- 110
I'm totally stuck... what can cause this problem ? My support doesn't have the answer
Hello !
More then 1 month i'm having problems with my domainname.
I even had to register another domainname according to my host to make it work.
But still, now it isn't working yet... i really don't know what to do.
The following problem occurs:
When my clients try to change their nameservers of their domainname (.NL domainname, they are always VERY VERY strict that EVERYTHING is in order... one fail and they don't accept the nameserver change ).
They always get back the following error:
Errors=1, Warnings=1, Informational=0
** Summary: REJECTED crs.nl.
Some problems need to be fixed:
- Not everything could be tested, because of (technical) failures.
** Full check report:
* general reports
Warning: all specified name servers are on sub-net 64.34.205.0/24
* primary name server "ns1.fsws.info." [BROKEN]
Failure: name server cannot be reached: query timed out
* secondary name server "ns2.fsws.info."
Info: name server looks correctly configured.
#### fail
My support has looked in it multiple times with several tech's but they don't seem to get it to work...
This is a huge problem for me, because i cannot accept new clients because they cannot register the domainname with my hosting services
Some extra info:
I rent a VPS and 2 domainnames are attached to it fsws.nl and fsws.info
Could some one help me with this ?
Thanks soo much !!
-
05-01-2007, 05:20 PM #2Web Hosting Master
- Join Date
- Jul 2005
- Location
- Mexico
- Posts
- 1,762
well, maybe you have no glue, not really ns and a dns in your nameservers.
check dnsreport.com and dnsstuff.comEach registrar is a tool. Not all Tools are for the same thing
-
05-01-2007, 05:22 PM #3WHT Addict
- Join Date
- Jan 2006
- Posts
- 110
Thanks for your reply !
My support already did that...
Only 1 fail on it, but they say it's not neccessary to fix it
http://www.dnsstuff.com/tools/dnsrep...main=fsws.info
-
05-01-2007, 05:44 PM #4Temporarily Suspended
- Join Date
- Mar 2005
- Location
- Texas, USA
- Posts
- 133
The domain that you are having issues with is fsws.info, correct?
If so the domain appear to be working and configured properly.
-
05-01-2007, 08:10 PM #5Web Hosting Evangelist
- Join Date
- Jun 2005
- Posts
- 531
I just tried to query your nameservers and it appears that there is no zone data for crs.nl.
Make sure that both nameservers are configured to be authoritative for the zone(s) in question.
-
05-02-2007, 05:07 AM #6WHT Addict
- Join Date
- Jan 2006
- Posts
- 110
Hi there !
Thanks all for your replies, here is some more detailed information to clear everything up:
My domainnames are FSWS.nl AND FSWS.info
Both are working "normally".
Only the problem is with the Nameservers.
They seem to be broken, well NS1 seems according to the error my clients get when they try to change the nameservers to mine.
CRS.nl is a client his domainname, it is correct that the nameservers are not the same as mine, because they can't change them to mine nameservers because they always get the error i mentioned before.
So, in short, the problem is that I and my support do not know how to solve the error my clients always get when they try to change theire nameservers to mine (ns1.fsws.info and ns2.fsws.info)
Errors=1, Warnings=1, Informational=0
** Summary: REJECTED crs.nl.
Some problems need to be fixed:
- Not everything could be tested, because of (technical) failures.
** Full check report:
* general reports
Warning: all specified name servers are on sub-net 64.34.205.0/24
* primary name server "ns1.fsws.info." [BROKEN]
Failure: name server cannot be reached: query timed out
* secondary name server "ns2.fsws.info."
Info: name server looks correctly configured.
#### fail
I hope this clears things up
Thanks
-
05-02-2007, 05:14 AM #7Hey, whats your uptime ?
- Join Date
- Mar 2004
- Location
- Tokyo / Japan
- Posts
- 492
Some registrars have certain procedures how to "register" or change the IP of a nameserver (if that is what you are trying to do). It is possible that you will have to ask the domains registrar how they handle IP updates on nameservers.
You cant just enter the nameserver in case you also have a new IP. You first have to update the IP for the nameserver or register it and then set it for your domain.
Note also that f.e for German DE domains both nameservers have to be in separate C-class networks !!
I hope you can make any sense of what I wrote above ;-)__--- Nils Valentin ---
☆★☆ Speedtest One: Tokyo / Japan ☆★☆ / Feedback
☆★☆ Speedtest Two: Tokyo / Japan ☆★☆ / Feedback
-
05-02-2007, 01:07 PM #8Web Hosting Evangelist
- Join Date
- Jun 2005
- Posts
- 531
As I said above, your nameservers have no data for the crs.nl domain. Fix that and you should be okay.
When you think you've corrected the problem you can use the shell commands
host -t ANY crs.nl ns1.fsws.info
and
host -t ANY crs.nl ns2.fsws.info
to see if you've corrected them.
-
05-02-2007, 02:07 PM #9WHT Addict
- Join Date
- Jan 2006
- Posts
- 110
Okay ! Thanks again for you all your answers !
I forwarded them to my support, because i have bought a fully managed VPS, so i demand that my host fix those error's for me then... you guys even helped them out
I will keep you guys updated
Thanks
-
05-06-2007, 12:12 PM #10WHT Addict
- Join Date
- Jan 2006
- Posts
- 110
it is only getting worse
Errors=7, Warnings=5, Informational=1
** Summary: REJECTED crs.nl.
Some problems need to be fixed:
- Some of your name servers cannot be used (are broken).
- In total, 5 configuration errors where found.
** Full check report:
* general reports
Warning: all specified name servers are on sub-net 64.34.205.0/24
* primary name server "ns1.fsws.info."
Error: specified name server is not listed as NS record.
Error: specified name server is not listed as NS record.
Warning: "localhost.crs.nl." not defined.
crs.nl. 2560 IN SOA ns2.crs.nl.info.
hostmaster.crs.nl.
(1178404693 4H33M4S 34M8S
12D3H16M16S 42M40S)
Error: the MNAME in SOA says "ns2.crs.nl.info." is the primary
name server.
Hint: serial in SOA often formatted as YYYYMMDDnn.
crs.nl. 259200 IN NS ns1.crs.nl.info.
Warning: hidden name server "ns1.crs.nl.info." never used for
first contact.
crs.nl. 259200 IN NS ns2.crs.nl.info.
Error: extra name server "ns2.crs.nl.info." listed via IP
64.34.205.15
Warning: name server "ns2.crs.nl.info." listed twice.
crs.nl. 259200 IN NS ns2.crs.nl.info.
Warning: hidden name server "ns2.crs.nl.info." never used for
first contact.
* secondary name server "ns1.crs.nl.info." [BROKEN] [HIDDEN]
Broken: name server "ns1.crs.nl.info." not found in your zone.
* secondary name server "ns2.crs.nl.info." [BROKEN] [HIDDEN]
Broken: name server "ns2.crs.nl.info." not found in your zone.
* secondary name server "ns2.fsws.info."
crs.nl. 259200 IN NS ns2.crs.nl.info.
Error: extra name server "ns2.crs.nl.info." listed via IP
64.34.205.16
#### fail
-
05-06-2007, 12:33 PM #11Web Hosting Evangelist
- Join Date
- Jun 2005
- Posts
- 531
Have you considered changing to a provider that actually knows what they're doing?
Have they seen the output? Correcting the errors is trivial.
-
05-06-2007, 02:00 PM #12WHT Addict
- Join Date
- Jan 2006
- Posts
- 110
Well, i still have confidence that they will fix it, but if it isn't fixed before Mid May, i will consider it indeed... i'm sorry to say that for my host, good guys,they have already enough trouble on their heads... but hey the service has to work, and 2 months is enough time to fix it
-
05-06-2007, 09:45 PM #13Web Hosting Evangelist
- Join Date
- Jun 2005
- Posts
- 531
Ignoring the fact that they should have done it correctly the first time, when they tried the second time they should have taken the time to check their configuration. If they take the time to read the error report, it's quite clear as to what the issues are. They should be able to correct it and verify that it's corrected in a matter of ten or so minutes. Good luck with it.
-
05-08-2007, 11:18 AM #14Aspiring Evangelist
- Join Date
- Nov 2006
- Posts
- 369
I do not understand what hosting company you are using if their support cannot fix a simple issue with the nameserver settings, change your host and try to find a real tech support