HELP! Could you check if you can access my...

[FancyToy]

temporary Web site:

http://xheartstreet.futurequest.net

I'm having trouble to load it from my side of the net!

Thank you very much for your help!

FancyToy

[sheila]

I accessed it with no problems.

[teach1st]

I couldn't access it.

[Dan Kaplan]

I get unknown host.

Dan

[Terra]

I have just gone through all of the DNS servers (ns1/ns2/ns3) and everything is working properly...

Below is the 'dig' result:
; <<>> DiG 8.2 <<>> @ns1.futurequest.net xheartstreet.futurequest.net
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
;; QUERY SECTION:
;;[nbsp][nbsp][nbsp][nbsp][nbsp]xheartstreet.futurequest.net, type = A, class = IN

;; ANSWER SECTION:
xheartstreet.futurequest.net.[nbsp][nbsp]1D IN A[nbsp][nbsp]208.243.19.61

;; AUTHORITY SECTION:
futurequest.net.[nbsp][nbsp][nbsp][nbsp][nbsp]1D IN NS[nbsp][nbsp][nbsp][nbsp][nbsp]ns1.futurequest.net.
futurequest.net.[nbsp][nbsp][nbsp][nbsp][nbsp]1D IN NS[nbsp][nbsp][nbsp][nbsp][nbsp]ns2.futurequest.net.
futurequest.net.[nbsp][nbsp][nbsp][nbsp][nbsp]1D IN NS[nbsp][nbsp][nbsp][nbsp][nbsp]ns3.futurequest.net.

;; ADDITIONAL SECTION:
ns1.futurequest.net.[nbsp][nbsp][nbsp][nbsp][nbsp]1W IN A[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]208.243.19.2
ns2.futurequest.net.[nbsp][nbsp][nbsp][nbsp][nbsp]1W IN A[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]208.243.19.3
ns3.futurequest.net.[nbsp][nbsp][nbsp][nbsp][nbsp]1W IN A[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]208.243.19.4

;; Total query time: 0 msec
;; FROM: six.futurequest.net to SERVER: ns1.futurequest.net[nbsp][nbsp]208.243.19.2
;; WHEN: Tue Jan[nbsp][nbsp]4 21:46:10 2000
;; MSG SIZE[nbsp][nbsp]sent: 46[nbsp][nbsp]rcvd: 179

Perhaps you have tried to load up 'futurequest.net' before the new temporary URL 'xheartstreet.futurequest.net' was setup and brought online...

The TTL (Time to Live: 86400 sec) covers '*.futurequest.net' so it appears that this will have to timeout before the new URL becomes active...[nbsp][nbsp]This is why we have a 24 hour setup time to take this into account...

I will investigate ways trimming the TTL down, but for best efficiency, TTL==86400 is about as low as I can realistically lower it...

Hope this helps to explain...

--
Terra
--DNS is one of those things that needs to be understood and respected to ensure proper operation, people have learned the hard way that it does in fact have fangs and claws--
FutureQuest

[FancyToy]

Deb,

I just tried from home and it seems to work.

Yet, 4 individuals were able to confirm it is not accessible from everywhere.

This is very mysterious. I have founded an ISP and I never experienced something similar.

It would be interesting to understand what is the cause of this situation.

My lab. is behind a firewall and we have a proxy set up. Could that explain it?

[tedloh]

I got it instantly here in Thailand!
------------------
Ted (Chief Do-It-All)
Tygre Systems Co Ltd
Bangkok, Thailand, Land of Smiles :) :)
http://www.tygresystems.com (work currently on hold)
ted@tygresystems.com

[MTDesigns]

Don't know if you're still having problems, but I was able to access it with no problem :-).

------------------
Joi
My ParenTime (Info Community)
http://www.myparentime.com
STOP Sex Offenders (Child Safety)
http://www.stopsexoffenders.com

[Dean B]

Clear as a bell here in the UK :)

------------------
Regards, Dean.
**DMCity**
www.dmcity.com (http://www.dmcity.com)[nbsp][nbsp][nbsp][nbsp][nbsp][nbsp]
**********