Thx for this very instructive response, I suck in networking issues so this
is all very appreciated.
I'll get right on it.
Regards. Janusz.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https
On Fri, Sep 30, 2011, Janusz Skonieczny wrote:
> What I meant to ask was, what have caused those servers to cache a negative
> result.
> The app.dziennik.edu.pl domain was a CNAME to ghs.google.com from the start,
> and it is set-up for a couple of months now. My other domain that have the
> same
Are all the affected users/locations using one ISP. ? I would try and
isolate where the DNS is failing, its probably one DNS server that all
of these locations use, and its having trouble for whatever reason.
Asking your users to use google's dns may be your only option. (or
possibly you could send
I don't know what could have caused the blip to be honest - network issues
are always are pain to diagnose, especially when you have no control over
most of the infrastructure.
Who is hosting your CNAME records? If there was an underlying issue with
Google's network I think they'd be a lot of
What I meant to ask was, what have caused those servers to cache a negative
result.
The app.dziennik.edu.pl domain was a CNAME to ghs.google.com from the start,
and it is set-up for a couple of months now. My other domain that have the
same issues www.bravelabs.pl have been setup and untouched
Negative results are cached for exactly the same reasons as positive ones -
performance. If a domain is unresolvable, then it's very likely that in 5
minutes time it will still be unresolvable, so the negative result is stored
for a period of time to remove the need to do the lookup again.
As
What can be the reason whey a negative result was cached?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/oBwVWXRJyaEJ.
To post to this group, sen
DNS servers can cache negative results as well as positive - albeit
normally for a shorter time. It seems that 62.179.1.63 or 62 are
caching or a pointing to another DNS server that's caching the fact
that app.dziennik.edu.pl was unresolvable.
On Sep 30, 4:41 pm, Janusz Skonieczny
wrote:
> But ho
But how It could have cached a bad lookup? The CNAME was set to
ghs.google.com from day one.
Here an example network settings:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : chello.pl
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
P
That means that their company's internal DNS server, or the user's ISP's DNS
server, isn't resolving your name.
What DNS server are they pointing to? It looks like their server's cached a
bad lookup and hasn't refreshed.
--
You received this message because you are subscribed to the Google Gr
This a problem, cause their pointed nowhere. It's not a case of bad IP
address or a proxy server looking in the wrong place. Its like there is no
DNS entry for my domain.
Call to ipconfig /displaydns gives results like these:
Windows IP Configuration
ghs.google.com
It sounds to me like there is a common DNS server which your users are
using, which is returning incorrect results. Flushing their DNS wouldn't
help, because all that flushes is the local PCs cache and as soon as it went
to the DNS server it would retrieve the incorrect result again.
Get them
I have asked for flushdns, it did not help. Anyway there was never anything
other than ghs.google.com under app.dziennik.edu.pl CNAME, so these people
could not have cached anything else.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
hmm, some kind of network/dns caching going on in those remote locations?
proxy servers?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/VQ8TgYidl
I have done all that a while ago and everything worked fine (at least no one
was complaining). This problem only appeared recently (maybe two weeks ago)
as users started to that server is unreachable from some locations, like it
is working from the office but not from home.
App is working with
All you need to do is create a cname record for 'app' to point to
ghs.google.com (did a dns lookup - seems you have already done that). Then,
log into your Google Apps domain CPanel (www.google.com/a/[your-domain]) and
click Add More Services, then enter the App ID for your App Engine in the
"E
16 matches
Mail list logo
