View Full Version : ROM10x suspended?
I just looked at the WHOIS info to see if they changed name servers and tha tis the reason why we can't reach them but now. At the end of the results you see this:
Domain Name: ROM10X.COM
Registrant:
Rom10x.com
Rom10x.com (snags204@hotmail.com)
100 Continental Dr.
Newark
Deleware,19713
US
Tel. +302.4541500
Creation Date: 12-Jun-2005
Expiration Date: 12-Jun-2007
Domain servers in listed order:
ns11.rom10x.net
ns10.rom10x.net
ns9.rom10x.net
ns8.rom10x.net
Administrative Contact:
Rom10x.com
Rom10x.com (snags204@hotmail.com)
100 Continental Dr.
Newark
Deleware,19713
US
Tel. +302.4541500
Status:SUSPENDED
Note: This Domain Name is Suspended. In this status the domain name is
InActive and will not function.
ANyone has any idea why is it suspended? I find it a strange coincidence that a day or two after there are posts about informants and there is a thread at hashhu by an alleged insider about how they combat piracy and rom10x falls off the face of the Earth??? I saw Snags taunt and tease on his forum and now they are gone?
I hope it is just the usual server crash, hack, problem and they will be back up soon.
mili
skinerd
03-10-2007, 08:24 AM
I just logged on there a minute ago, no problem??
OK saw sonething weird, you can see http://rom10x.com/ but not http://www.rom10x.com/ so it is a missconfigured Apache server. Why the hell does it not resolve though is beyond me.
mili
Stockwell_Day
03-10-2007, 08:36 AM
I just got using both links
Yeah it is working now. THey must have been screwing around wiht the server.
mili
Yeah it is working now. THey must have been screwing around wiht the server.
mili
Snaggs explained what happened, surprised how quick this event can unfold! :-(
hotrodder1039
03-11-2007, 02:06 AM
Yeah it is working now. THey must have been screwing around wiht the server.
mili
he said it was problems with the dns....
Phottoman
03-11-2007, 04:39 AM
copy and paste from rom10x
'Well today has been a fun one around here,
someone decided to put in a complaint about the info under our dns and due to the e-mail isuses i have been having at this site i did not get the complaint.. well the dns got suspended and we have been faxing and dealing with this all day.
Sorry for the downtime
Snags'
great havin g it back, I for one rely on rom10x as much as here.
Photto
Bandit5906
03-11-2007, 06:00 AM
Royce has posted that several sites have been busted (hashHU amoung them)!
smilingjack
03-11-2007, 07:04 AM
hasHU has been up all day
hasHU has been up all day
That proves exactly what?
I don't know what happened but I know if they bust a site they can take over and keep it open if they want it so. Just cause something is up it means nothing IMHO. I am NOT saying they got busted just pointing out the obvious. I never read a fake news on Royce's site but it is possible someone who does not like HashHu furbished teh bad info to him. It is no secret that there is no love lost between HashHu and ROM10X. Also most likely someone complained to the registrar that the regirtration info for rom10x was invalid and one of the conditions for registering a domain name is to have real info in there hence it got suspended.
mili
smilingjack
03-11-2007, 08:07 AM
One never knows...............................
The close most of them,
but Dish may be operation any one of the sites
That proves exactly what?
I don't know what happened but I know if they bust a site they can take over and keep it open if they want it so. Just cause something is up it means nothing IMHO. I am NOT saying they got busted just pointing out the obvious. I never read a fake news on Royce's site but it is possible someone who does not like HashHu furbished teh bad info to him. It is no secret that there is no love lost between HashHu and ROM10X. Also most likely someone complained to the registrar that the regirtration info for rom10x was invalid and one of the conditions for registering a domain name is to have real info in there hence it got suspended.
mili
After what happened to them recently, I'm a little suspicious of satjunction. Any comments on this one Mili? No evidence what so ever to support my insecurity, just a feeling.
I got no clue man. I stay away from other forums, when I got time I'd rather do other things that satellite stuff reading.
mili
seaboard18
03-11-2007, 09:02 PM
I just looked at the WHOIS info to see if they changed name servers and tha tis the reason why we can't reach them but now. At the end of the results you see this:
Domain Name: ROM10X.COM
Registrant:
Rom10x.com
Rom10x.com (snags204@hotmail.com)
100 Continental Dr.
Newark
Deleware,19713
US
Tel. +302.4541500
Creation Date: 12-Jun-2005
Expiration Date: 12-Jun-2007
Domain servers in listed order:
ns11.rom10x.net
ns10.rom10x.net
ns9.rom10x.net
ns8.rom10x.net
Administrative Contact:
Rom10x.com
Rom10x.com (snags204@hotmail.com)
100 Continental Dr.
Newark
Deleware,19713
US
Tel. +302.4541500
Status:SUSPENDED
Note: This Domain Name is Suspended. In this status the domain name is
InActive and will not function.
ANyone has any idea why is it suspended? I find it a strange coincidence that a day or two after there are posts about informants and there is a thread at hashhu by an alleged insider about how they combat piracy and rom10x falls off the face of the Earth??? I saw Snags taunt and tease on his forum and now they are gone?
I hope it is just the usual server crash, hack, problem and they will be back up soon.
mili
DNS Report for rom10x.com
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.
Single Point of Failure WARNING:
Although you have at least 2 NS records, there is a chance that they may both point to the same server (one of our two tests shows them being different, the other is unsure; it appears that there are one or more firewall(s) that intercept and alter DNS packets (some versions of Linux reportedly have a built-in firewall that does this, too)), which would result in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.
NS agreement on SOA Serial # ERROR:
Your nameservers disagree as to which version of your DNS is the latest (2006112306 versus 2007021803). This is OK if you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. I will continue the report, assuming that 2007021803 is the correct serial #. The serial numbers reported by each DNS server are:
210.245.211.22: 2006112306
210.245.211.23: 2006112306
210.245.211.18: 2007021803
210.245.211.19: 2007021803
Searching for rom10x.com A record at l.root-servers.net Got referral to h.gtld-servers.net. [took 83 ms]
Searching for rom10x.com A record at h.gtld-servers.net. Got referral to ns8.rom10x.net. [took 92 ms]
Searching for rom10x.com A record at ns8.rom10x.net. Reports an answer.
Record is:
Domain Type Class TTL Answer
rom10x.com. A IN 14400 210.245.211.20
rom10x.com. A IN 14400 210.245.211.25
rom10x.com. NS IN 86400 ns10.rom10x.net.
rom10x.com. NS IN 86400 ns11.rom10x.net.
rom10x.com. NS IN 86400 ns8.rom10x.net.
rom10x.com. NS IN 86400 ns9.rom10x.net.
ns8.rom10x.net. A IN 14400 210.245.211.18
ns9.rom10x.net. A IN 14400 210.245.211.19
ns10.rom10x.net. A IN 14400 210.245.211.22
ns11.rom10x.net. A IN 14400 210.245.211.23
Looking up at ns10.rom10x.net.... Reports 2 A record(s). 330ms.
Looking up at ns11.rom10x.net.... Reports 2 A record(s). 338ms.
Looking up at ns8.rom10x.net.... Reports 2 A record(s). 323ms.
Looking up at ns9.rom10x.net.... Reports 2 A record(s). 339ms.
Average of all 4 nameservers: 332ms (plus 175ms overhead).
Score: C+
Took off 22 points for >300ms average response time.
Reverse DNS for 210.245.211.18 >>>>>>IP FOR <<<<<<<<<<<<<<<< CHANGES TO ROM10X.NET HERE>>>>>>>>>>>>>>
Location: Hong Kong [City: ]
Preparation:
The reverse DNS entry for an IP is found by reversing the IP, adding it to "in-addr.arpa", and looking up the PTR record.
So, the reverse DNS entry for 210.245.211.18 is found by looking up the PTR record for
18.211.245.210.in-addr.arpa.
ll DNS requests start by asking the root servers, and they let us know what to do next.
See How Reverse DNS Lookups Work for more information.
How I am searching:
Asking e.root-servers.net for 18.211.245.210.in-addr.arpa PTR record:
e.root-servers.net says to go to dns1.telstra.net. (zone: 210.in-addr.arpa.)
Asking dns1.telstra.net. for 18.211.245.210.in-addr.arpa PTR record:
dns1.telstra.net [203.50.5.200] says to go to dns2.nwtgigalink.com. (zone: 211.245.210.in-addr.arpa.)
Asking dns2.nwtgigalink.com. for 18.211.245.210.in-addr.arpa PTR record: Reports rom102.rom10x.net. [from 203.98.129.9]
Answer:
210.245.211.18 PTR record: rom102.rom10x.net. [TTL 3600s] [A=210.245.211.18]
To see the reverse DNS traversal, to make sure that all DNS servers are reporting the correct results, you can Click Here.
WHOIS results for rom10x.net
Generated by www.DNSstuff.com
Registrar: DIRECT INFORMATION PVT LTD D/B/A PUBLICDOMAINREGISTRY.COM
Status: ok
Dates: Created 10-sep-2005 Updated 23-may-2006 Expires 10-sep-2007
DNS Servers: NS8.ROM10X.NET NS9.ROM10X.NET NS10.ROM10X.NET NS11.ROM10X.NET
I was referred to whois.PublicDomainRegistry.com; I'm looking it up there.
WHOIS results for rom10x.net
Domain Name: ROM10X.NET
Registrant:
Rom10x.com
Rom10x.com *********@hotmail.com)
100 Continental Dr.
Newark
Deleware,19713
US
Tel. +302.4541500
Creation Date: 10-Sep-2005
Expiration Date: 10-Sep-2007
Domain servers in listed order:
ns11.rom10x.net
ns10.rom10x.net
ns9.rom10x.net
ns8.rom10x.net
Administrative Contact:
Rom10x.com
Rom10x.com *********@hotmail.com)
100 Continental Dr.
Newark
Deleware,19713
US
Tel. +302.4541500
Technical Contact:
Rom10x.com
Rom10x.com *********@hotmail.com)
100 Continental Dr.
Newark
Deleware,19713
US
Tel. +302.4541500
Billing Contact:
Rom10x.com
Rom10x.com *********@hotmail.com)
100 Continental Dr.
Newark
Deleware,19713
US
Tel. +302.4541500
Status:ACTIVE
DNS Report for rom10x.net
Parent PASS Missing Direct Parent check OK.
Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:
ns10.rom10x.net. [210.245.211.22] [TTL=172800] [HK]
ns11.rom10x.net. [210.245.211.23] [TTL=172800] [HK]
ns8.rom10x.net. [210.245.211.18] [TTL=172800] [HK]
ns9.rom10x.net. [210.245.211.19] [TTL=172800] [HK]
[These were obtained from b.gtld-servers.net]
PASS Parent nameservers have your nameservers listed OK.
When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
PASS Glue at parent nameservers OK
The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
PASS DNS servers have A records OK.
All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records.
NS INFO NS records at your nameservers Your NS records at your nameservers are:
[None of your nameservers returned your NS records; they could be down or unreachable, or could all be lame nameservers]
PASS Open DNS servers OK.
Your DNS servers do not announce that they are open DNS servers. Although there is a slight chance that they really are open DNS servers, this is very unlikely. Open DNS servers increase the chances that of cache poisoning, can degrade performance of your DNS, and can cause your DNS servers to be used in an attack (so it is good that your DNS servers do not appear to be open DNS servers).
PASS Mismatched glue OK.
The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.
PASS No NS A records at nameservers OK.
Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
WARN All nameservers report identical NS records WARNING:
At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed).
210.245.211.22 returns 0 answers (may be a referral)
210.245.211.23 returns 0 answers (may be a referral)
210.245.211.18 returns 0 answers (may be a referral)
210.245.211.19 returns 0 answers (may be a referral)
PASS All nameservers respond OK.
All of your nameservers listed at the parent nameservers responded.
PASS Nameserver name validity OK.
All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
PASS Number of nameservers OK.
You have 4 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
FAIL Lame nameservers ERROR:
You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
210.245.211.22
210.245.211.23
210.245.211.18
210.245.211.19
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:
ns10.rom10x.net.
ns11.rom10x.net.
ns8.rom10x.net.
ns9.rom10x.net.
PASS No CNAMEs for domain OK.
There are no CNAMEs for rom10x.net. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
PASS No NSs with CNAMEs OK.
There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
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.
PASS TCP Allowed OK. All your DNS servers allow 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
.
WARN Single Point of Failure WARNING:
Although you have at least 2 NS records, there is a chance that they may both point to the same server (one of our two tests shows them being different, the other is unsure; it appears that there are one or more firewall(s) that intercept and alter DNS packets (some versions of Linux reportedly have a built-in firewall that does this, too)), which would result in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.
INFO Nameservers versions [For security reasons, this test is limited to members]
FAIL Stealth NS record leakage Your DNS servers leak stealth information in non-NS requests:
Stealth nameservers are leaked [H.ROOT-SERVERS.net.]!
Stealth nameservers are leaked [I.ROOT-SERVERS.net.]!
Stealth nameservers are leaked [J.ROOT-SERVERS.net.]!
Stealth nameservers are leaked [K.ROOT-SERVERS.net.]!
Stealth nameservers are leaked [L.ROOT-SERVERS.net.]!
Stealth nameservers are leaked [M.ROOT-SERVERS.net.]!
Stealth nameservers are leaked [A.ROOT-SERVERS.net.]!
Stealth nameservers are leaked !
Stealth nameservers are leaked [C.ROOT-SERVERS.net.]!
Stealth nameservers are leaked [D.ROOT-SERVERS.net.]!
Stealth nameservers are leaked [E.ROOT-SERVERS.net.]!
Stealth nameservers are leaked [F.ROOT-SERVERS.net.]!
Stealth nameservers are leaked [G.ROOT-SERVERS.net.]!
This can cause some serious problems (especially if there is a TTL discrepancy). If you must have stealth NS records (NS records listed at the authoritative DNS servers, but not the parent DNS servers), you should make sure that your DNS server does not leak the stealth NS records in response to other queries.
SOA FAIL SOA Record No valid SOA record came back:
(root) is not rom10x.net.
[B]BTW - Mili. I Looked At Your Setup Too... YOU Are In Good Shape -
I think people that can understand what is going on should be able to figure out what is up with this mess. I rather not post an opinion as to the outcome of Rom10x.
smilingjack
03-11-2007, 09:51 PM
long winded again ?
seaboard18
03-11-2007, 10:21 PM
long winded again ?
I tried to make it as brief as possible Jack. It appears that the registrar has locked down the name rom10x.com. There are several reasons why this can happen. The provider could have something to do with it through legal channels. Hackers could also be one of the reasons. One thing for sure, rom10x.com is trying disparately to keep the site resolved to rom10x.com through DNS records that could be spoofed. Its even possible that rom10x.com has been taken over by someone else. If it were law enforcement, I doubt that they would have the domain name suspended by the registrar because they would want the peeps to think its business as usual. As you can see, there are many reasons to consider. It could be that its just a sloppy mess that needs fixing by someone who understands how to do it. Its a wait and see thing at this point. I do have other opinions but I rather not post them now.
According to what you posted, it looks to me like rom10x is based in the US. Is that about right seaboard?
seaboard18
03-12-2007, 12:13 AM
According to what you posted, it looks to me like rom10x is based in the US. Is that about right seaboard?
The domain name is registered in the U.S. but the server is in Hong Kong. The problem is that registrar is bound by United States Law, so if the provider pushes the issue, a federal court here would have jurisdiction and could shut down the domain name if found to be in violation of United States Law.
However, the IP address is issued by the hosting company in China, which means that the site could still be accessed by that number but not by rom10x.com. If a federal court were to order the site to be closed, it would be up to the Chinese government as to what would happen to the IP address. Under these circumstances, I think the hosting company would comply with the United States Government and shut down that IP address.
It appears that Rom10x decided to use there own DNS server, using an IP block under .NET. Once Rom10x.net is also blocked then that is the end game. They have no more access to the DNS records. At that point, they might as well through in the towel or they could re-emerage under a new name. If this winds up in Federal Court, they all may goto jail, so I think if worse comes to worse, they would just cut there losses and run, if they can.
Its unusual for someone in this type of business to use information that would bind them to United States Jurisdiction. They were not thinking very well at the time.
There is no way it is the law type doing this if anyone but they do have serious problems with hackers who try everything left and right to disrupt that site. I am curious as to why actions by hackers would result in a domain name lock down?
mili
seaboard18
03-12-2007, 03:28 AM
There is no way it is the law type doing this if anyone but they do have serious problems with hackers who try everything left and right to disrupt that site. I am curious as to why actions by hackers would result in a domain name lock down?
mili
Mili, that is not how site owners handle a hacking incident. If you think so, you are really misinformed. Dish Network is the only people that would gain from the site being disrupted.
skinerd
03-12-2007, 03:56 AM
Mili, that is not how site owners handle a hacking incident. If you think so, you are really misinformed. Dish Network is the only people that would gain from the site being disrupted.
Not so, there is the "revenge" factor involved too.....there are some folks that don't like the admin over there.....same as when this site was hit by DDNS attacks......some people just like to hit sites for odd reasons......
seaboard18
03-12-2007, 04:16 AM
Not so, there is the "revenge" factor involved too.....there are some folks that don't like the admin over there.....same as when this site was hit by DDNS attacks......some people just like to hit sites for odd reasons......
Disrupting DNS could take up to 48 hours and a request has to be made to the Registrar. It can take up to 48 hours to re-propagate once the Registrar turns it back on. If you are a site owner and you have a hacking problem, its best to pull the plug from the wall, not stop DNS.
Back in the day, poisoning DNS records worked well for high jacking a domain name for awhile. That would not allow you to hack the server. It would allow you to take the traffic that the site generated. That could be worth money depending on the type of business you are in. I have not heard of anyone being re-directed from Rom10x since this first started to be an issue. Rom10x owners do know the cause though, you can be sure of that bit of information.
It really looks like a survival thing to me. I spent way to much time on this anyway, so whatever it is, I'm sure we will find out someday. Rom10x would be a real great loss to all of us. I hope whatever the problem is, it gets worked out.
The provider could have something to do with it through legal channels. Hackers could also be one of the reasons.
This is why I asked you what would hackers have to do with his surrent DNS problems???
mili
skinerd
03-12-2007, 06:56 AM
I was not suggesting DNS attack, only that it was done against here, there are other methods a hacker could use to disrupt a guy.
I was disputing the statement that only the provider would have something to gain.
I came under DoDOS attack in 2004 January and that was done by major assholes not any provider. Was not fun. DNS attacks are usually used to hijack websites redirecting traffic to a third party. Even if they hijacked ROM10x they'd need a complete copy of their FTP structure AND a current DBASE to masquarade as the real thing. I don't get it how and why they use a DNS server for rom10x.NET for resolving rom10x.COM and this being a possible result of WHAT?
I can handle tech explanation please explain it to me.
mili
seaboard18
03-12-2007, 07:36 AM
This is why I asked you what would hackers have to do with his surrent DNS problems???
mili
Many people have repeatedly blamed Rom10x problems on hackers every time the site has went down, more than a few minutes. However it would be possible for hackers to gain access to sensitive information and turn off DNS through online access to the Registrar. That can't be ruled out when one speculates about the problem. That is why I included hackers as a possible reason in that post.
I take it that you mean current DNS problems.
seaboard18
03-12-2007, 08:13 AM
I came under DoDOS attack in 2004 January and that was done by major assholes not any provider. Was not fun. DNS attacks are usually used to hijack websites redirecting traffic to a third party. Even if they hijacked ROM10x they'd need a complete copy of their FTP structure AND a current DBASE to masquarade as the real thing. I don't get it how and why they use a DNS server for rom10x.NET for resolving rom10x.COM and this being a possible result of WHAT?
I can handle tech explanation please explain it to me.
mili
There ISP may require that they provide the DNS service. Domains that are Networks generally provide hosting for other domains, so they may need to run a DNS server if they sell hosting to other people.
I don't really see much in that block of IP's.
210.245.211.1 : not resolved
210.245.211.2 : not resolved
210.245.211.3 : not resolved
210.245.211.4 : not resolved
210.245.211.5 : romlox.romlox.net (.NET | Network)
210.245.211.6 : not resolved
210.245.211.7 : not resolved
210.245.211.8 : not resolved
210.245.211.9 : not resolved
210.245.211.10 : not resolved
210.245.211.11 : not resolved
210.245.211.12 : not resolved
210.245.211.13 : not resolved
210.245.211.14 : not resolved
210.245.211.15 : not resolved
210.245.211.16 : horai.ladyjapan.com (.COM | US Commercial)
210.245.211.17 : not resolved
210.245.211.18 : rom102.rom10x.net (.NET | Network)
210.245.211.19 : not resolved
210.245.211.20 : not resolved
210.245.211.21 : not resolved
210.245.211.22 : not resolved
210.245.211.23 : not resolved
210.245.211.24 : not resolved
210.245.211.25 : not resolved
210.245.211.26 : not resolved
210.245.211.27 : not resolved
210.245.211.28 : not resolved
210.245.211.29 : not resolved
210.245.211.30 : not resolved
210.245.211.31 : not resolved
210.245.211.32 : not resolved
210.245.211.33 : not resolved
210.245.211.34 : not resolved
210.245.211.35 : not resolved
210.245.211.36 : not resolved
210.245.211.37 : not resolved
210.245.211.38 : not resolved
210.245.211.39 : not resolved
210.245.211.40 : not resolved
The DNS Servers are Missing..
FAIL Lame nameservers ERROR:
You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
210.245.211.22
210.245.211.23
210.245.211.18
210.245.211.19
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:
ns10.rom10x.net.
ns11.rom10x.net.
ns8.rom10x.net.
ns9.rom10x.net.
They must be hidden someplace. Else Rom10x.com would resolve . I'm sure I can find them in time.
seaboard18
03-12-2007, 09:03 AM
I was not suggesting DNS attack, only that it was done against here, there are other methods a hacker could use to disrupt a guy.
I was disputing the statement that only the provider would have something to gain.
If you are Dish Network, your worst adversary is Rom10x, whose aim is to prevent Dish Network, the users of the cryptosystem, from achieving their goal. If you are Rom10x, your worst nightmare is Dish Network's legal team. A DSS site becomes an adversary only if they can present a colossal threat so great to the provider that the provider runs out of options, in which case they have to resort to legal alternatives. Rom10x has assembled the best coders/hackers in the history of DSS cryptosystem burglary to acheive this goal. Shutting down a DSS site is not a particularly hard problem if you are the provider and your cryptosystem is in jeopardy.
The question is will Rom10x revive its self once they fall? The chances are slim to none. The coders/hackers will move on and so will the owners and members. The provider will secure his system and in a few months, it begins again. Underground hacks may become avalable to other DSS sites in time. FTA will continue to prosper because they are powerful entities in the DSS community. They sell legitimate equipment and they have the resources needed to stave off the providers attempt to kill there webstes.
If they got info to change DNS settings I think Snags would have the clue to change their Domain Control Panel password and lock the name server. I agree on the FTA assessment in your above post BUT it is a fact that they started going after FTA end users that they can comfortably show hacked their FTA receivers and they have "visited" HashHu's owner Lance (not a bust) it is said on satscams and put pressure on him. If I had to volunteer I'd say they are trying to connect coders to the manufacturers of FTA equipment. If they can prove that the manufacturers of FTA receivers pay coders to support their receivers they can then for sure sue manufacturers into oblivion and deem such units illegal to own. Now honestly what percentage of FTA recievers sold out there you think are unmodified? I'd put that number to the high one tenths of a percent. :)
mili
seaboard18
03-12-2007, 05:13 PM
Lock down DNS with these tips
DNS servers will respond to any query for a zone for which they have authority. To keep your internal network structure hidden from the outside world, always configure a split namespace, which basically means that one DNS server holds your internal DNS infrastructure, and another DNS server contains your public or Internet DNS infrastructure. By blocking external users from accessing your internal DNS servers, you can prevent disclosure of non-public internal resources.
If you want more info about how to do this, check here. I did a c|p on this to get it right.
htxp://articles.techrepublic.com.com/5100-1009-6118191.html
vBulletin® v3.7.0, Copyright ©2000-2009, Jelsoft Enterprises Ltd.