Problems for .SC Domain Owners

[mbailey]

About a week after i bought 2 .sc domains from idotz.net for $50 each, i realized that both domains weren't being resolved sparadically throughout various parts of the internet.

So, i started investigating the issue, with the initial impression that this problem was stemming from my own dns servers.

Well, after about a half hour of checking things on my own server, i came to the conclusion that nothign was wrong there.

So, then i started looking into outside issues that may be causing the problem, and when i found the actual problem i was pretty shocked.

Here's how it breaks down


The .SC ccTLD has 3 nameservers listed in it's IANA records:

• tld1.ultradns.net
• tld2.ultradns.net
• ns1.nic.sc

But, if we run the same query at each of those nameservers, they each list only those of ultradns.net, with absolutely no mention of ns1.nic.sc .

So, i did some more digging, and i found that ns1.nic.sc returns an NXDOMAIN error on both of my .sc domains (webhost.sc and irc.sc), and the .sc domain of my friend (geeks.sc). But, those 2 ultradns.net dns servers report just fine.

Aparently, ns1.nic.sc should have been removed from the IANA records, but somewhere along the line someone forgot to remove it from the IANA records.

So now, us .sc domain owners are facing a particularly major problem. Any time a user tries to access one of our domains, there is a 1 in 3 chance that the domain will be reported as non-existant, and they won't be able to access the website.

On January 30th i filed a support ticket with the people i registered my .sc domains with - idotz.net asking what is going to be done.

On february 1st, they replied back saying that they forwarded the ticket to Afilias - the .SC and .INFO Registry.

Later that day, they replied back saying that Afilias and ultradns are looking into the issue. .

On February 2nd, i replied back saying that i'll be waiting for a response, and also inquiring if anything may be done to reimburse us customers who have been affected by this issue.

On February 5th, there still hadn't been a response, and i asked if there was an update on this issue.


There hasn't been a response from idotz.net to this day.

Tonight, ns1.nic.sc is still responding with NXDOMAIN on each of those .sc domains i have been registered with idotz.net.

 

[mbailey]

Clear your BROWSER cache. http://validator.w3.org/check?uri=http://geeks.sc responds everytime with the correct response after the www.geeks.sc request is made.

IT does work now, but that still doesn't change the fact that a dns query may be routed through ns1.nic.sc.

Glad to know your not actually a SysAdmin with their own nameserver. Try using a real Server to get your DIG responses. Here are some free public tools, http://www.kloth.net/services/dig.php or http://network-tools.com/default.asp?

A) If you wanted to insult me, you could have at least checked your grammar.
B) That command uses the nameservers that the client server is configured to use. The nameservers that this machine is using are still showing that the dns query brings up ns1.nic.sc.

The ccTLD isn't functioning? Really? Idotz has a duty to sell domains.

It's not completely functioning correctly.

By the way,

; <<>> DiG 9.1.3 <<>> @G.root-servers.net webhost.sc ANY
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48953
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 3

;; QUESTION SECTION:
;webhost.sc. IN ANY

;; AUTHORITY SECTION:
sc. 172800 IN NS TLD1.ULTRADNS.NET.
sc. 172800 IN NS TLD2.ULTRADNS.NET.
sc. 172800 IN NS NS1.NIC.sc.

;; ADDITIONAL SECTION:
TLD1.ULTRADNS.NET. 172800 IN A 204.74.112.1
TLD2.ULTRADNS.NET. 172800 IN A 204.74.113.1
NS1.NIC.sc. 172800 IN A 202.72.100.47

;; Query time: 260 msec
;; SERVER: 192.112.36.4#53(G.root-servers.net)
;; WHEN: Sat Feb 12 22:49:22 2005
;; MSG SIZE rcvd: 148

from http://www.kloth.net/services/dig.php

As an owner of a few .sc domains and an experienced admin this is a non-issue to me. Thanks for your concern and Thread mbailey however you may want to do more research before claiming that an entire domain extension isn't functing or that traffic to .sc domains is limited to 1 in 3 requests - Any time a user tries to access one of our domains, there is a 1 in 3 chance that the domain will be reported as non-existant, and they won't be able to access the website

When did i ever say that the entire TLD wasn't functioning correctly?

 

[KwelX]

How are people supposed to know that the tld isn't functioning well when there is a scare number of .sc domains out there, right now?

That command uses the nameservers that the client server is configured to use. The nameservers that this machine is using are still showing that the dns query brings up ns1.nic.sc.

