___________________
Beware of killer hamsters and the random running dogs.
Nov-19-2002 16:41
flystyler
Defected[JULES]Addict
Registered: Jun 2001
Location: Aylesbury, UK
quote:
Originally posted by jonsimmonds
you deleted the tempory internet files?
hehe. I doubt that would be the problem
It maybe down to cookies, but i doubt it, and i hope u dont have a pop up blocker on yr comp
Anyway if it isnt any of them, it sounds like u have been messing around with IE6, not sure wot u have done, just reset all the security options to default, etc
___________________
Nov-19-2002 17:15
tranceaholic
chus & Ceballos addict
Registered: Mar 2002
Location: behind the decks
well what if u have pop up blocker?
Nov-19-2002 17:19
Swamper
Webmonstah
Registered: Jan 2000
Location: Toronto, Canada
Uh, the problem is already explained there:
"If you see this message it is because your ISP's DNS servers have not yet been updated with TranceAddict.com's new server address."
___________________
"In a world of illusion you only see what you feel"
Nov-19-2002 18:45
arturob
Supreme tranceaddict
Registered: Jan 2001
Location: Miami
quote:
Originally posted by Swamper
Uh, the problem is already explained there:
"If you see this message it is because your ISP's DNS servers have not yet been updated with TranceAddict.com's new server address."
Originally posted by Swamper
Uh, the problem is already explained there:
"If you see this message it is because your ISP's DNS servers have not yet been updated with TranceAddict.com's new server address."
exactly.... i got it last night. then magically at 2am, when cogeco's dns servers update everything started working again.
___________________
i r teh hax
~~~Xxx(((TrancEaddicT Haiku/CQ Alliance 2005)))xxX~~~
Nov-19-2002 18:49
butterfly
melissa
Registered: Apr 2002
Location: West CoCo, CA
quote:
Originally posted by Swamper
Uh, the problem is already explained there:
"If you see this message it is because your ISP's DNS servers have not yet been updated with TranceAddict.com's new server address."
yeah but that still doesn't make much sense to some people. (like me)
Nov-19-2002 18:52
Fir3start3r
Armin Acolyte
Registered: Oct 2001
Location: Toronto, ON, Canada
quote:
Originally posted by butterfly
yeah but that still doesn't make much sense to some people. (like me)
A DNS server converts domain names like "Tranceaddict.com" into an IP address for your computer to use.
When you type in Tranceaddict.com, your computer sends a DNS request to your ISP's DNS servers.
The DNS server converts Tranceaddict.com into the IP address (in this case 207.44.152.203) and sends it back to your computer.
Your computer then uses this information to go out into the web to connect to the address you specified.
In theory if the ISP's DNS server didn't have an entry for Tranceaddict.com it 'should' have passed the request onto another DNS server up the chain of hierarchy on the internet until it does get resolved. Instead, they chose to give the error: "If you see this message it is because your ISP's DNS servers have not yet been updated with TranceAddict.com's new server address."
Strange though that is worked with Opera but not IE6...
Mr.Mystery have you tried going back to IE6 since success with Opera?
___________________
"...End? No, the journey doesn't end here. Death is just another path...one that we all must take.
The grey rain-curtain of this world rolls back, and all change to silver glass...and then you see it...
...white shores...and beyond...the far green country under a swift sunrise."
Nov-20-2002 04:47
Swamper
Webmonstah
Registered: Jan 2000
Location: Toronto, Canada
quote:
Originally posted by Fir3start3r
In theory if the ISP's DNS server didn't have an entry for Tranceaddict.com it 'should' have passed the request onto another DNS server up the chain of hierarchy on the internet until it does get resolved. Instead, they chose to give the error: "If you see this message it is because your ISP's DNS servers have not yet been updated with TranceAddict.com's new server address."
Not quite... the ISP is caching the old data - expiry for cached data is WAY too long for some places. Once it comes time to refresh it hits the primary dns, when that dies it hits the secondary dns, and finally when that dies it checks the whois database to see if the nameserver data is the same for that domain - if it's modified then it digs the info out of the new name servers...
That message that came up was a message I set up on the old server as a redirect to any clients coming to the old IP.... :P
___________________
"In a world of illusion you only see what you feel"
Nov-20-2002 07:29
Fir3start3r
Armin Acolyte
Registered: Oct 2001
Location: Toronto, ON, Canada
quote:
Originally posted by Swamper
Not quite... the ISP is caching the old data - expiry for cached data is WAY too long for some places. Once it comes time to refresh it hits the primary dns, when that dies it hits the secondary dns, and finally when that dies it checks the whois database to see if the nameserver data is the same for that domain - if it's modified then it digs the info out of the new name servers...
That message that came up was a message I set up on the old server as a redirect to any clients coming to the old IP.... :P
An addendum,
If you're using Windows2000/XP the local DNS resolver (local cache) should be cleared to...as DNS errors will just continue unless cleared...
command: ipconfig /flushdns
___________________
"...End? No, the journey doesn't end here. Death is just another path...one that we all must take.
The grey rain-curtain of this world rolls back, and all change to silver glass...and then you see it...
...white shores...and beyond...the far green country under a swift sunrise."
