Attack of the Disney DVD

[deaxe]

Can some have a look at www.nzafmp.org and tell me if my site has been over run by a site about disney dvd? For some reason my site has been replaced by it, from where I'm looking from anyways. It' s a bit freaky.

thanks


Gary

ps the ip address works but this sucks

[mike7727]

I get the New Zealand Armed Forces . . . (not disney)

[deaxe]

thanks mike,

I've tried 3 different machines from my location and they are all sending me to some disney page unless I use the ip weird eh?


Gary

[dkadave]

i get the New Zealand Armed Forces site!

[lookout]

That's what I see too.

But since from a past thread it appeared you had recently been moved to a new server, you might be seeing domain resolution flip-flopping due to conflicting MX records at Jaguar (old and new). I'd have tech support check into that if I were you. Other possibilities exist, but this one seems the most likely cause to me in this case.

[lookout]

Another thread today made me wonder if you were talking about this site: www.ultimatedisney.com, apparently one of your neighbors on Jaguar's Dragonfire server.

I do see what looks like a IP mixup between your sites. A "dig" reveals you both with A addresses of 66.227.58.204, which currently is resolving to the ultimatedisney.com site. They are also resolving at another IP address. I suspect that's wrong. It looks like your respective IPs should be:

www.nzafmp.org = 66.227.19.247

www.ultimatedisney.com = 66.227.17.213

Looks like the 66.227.58.204 IP is causing others on your server some grief too. Have support check it out.

[deaxe]

Hi Lookout and everyone else

Have updated my ticket as it seems to be an ongoing thing, thanks for the help, I freak out a bit at the thought of our volunteers being unable to access the site.

Yes ultimatedisney is the site in question and you are right about the ip addresses I guess that's why if i use the ip address to access the site it works while the name doesn't..

cheers

Gary

I wasn't aware I was on dragonfire I was told that i was on neo.

[Vin DSL]

That Neo server is goofy all right!

Get it? Hahahahahahaha! Every hear the one about Neutron?

Neutron walks into a bar and says, "I'd like a beer."

The bartender promptly serves him up a beer.

"How much will that be?" asks Neutron.

"For you?" replies the bartender, "no charge"

Get it? Hahahahahahaha!

Take my wife - please!

Sorry! Anyone want a Red Dog?

[lookout]

Neutron was nonplussed, I'm sure.

Deaxe, I'm getting the reference to Dragonfire from this entry in each of the "digs" I performed on the sites in question.

Responsible person: root@dragonfire.nocdirect.com

Typically that indicates the server name here, although it isn't foolproof. No mention of Neo anywhere in the record. If memory serves me, both dragonfire.nocdirect.com and neo.nocdirect.com were pulling up pages of their own a couple of weeks ago, suggesting (but not necessarily confirming) the existance of both servers. Now only the Neo one seems to work (just a basic page with the word Neo on it, some servers here put up an Apache "It worked" page).

Also, Neo is listed on Jaguar's network status page, but I've never seen Dragonfire there. It seems possible Dragonfire may have been an earlier name for Neo (or vice versa), rather than its own server as the "dig" results suggest. If it really IS one of Jaguar's client servers, ask tech support to add Dragonfire to their network status page. While there, they could also fix the missing service indicator lights for Neo. Having them put up a basic dragonfire.nocdirect.com page would also be good. It provides a quick means of comparing your site's web availability versus your hosting server's.

[jason]

You wouldn't happen to be on the v100 plan, would you? If that's the case, you share an IP address with other v100 users on your server and Apache becoes responsible for serving up the correct site based on the HTTP_HOST header that your browser sends. (Some old browsers didn't support HTTP_HOST, but all current and recent browsers (probably going back to the 2.0's) do, so this shouldn't be a problem.)

If you are on the v100 plan, then the issue lies in Apache's conf files and not the DNS. If you are on any other plan then your DNS settings are messed up.

--Jason

[lookout]

The DNS settings look ok; I checked. Though the order of the primary and secondary nameservers are reversed between the two sites, which might make a difference. But it does appear more of an IP mixup with the account configuration at Jaguar. I doubt that Jaguar mean to assign two separate IPs to ultimatedisney.com, one of which is also appearing in deaxe's dig record.

[lookout]

Gary, I'm pm-ing you the dig results. There's a reference to the other ultimatedisney.com IP in it. Pass it on to the techs.

[deaxe]

Thanks I'll pass it on, tech support are blaming my web browsers cache even after I sent the last lot of ip's that I got from my own tracert, even when I checked it on 3 different machines using 3 different o/s.

It seems to be an itermittant problem as everything has been ok since early or late last night depending on your timezone.

I notice in the network stats page on the main jag account page that neo doesn't have any network indicator graphics, I wonder if this is an indication of neo's state of mind?


I'm on a v200 plan sorry I don't know the difference between that and the v100

cheers

Gary

[jason]

The only difference between the v100 and any of the others (besides the disk space and bandwidth alotments) is that the v100 doesn't come with a unique IP address, which can be the cause of things like this occasionally. I was just asking because I wanted to point out that it could have been that all of the sites in question were supposed to have the same IP and that the error was coming from something else. Now that I know you aren't on the v100, it is safe to say that this is, in deed, a DNS problem.

--Jason

[lookout]

Originally posted by jason
Now that I know you aren't on the v100, it is safe to say that this is, in deed, a DNS problem.

I think some clarification is in order. When I said they looked OK, I was referring to the ones that show up Gary's whois record. Those show Gary using

NS.JAGUARPC.NET
NS2.JAGUARPC.NET

as nameservers, the same pair that JaguarPC uses for their own site.

There's an account configuration problem with DNS on the Jaguar end. The 66.227.58.204 IP that I flagged earlier shouldn't be appearing in the dig results for Gary's site. It shows a clear link to the other site.