More .us Domain Problems? 39
possible asks: "My .us domain registrations supposedly went through on April 27th 2002. However, even though register.com's .us FAQ states that you can use their Domain Manager to edit addresses, aliases, MX records, and SOA's for your .us domain, I have not been able to do ANYTHING yet. When I called their technical support on May 1st, they basically said "This is Neustar's fault, in the meantime we have to do everything manually." So I had them set up my MX and name records over the phone. 6 days later, I'm still unable to resolve my domains. Today I called register.com again they told me 'Somehow your zone file got corrupted, you have to realize that .us domains are a new thing and it's not going smoothly for many people.' Some of my friends are having similar .us problems with different registrars. Is anyone else having problems with their .us domains? Does anyone know what the underlying problem is?"
Do you need to ask? (Score:3, Funny)
Capitalism.
Re:Do you need to ask? (Score:1)
Amen. There was NO REASON to dismantle .us - the last bastion of The Good Old Internet Community and make it into another corporate annex. It's like demolishing the old vacant lot that was at the 280/101 interchange in San Francisco to put up a mall. There is no reason to have a mall - it's the same shit in that mall that's in every other mall. At the vacant lot there were swap meets every week where hundreds of one of a kind items traded hands.
To HELL with verisign, neustar, and most egregious, ICANN.
-Lx?
Sounds rough (Score:1, Interesting)
On a completely side note, why does each article get posted only to its server? This one is on ask.slashdot.org, but normally it would be available from both ask./.org and slashdot.org (no prefix).
Considering that one can't get back to the real
Re:Sounds rough (Score:2)
I'm not him, but I can think of several good reasons, starting with the fact that practically all the useful .com namespace is either in use or being squatted, by Network Associates if by no one else.
Actually it's been doing that on and off for several weeks now. No idea what the problem is.
.us Zone Configuration (Score:2, Insightful)
What is Neustar's problem?
Re:.us Zone Configuration (Score:2)
It's not Neustar having problems. My changes put in at Verisign (I have one .us domain there) go through quickly just fine. But the changes at register.com (also one .us domain there) are not going through at all. I think register.com is having problesm deploying their software. They did offer to update manually, but so far it hasn't been done correctly.
Re:.us Zone Configuration (Score:2, Informative)
You'll need to escape your dots, like this: :s/\.com/\.us/g Otherwise you might replace somethings you didn't want to, like "thecommons.com" -> "th.usmons.us". Also, you'll probably want to do it on every line, so something like this :%s/\.com/\.us/g
or
g/\.com/s/\.com/\.us/g would be better.
Re:.us Zone Configuration (Score:2)
Reasons why .us is sucking (Score:1)
a new thing? (Score:4, Informative)
Maybe what the should have said is "a new thing for us". I remember several years ago registering a
I can't imagine that things have gotten any better since then, even with a new company handling
In their attempt to monopolize as much domain registration as possible, VeriSign/NSI has managed to cause a lot more damage for
Re:a new thing? (Score:1)
Re:a new thing? (Score:2)
Plus, according to this site [doc.gov] on November 2, 2000 Amendment 21 [doc.gov] was added to the NSI Cooperative Agreement. It wasn't unter October, 2001 [slashdot.org] that Neustar was granted control of US-DOM, with the transition completed in [slashdot.org] November, 2001 [neustar.com].
Although, the arguably worst part of the time VeriSign/NSI was controlling
not really new (Score:2, Informative)
Sounds like this whole thing has been a fiasco (Score:2, Insightful)
But what can we expect on the domain-registering front nowadays? Look at verisign and bulkregister. Instead of spending money upgrading quality and customer service, they're going to use it to run sleazy campaigns and sue the living daylights out of each other.
Its got to go back to the non-profit organization model. This sorta stuff really stinks.
If it's any consolation... (Score:2)
.
Re:If it's any consolation... (Score:2)
All the 1 letter and 2 letter domains are reserved, as are many others. I found the list somewhere (forgot where, but I'm sure it's somewhere at Neustar) and put it online here [ipal.us] (compressed text is here [ipal.us]).
ehh? (Score:2)
Once your nameserver records are in place, how well your DNS works is dependant on whoever provides your DNS, not the registry.
I have a number of
Justin
Re:ehh? (Score:1)
Re:ehh? (Score:2)
The root servers delegate the .us zone to the Neustar servers, which are:
Recursive lookup starts a one of the servers in root-servers.net, and goes to the above, then finally to your registered DNS servers (yours, or you ISP's, or the registrar's).
Now there are still some problems:
I registered 2 domains in .us, one via register.com [register.com] and the other via Verisign/Netsol [netsol.com]. I, too, had trouble getting my DNS servers set up via register.com. They finally said they could do it manually, but then they goofed that up by entering them wrong after giving me an excuse that some of them had no IPs (they did ... but they weren't the ones I wanted used, though). OTOH, with Verisign, I was able to change my DNS servers just fine, and it went through in 6 hours (while everyone says it can take 24-72 hours). My only beef with Verisign is the limit of 4 DNS servers. I've had another person also tell me eNom is working OK for them.
Re:ehh? (Score:2)
That doesn't appear to be the case. All three of the IP addresses you listed are in separate
Some of your other points appear to be quite valid, though.
Re:ehh? (Score:2)
That can be done by simple BGP trickery. I know, because I've done it before. What they have is redundant paths through those 3 upstreams, which is certainly better than none. But it just doesn't say one way or the other what locations these are in. Can one fire take out all of .us because 3 pipes converge in the same building? The thing is, we don't know.
Re:ehh? (Score:2)
Yeah, but there are about 10 people a month looking up .us domains, vs 10,000,000 a day looking up .com domains.
Suggests, to the naïve, but certainly does not require. Traceroute to 4.2.49.1 and then to 4.2.49.2. Same subnet (unless you use mask 255.255.255.255), and yet they're 3000 miles apart.
Troubles with NS changes (Score:1)
Still, they're working great as long as I set up the records on the name servers I originally used...
register.com apparently just sucks. (Score:1)
Re:register.com apparently just sucks. (Score:2)
I really don't understand why the poster thinks that the registrar has anything to do with zone files and MX records. Those things are the responsibility of your DNS provider. Since people other than register.com are able to successfully provide DNS service for .us domains I'd be inclined to blame register.com rather than Neustar or some vast unnamed internet conspiracy.
Neustar and .us propagation (Score:1)
When Neustar took over they, first off, sent us pages and pages of documents to fill out. The big technical change is that they required us to allow zone updates to be pushed from their servers. My guess is that they want to be able to bill people for an aurora.il.us registration and have it entered automatically that way, bypassing the possible human failure point that is introduced under the old system when a request was mailed. That pretty much would have prevented anyone from billing for changes because the "registrar" would not be able to guarantee that the changes were entered. This thought is backed up by a lot of the questions in the aforementioned paperwork asking indirectly about if we would expect a cut if someone started changing for registrations.
So the problems reported may be that the person running the nameserver simply did not change the ACL allowing Neustar to push down changes. Now remember that there were two types of
Just thought I would share this lest anyone think that Neustar were the first to screw up the
--chris
.us is not new. (Score:1)
register.com passing the blame (Score:1)
What's the problem? (Score:1)
If you register the name through RCOM, then their job is to take your money ('natch), and send the info to Neulevel, who *only* needs to know who your nameservers are.
[Although, Neulevel's requirement that any nameservers for a
From then on, your zone file and MX settings, etc., are handled by your DNS provider (i.e. whoever runs your nameservers). If RCOM said your "zone file got corrupted", it sounds like they are covering up for some other incompetence.
Sure the