Hi, any DNS wizards, please advice me.

I have been asking to my previous hosting service provider to delete my domain record from their name server, but they don't.
Domain transfer itself was successfully completed. Who-is and all other name servers reply correct answer.

If they don't fix this problem, all people under their service can not find my domain, so they are not able to send me mails. I have another domain still under their service. In fact, I can not send mail from that domain, never arrived and never returned.

My question is... Where should I report my problem to force the provider fix it? I wonder if there is any organization has right to watch, warn or even order to fix these problems. I hope there must be something to do before bring this case to a court. Please advice me what I should do.

Thank you.

qollx,

There are no Internet organizations that have the authority to go to an ISP and force them to change their DNS. Your best solution is to have your attorney step in and send them a cease and desist order.

most webhosting companies are not ISP's so therefore this isnt an issue, if your host was an ISP as well and wont remove it see if they will update it to your current settings.

Steve

Keeg,

qollx statement:

"If they don't fix this problem, all people under their service can not find my domain, so they are not able to send me mails. I have another domain still under their service. In fact, I can not send mail from that domain, never arrived and never returned. "


- leads one to believe that this is actually an issue and appears to be so in this case. If it is obstructing his service in anyway and the webhosting company or ISP that is causing the problem isn't willing to mitigate, a cease and desist order is in order. A "cease and desist order" is not a go directly to jail card or an I'm going to sue card (although some may react that way when receiving one). However, it is a firm request to mitigate a situation that is creating a denial of service on this level.

It's just business, Keeg. nothing personal. whoever is runnig the nameservice needs to clean up the crumbs that are create a problem for this man.

Thank you valkaryn and Keeg. I appreciate your advice.

- General interest

It's very interesting that there is no organization watching DNS. There are a lot of organizations for making rules and receipt registration but maintaining it. It's all up to each administrator's skill and honesty. Is it true? And can we keep this way?
I'm afraid that it must be very easy to configure a name server with wrong information on some purpose. I mean, hiding the target domain from users to obstruct and damage his business. Also, I wonder how many domain owners really check their previous name server after they move to other hosting service provider (HSP). There would be many domains that can not be access from some people, without owner's recognition.

- My personal problem.

Fortunately, most of these problems are not caused by evil intention, I really hope so. The reason why my previous HSP don't correct this problem is mostly because they do not use appropriate engineers to investigate this case.
The first answer from them was replying a copy of who-is look up result and reporting that they don't see problem. The second answer was a copy of nslookup result which probably used other name server, no commend line typing was shown, and reporting same words.
After my detailed explanation of the problem and instruction for usage of DNS tools, they finally understand what I was talking about and edit their name server. However, the edit was not perfect. They delete NS, MX and other records but left SOA record. It means that the zone file is still under named directory and named.conf or named.boot was untouched. Now they keep saying the problem was fixed.
I made call to a HSP which bought my previous HSP this morning. Their recognition was same as the previous HSP. I sent nslookup result for checking but have not gotten their reply after that.

I think it's time to disclose the HSPs name. It's DIGIWEB and INTERLIANT. It's not for blaming them yet. I need experts agree me and help me.
My domain is easterntrend.com. Bellow is nslookup result on ns.digiweb.com.
-----------------------------------------------------------
$ nslookup - ns.digiweb.com
Default Server: ns.digiweb.com
Address: 216.205.137.2

> set type=any
> easterntrend.com
Server: ns.digiweb.com
Address: 216.205.137.2

Non-authoritative answer:
easterntrend.com
origin = ns.digiweb.com
mail addr = support.digiweb.com
serial = 2001082001
refresh = 21600 (6H)
retry = 3600 (1H)
expire = 3600000 (5w6d16h)
minimum ttl = 900 (15M)
-----------------------------------------------------------
It should be fixed like this.
-----------------------------------------------------------
$ nslookup - ns1.interliant.com
Default Server: ns1.interliant.com
Address: 198.64.193.25

> set type=any
> easterntrend.com
Server: ns1.interliant.com
Address: 198.64.193.25

Non-authoritative answer:
easterntrend.com nameserver = NS1.SBCWEBHOST.NET
easterntrend.com nameserver = NS2.SBCWEBHOST.NET
easterntrend.com internet address = 216.65.199.10

Authoritative answers can be found from:
easterntrend.com nameserver = NS1.SBCWEBHOST.NET
easterntrend.com nameserver = NS2.SBCWEBHOST.NET
NS1.SBCWEBHOST.NET internet address = 216.65.199.10
NS2.SBCWEBHOST.NET internet address = 216.65.199.11
-----------------------------------------------------------

Please let me hear your idea and help me please.

Thank you.

qollx,

Try getting to a manager with a clue. The problem obviously has not been taken care of as they indicated. Did they remember to bump the nameserver after the changes?

Valkaryn,

Thank you for advice. I will try to contact to the manager. I know now who is good and who is bad in their support team.
I am not sure if they reboot named program, but they suppose to refresh it quite often.
I guess their named configuration files are generated by data from their customer information database, because DIGIWEB was a huge hosting service provider. Probably no one is arrowed to touch the raw files. If the program has bag, it may cause their unorganized management.
Also I found their support staffs are using NT workstation. I'm not familiar with NT. Does NT nslookup tool work exactly like Unix's one? Also I guess they are using some integrated network management application on NT to configure it. It may also cause problems, if it does not work as it should.
Thank you anyway, I will try some more.

Thank you.

I had a similar situation a while back and although the web host was very cooperative and cleaned up their dns, the server that my site used to be on could not route mail properly.

It drove the webhost crazy and it was never fixed undil they upgraded their servers and had to do a format and fresh install.

Thank you for information Brav0.

If my problem is similar to yours, there must be many people have same problem. Did it happen on DIGIWEB server or another hosting service?

INTERLIANT moved all DIGIWEB users to new platform this May. Before this migration, they announced that they would change name server to asv4.webhosting.Interliant.com, but it seems they gave up this plan.

Thank you all.