E-Hell, you're back, but not for me....

[Twik]

For some reason, I can log in normally on one computer, but not my main home computer. The browser stubbornly returns "page not found". However, if I use a proxy server, I can log in, although for some reason my posts get random "/" symbols throughout.

If you're wondering why I keep hitting the slash key so much, I'm really not.

Anyone have the solution to the proxy problem?

[Ehelldame]

I swear it sounds like the DNS name change has not fully propagated completely through to every name server.

Below are instructions for testing whether your DNS has received the correct information for resolving the address of www.etiquettehell.com.


Under Windows, press the Start button.


Select "Run".


Type CMD and press enter.


At C:> prompt, type     nslookup www.etiquettehell.com      and press enter


The result should look something like:
C:\>nslookup www.etiquettehell.com
Server:  dslrouter
Address:  192.168.1.254
Non-authoritative answer:
Name:    etiquettehell.com
Address:  72.21.37.206
Aliases:  www.etiquettehell.com

The numeric Address entry under the Name entry should read 72.21.37.206 if your DNS server has received the update.

Tell me what you get.  My husband says that some name servers (including LANS and WIFIS) are set to delete their caches and update every two hours, some once a week, etc.  If a name server between you and me has not been cleared of its cache and updated the DNS name change, you won't be able to access the domain at all until it does. 

DNS propagation failure results in no access to the entire domain.  Cookies and temp internet files undeleted will result in flaky access to the forum but won't affect access to the main domain/site. 

[War_Doc]

I'm getting a "can't find www.etiquettehell.com:  Server failed" error.  My DNS request timed-out via nslookup.  Pinging gives me long hang times and 75% of my packets getting through.  tracert shows it getting hung up at the server 206.37.21.72.static.reverse.layeredtech.com.

[Twik]

Same thing as War_Doc:

***Can\'t find server name for address 192.168.2.1: Non-existent domain
***Default servers are not available
Server unknown
Address 192.168.2.1
***UnKnown can\'t find www.etiquettehell.com: Server failed

[Ehelldame]

I'm getting a "can't find www.etiquettehell.com:  Server failed" error.  My DNS request timed-out via nslookup.  Pinging gives me long hang times and 75% of my packets getting through.  tracert shows it getting hung up at the server 206.37.21.72.static.reverse.layeredtech.com.

Aha! We're getting somewhere!  The 206.37.21.72 IP address is the reverse IP address for the Ehell domain. I don't understand it and cannot explain it but something about how the reverse DNS lookup (reverting a numeric IP address to the name, I think) has not been set up yet.   I've forwarded your posts to tech support and I'm confident the problem will be solved soon. 

[Ehelldame]

Ok, War-Doc, your problem is related to an incorrect DNS matchup.

Twik, yours is a local problem. 192.168.*.* are local IPs used by private internal networks.

Tech support tweaked the DNS and then advised that it could be another 24 hours before the DNS corrections propagate through.

If that fails, I will rename the cookie the forum gives and see if that works. 

[freakyfemme]

I got the same message over and over again at various points over the course of today......so that's why I'm surfing E-hell at 3 a.m., lol.

[sparksals]

I have had the same problem for the last few days.  I had access from my home computer, then none, then got in and then shut out again.  This is the answer I got after some digging:

Go to start -> Run -> type cmd -> and then type ipconfig/flushdns

The information my not have left the DNS server at your ISP.  The above command will clear it out.  I didn't have to reboot either.  FWIW, I'm using Qwest, so I know Twik isn't since she's in CAnada, so it's not a single ISP issue.

Hope this helps for others!

[Twik]

Hurray, I'm back - whatever the problem was, it's worked out.