|
These forums aren't working properly...
|
View this Thread in Original format
| Mr.Mystery |
...I can't get to these forums at all when I use IE6 because I keep getting this message:
| quote: |
Hi.
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.
Please bookmark -> http://207.44.152.203 which is the new address.
|
But when I use the new address I just keep getting the same error message...
I'm surfing with Opera now and it seems to be working fine... any idea on what the problem is? |
|
|
| butterfly |
| i use IE6 and i haven't had any problems. |
|
|
| jonsimmonds |
| you deleted the tempory internet files? |
|
|
| flystyler |
| 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 :D |
|
|
| tranceaholic |
| well what if u have pop up blocker? |
|
|
| 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." |
|
|
| Starfox |
| 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." |
hrhr blind people =P |
|
|
| cycloptor |
| 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." |
exactly.... i got it last night. then magically at 2am, when cogeco's dns servers update everything started working again. |
|
|
| butterfly |
| 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) |
|
|
| Fir3start3r |
| 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? |
|
|
| Swamper |
| 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 |
|
|
| Fir3start3r |
| 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
:) |
|
|
|
|
