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.

If that website is inga ellzey..... it came up for me.
1 10.153.192.1 (10.153.192.1) 12.539 ms 17.234 ms 11.495 ms
2 12.244.96.129 (12.244.96.129) 14.569 ms 11.647 ms 29.261 ms
3 12.244.67.109 (12.244.67.109) 26.817 ms 15.797 ms 16.238 ms
4 12.244.67.97 (12.244.67.97) 21.159 ms 12.144 ms 13.701 ms
5 12.244.67.93 (12.244.67.93) 28.070 ms 14.989 ms 13.122 ms
6 12.127.32.33 (12.127.32.33) 17.212 ms 16.275 ms 13.563 ms
7 tbr2-p013701.sffca.ip.att.net (12.123.13.177) 14.497 ms 14.689 ms 18.030 ms
8 12.122.80.57 (12.122.80.57) 15.138 ms 13.428 ms 14.087 ms
9 att-gw.sfo.qwest.net (192.205.32.82) 16.351 ms 15.875 ms 21.243 ms
10 svx-core-01.inet.qwest.net (205.171.214.133) 25.669 ms 16.262 ms 18.221 ms
11 svl-core-02.inet.qwest.net (205.171.14.77) 24.862 ms 16.576 ms 28.905 ms
12 dca-core-03.inet.qwest.net (205.171.9.10) 82.007 ms 82.494 ms 83.375 ms
13 dca-edge-04.inet.qwest.net (205.171.9.98) 82.819 ms 82.385 ms 82.095 ms
14 65.123.21.194 (65.123.21.194) 81.135 ms 81.962 ms 80.707 ms
15 65.125.28.194 (65.125.28.194) 88.634 ms 85.627 ms 84.012 ms
16 iepg.com (64.176.162.44) 86.724 ms 85.979 ms 88.882 ms

temp downstream congestion?

as a side not, it took fairly long to load. +60ms once it gets to quest so i imagion something going on

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).

Came up like a champ for me...

BAM! open working

I'm afraid to look. What's on it?

figure out where the qwest router in question is located and let them know it's down ...

your website werks fine, it's just that the route between you and the site is broken. has nothing to do with your provider or NWS ...

Andy

It was fixed. Turns out it was the hoster. They had a server that was pooling unused IPs and mine somehow got in the loop this afternoon.