新聞財經娛樂♬資訊 News Economy

Dear Export,

I've  shared-server account in one hosting and now I switch into unmanaged VPS account in
the same hosting company.

So at the shared-server I got one IP and
at VPS acount I got other new IP.

But when I connect ot my website after pay the VPS account, sometimes
it go to VPS'IP correctly, but sometimes, it go to the old IP of shared-server
I reported it to hosting company, they mentioned it might be due to
DNS propagation delay but it is already 4 days long, how DNS propagation is
so long. ANd they reply, you may need to change httpd.conf

So Why my website is not stable. Sometimes, I can see my expected page, sometimes, I
see the old shared-server account , suspend page I mean the old account is suspended

When I try to inconfig/flushdns, but it doesn't help at all
and when I try to ping mysite.com, it report VPS IP bit the content of webpage
is still the old shared-account page. Why

I aks other users to test it at Hong Kong side, all users is getting the same unstable on
my website. At HongKong side, I get unstable webpage, sometimes new VPS page
and sometimes old acount webpage, WHy ?

They just reply me at US side, my website display correct content page and capture image
to let me see. I talked to them. I mean the website is unstable

Please advise
DUncan

8524 is the number of minutes for the TTL. it's 5+ days before the DNS will complete propagation. As someone above me said: it's a DNS issue.

.htaccess files are hidden on a server...
(the . prefix makes them "hidden"...)

ls -la

will show them if they are there.
And they are placed in the directory they are supposed to protect/configure.


Also ipconfig/flushdns only flushes your local cacheon you local system, not all intermediate caches with providers.

Try the dig tool (domain information groper)
dig +trace your.domain.name
or
dig +showsearch your.domain.name

should give more info.
These should be done local, not on the server.
You may need to find a dig version for windows, don't know if it is there by default, or even if get installed).

it sounds much more like DNS than a problem on the VPS

perhaps your DNS hosting company has a DNS server that your updated address has not propagated to ?

DNS works with TTL in the entries on the server.
all intermediate servers (between any client and your DNS) may retain the RR (dns resourse record) for TTL seconds in the cache. [ no need to ask the parent to get an answer.]
If the TTL counter (decremented every second when in cache or at client systems) reached 0 the record drops from the cache.

So it boils down to how long were the original TTL in the RR's.
86400 seconds = 1 day.
Until all caches are cleared from the old records someone may get the wrong answer.
[ you normaly reduce the TTL 10 10 minutes >original TTL seconds before you cut-over
so this unstable period is only a few minites, after succesfull cut-over you restore it to the original TTL ].

Then you may have code in your cgi scripting, redirecting to some hardcoded address.
or in the apache httpd.conf found mostly in (/etc/httpd   or /etc/apache) directories.
of some .htaccess file


you need to search your config for it.