FQDN not Resolving

I can reach your site from my end here in Northern, NJ.

Please post the output of a traceroute to the domain name.

Here is a sample trace from my end for comparative purposes;

Tracing route to eliashickman.com [35.206.108.229]
over a maximum of 30 hops:

1 7 ms 3 ms 4 ms 192.168.1.1
2 18 ms 11 ms 17 ms 96.120.73.93
3 13 ms 10 ms 18 ms 24.124.228.65
4 13 ms 12 ms 14 ms 96.108.9.17
5 15 ms 13 ms 13 ms be33-rar01.plainfield.nj.panjde.comcast.net [68.85.63.25]
6 20 ms 17 ms 13 ms be-98-ar03.plainfield.nj.panjde.comcast.net [68.85.35.37]
7 25 ms 16 ms 15 ms be-31113-cs01.newark.nj.ibone.comcast.net [96.110.42.33]
8 17 ms 14 ms 25 ms be-1101-cr01.newark.nj.ibone.comcast.net [96.110.36.82]
9 16 ms 14 ms 20 ms be-10203-cr02.newyork.ny.ibone.comcast.net [68.86.85.186]
10 40 ms 33 ms 46 ms be-10305-cr02.350ecermak.il.ibone.comcast.net [68.86.85.202]
11 49 ms 38 ms 34 ms be-1402-cs04.350ecermak.il.ibone.comcast.net [96.110.36.109]
12 31 ms 38 ms 34 ms be-2403-pe03.350ecermak.il.ibone.comcast.net [96.110.37.30]
13 36 ms 34 ms 37 ms 173.167.56.22
14 33 ms 29 ms 29 ms 10.252.162.222
15 33 ms 35 ms 31 ms 72.14.239.122
16 41 ms 91 ms 41 ms 108.170.243.219
17 32 ms 31 ms 33 ms 72.14.233.10
18 44 ms 50 ms 46 ms 142.250.231.184
19 42 ms 40 ms 41 ms 172.253.75.248
20 40 ms 54 ms 44 ms 172.253.78.179
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 46 ms 41 ms 39 ms 229.108.206.35.bc.googleusercontent.com [35.206.108.229]

Trace complete.

My trace does not do that. And it completes to the destination server.

The nameserver is in Iowa.

IP Address Country Region City

Why is it going through Chicago and East Cermak, any idea?

Is Google Hosting Services your webhost ? If so, this first IP address in the last hop belongs to Google (72.14.236.1 ), so it would appear that your packets are making it into their web space, but you are being blocked internally by them for some reason. If they are your host, you should contact them about this.

traceroute to eliashickman.com (35.206.108.229), 30 hops max, 60 byte packets
1 _gateway (10.0.0.1) 2.558 ms 3.468 ms 4.401 ms
2 96.120.5.145 (96.120.5.145) 19.975 ms 21.371 ms 20.741 ms
3 96.110.192.1 (96.110.192.1) 36.467 ms 36.852 ms 37.700 ms
4 ae-29-ar01.b0atlanta.ga.atlanta.comcast.net (162.151.88.217) 25.694 ms 25.280 ms 24.826 ms
5 be-33011-cs01.56marietta.ga.ibone.comcast.net (96.110.43.65) 26.579 ms 32.935 ms be-33041-cs04.56marietta.ga.ibone.comcast.net (96.110.43.77) 32.072 ms
6 be-1312-cr12.56marietta.ga.ibone.comcast.net (96.110.34.218) 32.436 ms be-1412-cr12.56marietta.ga.ibone.comcast.net (96.110.34.222) 14.018 ms be-1112-cr12.56marietta.ga.ibone.comcast.net (96.110.34.210) 13.511 ms
7 be-301-cr11.chicago.il.ibone.comcast.net (96.110.37.162) 35.590 ms be-302-cr11.chicago.il.ibone.comcast.net (96.110.38.74) 36.544 ms be-301-cr11.chicago.il.ibone.comcast.net (96.110.37.162) 36.122 ms
8 be-1211-cs02.chicago.il.ibone.comcast.net (96.110.36.21) 37.255 ms 42.011 ms be-1411-cs04.chicago.il.ibone.comcast.net (96.110.36.29) 41.218 ms
9 be-1212-cr12.chicago.il.ibone.comcast.net (96.110.36.38) 41.611 ms be-1112-cr12.chicago.il.ibone.comcast.net (96.110.36.34) 40.458 ms 31.935 ms
10 be-302-cr13.350ecermak.il.ibone.comcast.net (96.110.38.213) 36.135 ms be-304-cr13.350ecermak.il.ibone.comcast.net (96.110.38.221) 37.030 ms 36.627 ms
11 be-1113-cs01.350ecermak.il.ibone.comcast.net (96.110.35.33) 38.306 ms 41.592 ms be-1313-cs03.350ecermak.il.ibone.comcast.net (96.110.35.41) 41.117 ms
12 be-2301-pe01.350ecermak.il.ibone.comcast.net (96.110.37.10) 30.464 ms be-2201-pe01.350ecermak.il.ibone.comcast.net (96.110.37.6) 37.749 ms be-2211-pe11.350ecermak.il.ibone.comcast.net (96.110.33.198) 37.991 ms
13 50.208.232.238 (50.208.232.238) 36.677 ms 173.167.56.22 (173.167.56.22) 37.198 ms 96-87-9-190-static.hfc.comcastbusiness.net (96.87.9.190) 44.197 ms
14 216.239.56.7 (216.239.56.7) 43.393 ms 42.956 ms 74.125.251.183 (74.125.251.183) 43.764 ms
15 108.170.243.254 (108.170.243.254) 40.139 ms 108.170.243.175 (108.170.243.175) 45.507 ms 108.170.243.254 (108.170.243.254) 45.976 ms
16 216.239.40.189 (216.239.40.189) 47.368 ms 216.239.63.33 (216.239.63.33) 47.615 ms 216.239.57.77 (216.239.57.77) 46.785 ms
17 72.14.234.9 (72.14.234.9) 60.981 ms * 142.250.231.184 (142.250.231.184) 52.798 ms
18 142.250.235.163 (142.250.235.163) 88.184 ms 142.250.235.165 (142.250.235.165) 51.862 ms 216.239.59.20 (216.239.59.20) 53.188 ms
19 72.14.236.1 (72.14.236.1) 56.778 ms 142.250.57.168 (142.250.57.168) 55.816 ms 216.239.58.59 (216.239.58.59) 57.536 ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

I've never seen this before.... Your trace is resolving to 2 or three different numerical IP addresses on the latter hops. I'm afraid that I don't know how to advise you on this one. All I know is that I don't see your trace completing to the initial target IP address. Sorry.

Thanks for checking. At least I've opened a case and someone should be in contact with me soon.

Good luck with it ! Please do post back with how things turn out !

I beleive a comcast employee needs to clear the ARP (address resolution protocol) on the routers'/gateways' cache to allow the new address to be cached.

Best of luck with that ever happening bud..... Their NOC's / network engineers have never been transparent, especially not here....

Hello. Are there any comcast employees available to help?