brendanrtg

Well-Known Member
Oct 4, 2006
311
0
166
This is a very weird problem and we have never experience anything like this before when we move sites but this time round, we got unlucky and everything we tried failed to get the ghost domain to show.

Here's what happened:

We moved a domain over from another server, named: 52gao.com

NS is pointed correctly to our server and all IPs assgined to it are pointed correctly, including our NS, as can be seen as follows;

http://www.dnsstuff.com/tools/dnstime.ch?name=52gao.com&type=SOA

The domain is setup on our server on IP 67.159.4.53, which is also correctly pointed via the NS which can be seen as follows:

http://www.dnsstuff.com/tools/dnstime.ch?name=52gao.com&type=A

1. We checked the zones files for the domain and all entires are looking good and correct.
2. We checked httpd.conf and entries are also good.
3. We did the following too:
root@viper [/scripts]# /scripts/fixnamed
root@viper [/scripts]# /scripts/fixndc
root@viper [/scripts]# /scripts/fixrndc

No matter what we do, the domain wont show up nor even via its own dedicated IP (which is pingable).

http://www.dnsstuff.com/tools/ping.ch?ip=52gao.com

Can any experts out there please advise?
 

Lyttek

Well-Known Member
Jan 2, 2004
775
5
168
I'm seeing 67.159.4.46 as your IP, not 67.159.4.53

NS2 isn't responding, but NS1 is...
 

brendanrtg

Well-Known Member
Oct 4, 2006
311
0
166
We tweaked the IPs around but basically the error remains no matter where we shove this domain to.
 

jayh38

Well-Known Member
Mar 3, 2006
1,212
0
166
You have some screwey dns going on there. I would first start at the
registrar and delete all the created name servers and on the old host
server, remove all records as well.

Then after it is all clean, register your name server and you will probably
be all set.
 

brendanrtg

Well-Known Member
Oct 4, 2006
311
0
166
Thanks for your feedback.

It turns out the Dc guys screwed and binded the said IP addresses range to other serves instead of ours. lol