 OT: What to do when domain isn't working |
|
|
|
Porsche, and the Porsche crest are registered trademarks of Dr. Ing. h.c. F. Porsche AG.
This site is not affiliated with Porsche in any way. Its only purpose is to provide an online forum for car enthusiasts. All other trademarks are property of their respective owners. |
|
|
| Qarl |
 May 3 2005, 03:01 PM
Post
#1
|
|
Shriveled member  Group: Benefactors Posts: 5,233 Joined: 8-February 03 From: Florida Member No.: 271 Region Association: None   |
I have our own domain...
www.iepg.com It's not working. I called the web hosting company, they said their servers are fine and their DNS servers are fine. They said to call Network Solutions (the registrar) and that their servers weren't resolving the domain to their (webhoster) DNS servers. I called Network Solutions and they said everything was fine on their end. I did a tracert to the domains IP, and it looks like something is hanging up on or after qwest.net internet router. What do I do next? Here is the tracert... Destination host: 64.176.162.44 Data size: 48 bytes. 1: 10.0.0.126 [10.0.0.126], RTT: 0ms 2: fl-64-45-231-1.sta.sprint-hsd.net [64.54.365.1], RTT: 41ms 3: crflwnpk01 [69.34.4.249], RTT: 43ms 4: icrwnpk1 [207.30.23.29], RTT: 42ms 5: sl-gw13-orl-5-0.sprintlink.net [160.81.69.89], RTT: 43ms 6: sl-bb21-orl-14-0.sprintlink.net [144.232.2.187], RTT: 43ms 7: sl-bb20-atl-2-0.sprintlink.net [144.232.20.86], RTT: 63ms 8: sl-bb23-atl-8-0.sprintlink.net [144.232.12.14], RTT: 57ms 9: 144.232.9.86 [144.232.9.86], RTT: 59ms 10: atl-core-02.inet.qwest.net [205.171.21.170], RTT: 58ms 11: dca-core-02.inet.qwest.net [205.171.8.154], RTT: 75ms 12: dca-edge-04.inet.qwest.net [205.171.9.66], RTT: 77ms 13: Request timed out. 14: Request timed out. 15: Request timed out. 16: Request timed out. 17: Request timed out. 18: Request timed out. 19: Request timed out. 20: Request timed out. 21: Request timed out. 22: Request timed out. 23: Request timed out. 24: Request timed out. 25: Request timed out. 26: Request timed out. 27: Request timed out. 28: Request timed out. 29: Request timed out. 30: Request timed out. 31: Request timed out. 32: Request timed out. 33: Request timed out. 34: Request timed out. 35: Request timed out. 36: Request timed out. 37: Request timed out. 38: Request timed out. 39: Request timed out. Statistics for host: 64.176.162.44 40 packets transmited, 13 packets received, 68% packet loss. |
   |
 
|
  |
Replies
| lapuwali |
May 3 2005, 04:08 PM
Post
#2
|
|
Not another one! Group: Benefactors Posts: 4,526 Joined: 1-March 04 From: San Mateo, CA Member No.: 1,743 |
There's a great tool called DNS Report: DNS Report It will report EVERYTHING about your domain. Looks to me like your ISP has to clean up the DNS setup. They probably need to learn how to do it, first. It's amazing how many small-ish ISPs don't have anyone who actually understands the DNS system.
Your domain has multiple DNS servers and they're not reporting the same thing. There's one server that's not reporting "authoritatively", which is a rookie mistake in configuration. Send them to this page and see what they say. That site also came up for me, and it was also pretty slow, and it's definitely NOT at my end (I'm sitting inside Yahoo right now). |
|
|
|
Posts in this topic
Qarl OT: What to do when domain isn't working May 3 2005, 03:01 PM
ben1440 If that website is inga ellzey..... it came up for... May 3 2005, 03:26 PM ben1440 as a side not, it took fairly long to load. +60ms... May 3 2005, 03:33 PM ! Came up like a champ for me... May 3 2005, 04:16 PM rick 918-S BAM! open working http:... May 3 2005, 04:22 PM Howard I'm afraid to look. What's on it? May 3 2005, 04:23 PM SirAndy figure out where the qwest router in question is l... May 3 2005, 04:28 PM
Qarl It was fixed. Turns out it was the hoster. They ... May 3 2005, 04:37 PM |
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
Lo-Fi Version | Time is now: 1st June 2024 - 02:47 PM |
Invision Power Board
v9.1.4 © 2024 IPS, Inc.