Exactly. The fact that I have proven to you is that the presence of ns1.nic.sc will have NO enduser effect on traffic.

I have not attempted to insult your intelligence. I hope it did not come across that way.

 

[mbailey]

Exactly. The fact that I have proven to you is that the presence of ns1.nic.sc will have NO enduser effect on traffic.

it doesn't ?

 

[KwelX]

back to w3c talk i see.


http://kwelx.com/hhhsc.GIF <- initial request of hhh.sc

http://kwelx.com/hhhsc2.GIF <- after a www.hhh.sc request

; <<>> DiG 9.1.3 <<>> hhh.sc ANY
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37493
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;hhh.sc. IN ANY

;; ANSWER SECTION:
hhh.sc. 86400 IN NS ns1.sedoparking.com.
hhh.sc. 86400 IN NS ns2.sedoparking.com.

;; AUTHORITY SECTION:
hhh.sc. 86400 IN NS ns2.sedoparking.com.
hhh.sc. 86400 IN NS ns1.sedoparking.com.

;; ADDITIONAL SECTION:
ns1.sedoparking.com. 20356 IN A 217.160.95.94
ns2.sedoparking.com. 20356 IN A 217.160.141.42

;; Query time: 120 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Feb 12 23:33:40 2005
;; MSG SIZE rcvd: 135

==========================================================


now i will ask what experience you have with DNS and DNS Servers? all that i ask is that you simply take back the statement that .sc domain owners will see 1 out of 3 requests. your basis is way off for most of the statements and examples that you are giving here.

there is no reason to try to scare .sc owners or claim that Idotz has any duty to inform a .sc owner of anything.

now i think this Thread should be left to see if IANA or nic.sc sends any update to see why ns1.nic.sc is not responding correctly.

 

[mbailey]

http://kwelx.com/hhhsc.GIF <- initial request of hhh.sc

http://kwelx.com/hhhsc2.GIF <- after a www.hhh.sc request

It got a correct result for www.hhh.sc because it queried a nameserver other than ns1.nic.sc . It didn't resolve a hostname on the hhh.sc result because ns1.nic.sc was queried.

If you think a www. is requierd for the validator to resolve a hostname, see this: http://validator.w3.org/check?uri=http://postwhatever.com

; <<>> DiG 9.1.3 <<>> hhh.sc ANY
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37493
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;hhh.sc. IN ANY

;; ANSWER SECTION:
hhh.sc. 86400 IN NS ns1.sedoparking.com.
hhh.sc. 86400 IN NS ns2.sedoparking.com.

;; AUTHORITY SECTION:
hhh.sc. 86400 IN NS ns2.sedoparking.com.
hhh.sc. 86400 IN NS ns1.sedoparking.com.

;; ADDITIONAL SECTION:
ns1.sedoparking.com. 20356 IN A 217.160.95.94
ns2.sedoparking.com. 20356 IN A 217.160.141.42

;; Query time: 120 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Feb 12 23:33:40 2005
;; MSG SIZE rcvd: 135

include +trace in your query, you'll see ns1.nic.sc .

now i will ask what experience you have with DNS and DNS Servers? all that i ask is that you simply take back the statement that .sc domain owners will see 1 out of 3 requests. your basis is way off for most of the statements and examples that you are giving here.

It's simple. There is a 1 in 3 chance that ns1.nic.sc will be queried. This is because there are 3 root .sc ccTLD nameservers. You can see this by running dig whatever.sc +trace .

there is no reason to try to scare .sc owners or claim that Idotz has any duty to inform a .sc owner of anything.

They don't? Let's say your friend goes to the store and buys a bottle of pills, the store he bought it from is one of 3 stores in the country that sells this type of pill, and the pill is pretty much unknown in most parts of the country. About a week after taking the pills, your friend keils over and dies. The store knew that the pills would result in his death, but still chose to not tell him about it. Does that mean that the store isn't (even partially) at fault?

Tell me, where are we supposed to go for information about the .sc tld? Hell.. i'll do you one better - name 3 places that offer .sc domain registration.

now i think this Thread should be left to see if IANA or nic.sc sends any update to see why ns1.nic.sc is not responding correctly.

It's simple. The nameserver should have been removed from all dns records a long time ago.

 

[IAmAllanShore]

This has been a very informative thread... learning a ton about how all this jazz works
Also good to see the tech evolving (Partly probably due to some of the folks here).
-Allan