another website is using my nameservers - HELP !

[VTEC]

Hi,

so as above another website is using my nameservers. The NS are set-up with/on my domain which is currently in my GoDaddy account.

What can I do about this ? Can I make his website crash or at least disable it somehow ?

Please advise,

Thanks,

V

[south]

You mean you are Hosting their dns? Or at least their site is pointing to your dns server? I'm not sure I understand your question completely. If you think it's intentionally malicious, point their site to 127.0.0.1, or a porn site. Or forward it to a good cause. If you think it's an honest mistake, send them an email. dns normally puts very little load on a server, and the traffic is usually very efficient because it uses udp rather than tcp, so unless it's a very high traffic site, it probably won't have much affect on you.

[VTEC]

thanks South

yes, their site is pointing to my dns server

basically if the domain name xxxx.com is on my account and it's the same one as the NS ns1.xxxx.com / ns2.xxxx.com they are using all what I can do is forward this domain somewhere through my GD account, but how will this affect the guy who is using my domain as his NS ? will it also point his website to whatever (forwarding) I set on my GD account if he is only using the NS ?

thanks again

[south]

Ok. Still not totally clear to me, maybe I need more coffee.

But;

There are a lot of "ifs"

In a nutshell:

Depending on what nameservers hisdomain.com is set to use, some possible scenarios:

If hisdomain.com is set to use yourdomain.com as it's nameservers, for hisdomain.com to work, you would need to be running actual nameservers on yourdomian.com. Otherwise, hisdomain.com should give a 404 (not resolve). If you ARE running a dns server on your domain, you would need to create records for hisdomain to resolve. Otherwise it should also give a 404 for hisdomain.com. If you ARE runnign nameservers on your domain, and you have created records for hisdomain.com, you would have total control of where his traffic goes. Keep in mind, that is assuming a lot. First, it assumes he is setting hisdomain.com's nameservers as your root domain name. It also assumes you have created records for his name. At least an A record. Now, if hisdomain.com is pointing to ns1.yourdomain.com, ns2.yourdomain.com, and you have no A or cname records for ns1 and/or ns2, OR no name servers running on those addresses (ns1.yourdomain.com &/or ns2.yourdomain.com), then hisdomain.com should not resolve, and give a 404 also.

So.... for hisdomain.com to actually resolve (correctly), several conditions must be met. First, you have to have actual nameservers setup and running on yourdomain.com's site. yourdomain.com must not be parked. You must have dns records setup on your server for hisdomain.com. If any of these are not true, hisdomain.com will not resolve. The only exception I could see would be that if your domain is parked, the A record might be pointing to a parking company that provides dns services on all their servers, across all addresses, and then the domain would probably just point to that parking company.

[Adam Dicker]

If they are stupid enough to use your dns servers, add dnsrecords to your servers and point his traffic to one of your sites.

This has happened to me many times, people buy names and forget to change servers so I benefitted from the traffic.

-=DCG=-

[cursal]

If they are stupid enough to use your dns servers, add dnsrecords to your servers and point his traffic to one of your sites.

This has happened to me many times, people buy names and forget to change servers so I benefitted from the traffic.

-=DCG=-

Yep.
I have several parked names that I sold and the new owners still haven't changed the dns...years later and I'm still collecting on the revenue.

[Acro]

By using your DNS that has no effect on you unless you create records on your server for that domain so that it resolves.

[lilian]

why do they use your name servers. there are many sites offer free name servers