What do you guys see when you go to digitalsmackdown.com or www.digitalsmackdown.com Half the world see's our default hosting page and the other half see's this guys web site. All the DNS records are how they should be. This isn't a new domain transfer. He has been with us for a month now. What could the problem be????

Doesn't appear to be a DNS problem. When I go to digitalsmackdown.com, I see your default hosting page, and when I go to www.digitalsmackdown.com, I see his site. They both resolve to the same IP address, so it looks like an Apache misconfiguration.

the only other thing it might be is your just missing the cname or A record or what ever it is for the www instance of it.

doublecheck your dns records.

theres something screwy in there :)

the first .92 ip goes to the other guys webpage, the .168 goes to your hosting webpage.

> host -a digitalsmackdown.com ns3.echolima.com
Using domain server:
Name: ns3.echolima.com
Address: 216.40.247.167
Aliases:

digitalsmackdown.com 86400 IN A 216.40.247.92



but when you do..

> nslookup digitalsmackdown.com
Server: localhost
Address: 127.0.0.1

Non-authoritative answer:
Name: digitalsmackdown.com
Address: 216.40.247.168


unless you have changed the zone files in the last few hours, then it will take time to propogate..

Hi,


At first, do you differ http:// and http://www. in your config or not?

Second, please (if it possible) print here they dns records. It might flush a problem


Regards

Comon people ;) I've checked the DNS over. I've tried reconfiguring Apache, still nothing. I can't figure it out. Someone said they could see it when they go to www.digitalsmackdown.com but not digitalsmackdown.com I can't see it on either and neither can my client.

I can load both addresses in my web browser and get the correct site. Looking up both addresses returns 216.40.247.92

Do your own nslookup and post what results you're getting.

I'm also getting correct site on both http:// and http://www.

Nice music ;)

May be the dns server, serving you, is not doing correct resolution? as on my home computer where I'm browsing both:

digitalsmackdown.com -> 216.40.247.92
www.digitalsmackdown.com -> 216.40.247.92

whereas on my remote system:

digitalsmackdown.com -> 216.40.247.168
www.digitalsmackdown.com -> 216.40.247.92

wait a second, now on my remote system:

digitalsmackdown.com -> 216.40.247.92
www.digitalsmackdown.com -> 216.40.247.92

Looks like you are doing something :stickout

Hope this helps :)

Whoa, something screwy IS going on...

I just tried to resolve www.digitalsmackdown.com and it resolved to 216.40.247.168 at first, but then it changed to 216.40.247.92. I queried your DNS servers and they're both returning 216.40.247.92...let me investigate further. :eek:

Originally posted by ToastyX
Whoa, something screwy IS going on...

I just tried to resolve www.digitalsmackdown.com and it resolved to 216.40.247.168 at first, but then it changed to 216.40.247.92. I queried your DNS servers and they're both returning 216.40.247.92...let me investigate further. :eek:

Sounds kinda like a "Poor man Cluster".. aka.. Round Robin DNS doesn't it.

Do you have multiple DNS entries for www.digitalsmackdown.com with different IP addresses?

just a thought...

Originally posted by raq4less


Sounds kinda like a "Poor man Cluster".. aka.. Round Robin DNS doesn't it.

Do you have multiple DNS entries for www.digitalsmackdown.com with different IP addresses?

just a thought...

That's what I also thought at first, but then I queried his DNS servers, and it wasn't showing that.

Okay, I think I got it! This IS a tough one. I just found something really weird out...

DIGITALSMACKDOWN.COM and WWW.DIGITALSMACKDOWN.COM both seem to be registered as name servers pointing to 216.40.247.168! :eek: Either the registrar or the person that registered the domain name did something really screwy, so it has nothing to do with Echolima's DNS servers.

From my experience, for registered name servers, BIND tends to return information from the TLD servers for non-cached records and information from the domain name's name servers for cached records. My ISP uses Linux and BIND. That's why I got 216.40.247.168 the first time and 216.40.247.92 each consecutive time. That's why I didn't catch it the first time. That also explains why some people are getting one IP address instead of the other.

Originally posted by ToastyX
Okay, I think I got it! This IS a tough one. I just found something really weird out...

DIGITALSMACKDOWN.COM and WWW.DIGITALSMACKDOWN.COM both seem to be registered as name servers pointing to 216.40.247.168! :eek: Either the registrar or the person that registered the domain name did something really screwy, so it has nothing to do with Echolima's DNS servers.

From my experience, for registered name servers, BIND tends to return information from the TLD servers for non-cached records and information from the domain name's name servers for cached records. My ISP uses Linux and BIND. That's why I got 216.40.247.168 the first time and 216.40.247.92 each consecutive time. That's why I didn't catch it the first time. That also explains why some people are getting one IP address instead of the other.
Hmm....good theory. So what can I do at our end to fix this?

Originally posted by netsolutions

Hmm....good theory. So what can I do at our end to fix this?

Absolutely nothing, I'm afraid. :( This appears to be a registry issue. The person that registered the domain will have to contact the registrar.

They need to ask the registrar to remove the "nameserver". Not the nameservers for domain, but the nameservers created out of the domain :D

This may be available in the control panel of registrar :)