I was trying to check a WHOIS record on a domain that was registered through ResellOne, to see what how it looks.

However there's just an error being displayed



Just wondering if this is a known problem or not.

Thanks!
Ben

Thanks, this is a known issue and the dev. team is working on it.

Just wanted to check Glad it's known about

Is there an ETA on when the WHOIS server will be operational?

I do not at this time have an ETA on this, this particular issue, is apparently having to be investigated quite extensively, and the developement people are working on it. As soon as we have a resolution we will post it.

From a traceroute, it seems the whois server is hosted in canada, so is it the tucows "development people" who are working on the resellone whois server? I'm sure it will work out fine, but they sure don't seem as fast as the EV1 development people

This is an issue that is having to be investigated by our developement team, at this time I do not have an ETA on this, this particular issue, is apparently having to be investigated quite extensively, and the developement people are working on it. As soon as we have a resolution we will post it.

How come the traceroute to whois.resellone.net is so odd looking?

Are those ***-hop routers just not configured to respond to ICMP?

3 gphou-66-98-240-10.ev1.net (66.98.240.10) 0.374 ms 0.342 ms 0.362 ms
4 g0-3.na21.b015619-0.iah01.atlas.cogentco.com (38.112.25.21) 0.869 ms 4.411 ms 0.925 ms
5 g0-1.core01.iah01.atlas.cogentco.com (66.28.64.61) 2.277 ms 1.271 ms 1.214 ms
6 p13-0.core01.mci01.atlas.cogentco.com (66.28.4.106) 15.628 ms 15.659 ms 15.585 ms
7 p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34) 27.109 ms 26.926 ms 27.265 ms
8 p5-0.core01.yyz01.atlas.cogentco.com (66.28.4.214) 40.818 ms 40.620 ms 40.736 ms
9 g0-1.na01.b011152-0.yyz01.atlas.cogentco.com (38.112.35.130) 42.013 ms 43.199 ms 41.449 ms
10 IBMCanada.demarc.cogentco.com (38.112.20.66) 43.785 ms 43.411 ms 43.665 ms
11 * * *
12 * * *
13 129.33.183.72 (129.33.183.72) 43.573 ms 43.719 ms 43.496 ms
14 * * *
15 * * *
16 radware-osrs1.tucows.com (216.40.33.70) 60.208 ms 49.055 ms 46.061 ms
17 whoiscentral.net (216.40.33.56) 44.309 ms 45.081 ms 44.717 ms

1 69.5.4.gw.futurequest.net (69.5.4.1) 0.953 ms 0.786 ms 1.372 ms
2 brdr-01-1 (69.5.31.254) 1.586 ms 1.450 ms 1.233 ms
3 se-3-0-5.hsa1.Orlando1.Level3.net (63.209.98.69) 2.365 ms 2.058 ms 3.212 ms
4 ge-6-2-0.mp1.Orlando1.Level3.net (209.247.11.37) 5.497 ms 3.171 ms 3.786 ms
5 as-1-0.bbr1.Washington1.Level3.net (4.68.128.201) 25.990 ms 24.161 ms ae-0-0.bbr2.Washington1.Level3.net (4.68.128.210) 24.467 ms
6 so-6-0-0.edge2.Washington1.Level3.net (64.159.3.62) 25.170 ms so-7-0-0.edge2.Washington1.Level3.net (64.159.3.66) 24.468 ms 24.547 ms
7 cogent-level3-oc48.Washington1.Level3.net (4.68.127.10) 29.209 ms 29.960 ms 30.201 ms
8 p11-0.core02.dca01.atlas.cogentco.com (154.54.2.197) 30.351 ms 31.310 ms 34.158 ms
9 p6-0.core01.jfk02.atlas.cogentco.com (66.28.4.82) 39.377 ms 37.298 ms 36.899 ms
10 p5-0.core01.bos01.atlas.cogentco.com (66.28.4.117) 41.963 ms 42.888 ms 41.561 ms
11 p14-0.core01.yyz01.atlas.cogentco.com (66.28.4.218) 62.827 ms 61.646 ms 60.403 ms
12 g0-1.na01.b011152-0.yyz01.atlas.cogentco.com (38.112.35.130) 62.440 ms 62.380 ms 62.816 ms
13 IBMCanada.demarc.cogentco.com (38.112.20.70) 48.794 ms 48.295 ms 50.126 ms
14 * * *
15 * * *
16 129.33.183.72 (129.33.183.72) 48.230 ms 55.687 ms 50.913 ms
17 * * *
18 * * *
19 radware-osrs1.tucows.com (216.40.33.70) 50.867 ms 56.533 ms 53.342 ms
20 whoiscentral.net (216.40.33.56) 48.684 ms 49.370 ms 49.330 ms

Any news on getting the resellone.net whois server up and running? How about just setting a new one up from scratch if the old one has problems that cannot be diagnosed? Or is the thought that it's not a problem, just a cosmetic issue to have the fatal server error kicked back upon query?

I think there are many things wrong with resellone. IMO it's a floundering mess.

I've transferred in several domains and everything but the whois server has worked great for me. Have not attempted to use the api yet but that will come. I do hope they get the whois server online as it looks bad to have a client look and see "fatal server error" though -- especially from a company with thousands and thousands of servers.

maybe it got bird flu?

I was able to access the whois for several domain names this morning at http://resellone.net/Whois/Default.aspx, and it worked fine. I just wanted to keep you all updated.

No it doesn't, try a domain name registered with resellone not just any domain name.

Thanks very much for the followup. However, trying with one of the .com domain names that I transferred to resellone.net a few weeks ago, I still am still getting:

[Querying whois.internic.net]
[Redirected to whois.resellone.net]
[Querying whois.resellone.net]
[whois.resellone.net]
Fatal Server Error. Try again later

And the web interface you linked above results in simply
"Fatal Server Error. Try again later"

(above was for a command line whois domain.com query from my server here at EV1)

The web whois interface does seem to work fine for domains not registered with resellone.net

This is really a strange one, I am sending all the information that I have gathered regarding this issue to the development team, and Brooke, so that we can get this resolved as quickly as possible. Thanks for all of your input everyone.

For these issues please email them with a screen shot of the error to domainmanager@resellone.net. Thanks!

This is really starting to suck! This issue was reported over a month ago! http://forums.ev1servers.net/showthread.ph...8044#post368044

Working as I type this - appears to be fixed at last

Thank you EV1.

Indeed it is. Thanks

Thanks, we are working hard to get any issues that arise dealt with.

WHOIS server is working now.
It is yet to have reseller information (Registration Service Provider:) mentioned in it and hope they are aware and working on it.

I have sent this one to developement, as well. I hope to have an answer soon. Thanks for all the input.