Slashdot Mirror
Old Webhosting Providers Who Hijack DNS?
linzeal
asks: "Oneworld
Hosting my old webhosting provider keeps hijacking my DNS records
for my website Anarchists for Life
and pointing it at another customer's website.
I have talked to the owner of the IP block as well as my old web host
a multitude of times to no avail. My new webhosting provider
Trilucid has been very helpful
and has even suggested legal action. Does anyone here have an idea
on how to solve this problem short of that?"
How are they "hijacking" your DNS records?
Who's your registrar?? How can they update the DNS records for _your_ domain? Are you listed as the zone/technical contact?
If you gave them absolute control of the domain, then there's almost nothing you can do.
If you are the contact for the domain, update it with your registrar and make sure they're _NOT_ listed as the tech. contact!
Who's your DNS provider? Are they causing the problems?
Whois on networksolutions.com
Registrant:
Chris Welsh
2792 W. Jasper Dr.
Chandler, Az 85224
US
Registrar: Dotster (http://www.dotster.com)
Domain Name: ANARCHSFORLIFE.ORG
Created on: 06-SEP-00
Expires on: 06-SEP-02
Last Updated on: 26-OCT-00
Administrative Contact:
Welsh, Chris koat@disinfo.net
2792 W. Jasper Dr
Chandler, Az 85224
US
602-254-6398
Technical Contact:
Welsh, Chris koat@disinfo.net
2792 W. Jasper Dr
Chandler, Az 85224
US
602-254-6398
Domain servers in listed order:
NS3.TOMORROW2.NET
NS4.TOMORROW2.NET
NS2.TOMORROW2.NET
NS1.TOMORROW2.NET
I want to delete my account but Slashdot doesn't allow it.
you should contact a lawyer and have him send them a letter threatening legal action if they don't stop. For them to send a letter may cost you a couple hundred $$, but may be an easy way. If they continue, and you need to take them to court, you will definitely win and they will end up footing the bill for your legal costs. Unless, you still owe them money and that's why they are doing this.... Of course, you can just keep calling and emailing them daily.... then hourly... then every 5 or 10 minutes.... eventually they will get the point that you won't leave them alone till the resolve your problem.
Cyberbite Networks - Web Hosting, Dedicated Servers & Colocati
You shouldn't really rely on a company who you are in contract with to provide you DNS service. When you leave, they have no incentive to keep pointing records for you or even make it easy for you to move.
;-)
It's much easier to use a third party DNS provider who is either really cheap or free.
There are quite a few cheap ones out there and a couple free ones, but of course, I won't cool my own.
-davidu
# Hack the planet, it's important.
The simple way to resolve this is by changing the DNS server where your domains point to. Currently, it points to tomorrow2.net which have 4 of them listed.
But from the cursory checking of that domain, it seems to belong to neither party unless it does belong to oneworldhosting.com, but not sure about it. But you can change it to point to your new hosting provider DNS so it will updates it properly and use the much higher serial number to override the old one that is floating around which they might consider the valid DNS which it isn't. It happens a few times and it is not much of an issue if you change the serial number to be higher than the old one that existed on the old DNS Server.
-- Amazing how the Internet still humms along.... -- Dispite all the flaws of Micro$oft in their software!
Switch registrars: to networklsoultions.com, formerly internic.net. They were awarded the contract that internic once held. Which Verisign now holds. Manually remove all previus DNS Host records that you have information about. They are still there even when they tell you "this is all that is showing up". Host with a large provider. Verio, Verisign, ATT, SWBELL, Etc.
To save you all five seconds...
.COM, .NET, .ORG, .EDU domains and
Trying "anarchsforlife.org."
HEADER opcode: QUERY, status: NOERROR, id: 23812
flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 4
QUESTION SECTION:
anarchsforlife.org. IN ANY
ANSWER SECTION:
anarchsforlife.org. 172800 IN NS NS1.TOMORROW2.NET.
anarchsforlife.org. 172800 IN NS NS2.TOMORROW2.NET.
anarchsforlife.org. 172800 IN NS NS3.TOMORROW2.NET.
anarchsforlife.org. 172800 IN NS NS4.TOMORROW2.NET.
AUTHORITY SECTION:
anarchsforlife.org. 172800 IN NS NS1.TOMORROW2.NET.
anarchsforlife.org. 172800 IN NS NS2.TOMORROW2.NET.
anarchsforlife.org. 172800 IN NS NS3.TOMORROW2.NET.
anarchsforlife.org. 172800 IN NS NS4.TOMORROW2.NET.
ADDITIONAL SECTION:
NS1.TOMORROW2.NET. 172800 IN A 128.241.194.20
NS2.TOMORROW2.NET. 172800 IN A 128.241.194.21
NS3.TOMORROW2.NET. 172800 IN A 130.94.173.110
NS4.TOMORROW2.NET. 172800 IN A 130.94.173.111
Received 241 bytes from 198.142.0.51#53 in 352 ms
[mikem@nailbox mikem]$ whois anarchsforlife.org
[whois.crsnic.net]
Whois Server Version 1.3
Domain Name: ANARCHSFORLIFE.ORG
Registrar: DOTSTER, INC.
Whois Server: whois.dotster.com
Referral URL: http://www.dotster.com/help/whois
Name Server: NS1.TOMORROW2.NET
Name Server: NS2.TOMORROW2.NET
Name Server: NS3.TOMORROW2.NET
Name Server: NS4.TOMORROW2.NET
Updated Date: 18-dec-2001
>>> Last update of whois database: Wed, 26 Dec 2001 17:04:50 EST
The Registry database contains ONLY
Registrars.
[whois.dotster.com]
Registrant:
Chris Welsh
2792 W. Jasper Dr.
Chandler, Az 85224
US
Registrar: Dotster (http://www.dotster.com)
Domain Name: ANARCHSFORLIFE.ORG
Created on: 06-SEP-00
Expires on: 06-SEP-02
Last Updated on: 26-OCT-00
Administrative Contact:
Welsh, Chris koat@disinfo.net
2792 W. Jasper Dr
Chandler, Az 85224
US
602-254-6398
Technical Contact:
Welsh, Chris koat@disinfo.net
2792 W. Jasper Dr
Chandler, Az 85224
US
602-254-6398
Domain servers in listed order:
NS3.TOMORROW2.NET
NS4.TOMORROW2.NET
NS2.TOMORROW2.NET
NS1.TOMORROW2.NET
Register a domain name at www.dotster.com
End of Whois Information
can a DNS misconfiguration become "hijacking". Good work there Cliff, glad to see you're on top if it.
If that's not bad enough, only about two guys out of 20 had any clue what was going on in the first place. Get a lawyer?...that's rich...how 'bout a hostmaster with a clue?
His zone record was fucked up, but it's hardly hijacking.
The problem is that your old isp has your dns records in their system, but their web servers don't know about your domain (thus pointing it to the default or first one). You need to make sure that all the root servers point to the correct dns and ask your old isp to remove your zone from their configuation files (on masters and slaves).