nox
01-18-2002, 02:16 AM
I am desperate to find the source of a domain related problem I am having which has tech people at registrars etc running for cover.. maybe someone here could help my sanity... <begging>
1. Couple of years ago I purchased a domain, let's call it 'domain.com', through a Bulk Register reseller who was also providing hosting for that domain.
2. This domain was then used to provide hosting services and two aliased name servers, ns and ns2, [vDNS] were created by the hosting company with unique IP's and all correctly registered with NetSol etc.
3. I decided to change networks and move this domain and it's name servers away from the original host. This involved changing the IP's of the name servers and updating the zonefile etc etc.
I was unable to access the domain.com records because it was in the account of a Bulk Register reseller and so to avoid the inconvenience of having to refer to the 'ex host' each time I wanted to access the domain, I transferred it to a different registrar, where it currently still is. This gives me full control over the domain and it's records.
All was well with the domain and it's DNS etc.
4. The time came, yet again, to move this domain to another network which involved the change of NS IP's and all things related. This was done without incident and things were fine for a short while UNTIL the problem started.....
The problem is that 'domain.com' intermittently resolved to the IP address on the previous network. Now, www.domain.com DID NOT do this, it was fine.. only when just domain.com was used.
5. OK you say there are some obvious reasons why this might happen.. and I agree, but I have exhausted everything and even today during a random check the problem still exists.
Here are some further details of what we checked and/or changed since the problem started..
- we completely stripped all records associated with domain.com from the server it was on, and recreated the whole shebang.. vhost, zone file, new IP's ... everything, in case there was a rogue entry somewhere which inadvertently pointed at the old network and IP.. this didn't work.
- I contacted everyone connected with the domain from it's initial registration up to date and requested that they check to see if anything could possibly be affecting the DNS in this way.. nothing
- I subsequently tried different name servers for a period just to add to the investigative experience... no difference.
- The domain is yet again on a different network and a different server, all brand new with no chance of any old config's or files included... the problem still exists.
To wind up.. I have tried to analyse the path from the browser to the domain and the same with a couple of different tracert's and whois servers and the only place I can fathom where there may be an entry with the old IP, is at the registrar, because it's happening before it get's to the current name servers and zone file... and it's still only 'domain.com' that does it, not www or any other host!!!
This has been looked at by many people who all, understandably, slide away mumbling after finding no reasonable explanation.
It is not only mind rippingly frustrating, but it restricts what I can reasonably do with this domain..
Sorry to be long winded, but I thought it would avoid posts containing basic advice for things we did already..
Somebody please help... :eek:
1. Couple of years ago I purchased a domain, let's call it 'domain.com', through a Bulk Register reseller who was also providing hosting for that domain.
2. This domain was then used to provide hosting services and two aliased name servers, ns and ns2, [vDNS] were created by the hosting company with unique IP's and all correctly registered with NetSol etc.
3. I decided to change networks and move this domain and it's name servers away from the original host. This involved changing the IP's of the name servers and updating the zonefile etc etc.
I was unable to access the domain.com records because it was in the account of a Bulk Register reseller and so to avoid the inconvenience of having to refer to the 'ex host' each time I wanted to access the domain, I transferred it to a different registrar, where it currently still is. This gives me full control over the domain and it's records.
All was well with the domain and it's DNS etc.
4. The time came, yet again, to move this domain to another network which involved the change of NS IP's and all things related. This was done without incident and things were fine for a short while UNTIL the problem started.....
The problem is that 'domain.com' intermittently resolved to the IP address on the previous network. Now, www.domain.com DID NOT do this, it was fine.. only when just domain.com was used.
5. OK you say there are some obvious reasons why this might happen.. and I agree, but I have exhausted everything and even today during a random check the problem still exists.
Here are some further details of what we checked and/or changed since the problem started..
- we completely stripped all records associated with domain.com from the server it was on, and recreated the whole shebang.. vhost, zone file, new IP's ... everything, in case there was a rogue entry somewhere which inadvertently pointed at the old network and IP.. this didn't work.
- I contacted everyone connected with the domain from it's initial registration up to date and requested that they check to see if anything could possibly be affecting the DNS in this way.. nothing
- I subsequently tried different name servers for a period just to add to the investigative experience... no difference.
- The domain is yet again on a different network and a different server, all brand new with no chance of any old config's or files included... the problem still exists.
To wind up.. I have tried to analyse the path from the browser to the domain and the same with a couple of different tracert's and whois servers and the only place I can fathom where there may be an entry with the old IP, is at the registrar, because it's happening before it get's to the current name servers and zone file... and it's still only 'domain.com' that does it, not www or any other host!!!
This has been looked at by many people who all, understandably, slide away mumbling after finding no reasonable explanation.
It is not only mind rippingly frustrating, but it restricts what I can reasonably do with this domain..
Sorry to be long winded, but I thought it would avoid posts containing basic advice for things we did already..
Somebody please help... :eek: