I did not get a connection. Then I did a traceroute:
traceroute to www.pizzahut.com (192.112.151.78), 30 hops max, 40 byte packets
1 ursula (131.252.12.155) 2 ms 2 ms 2 ms
2 pdx-gwy (131.252.20.1) 4 ms 4 ms 4 ms
3 192.80.17.66 (192.80.17.66) 8 ms 5 ms 7 ms
4 portlandfr-gw.nwnet.net (192.147.174.3) 8 ms 6 ms 7 ms
5 spokane1-gw.nwnet.net (192.147.162.106) 30 ms 38 ms 18 ms
6 192.80.16.130 (192.80.16.130) 52 ms 40 ms 36 ms
7 seabr2-gw.nwnet.net (198.104.193.194) 62 ms 31 ms 48 ms
8 enss143-fddi.nwnet.net (192.147.179.2) 55 ms !H 35 ms !H 27 ms !H
This route is definately wierd.... I don't know if this
problem originates at pizzahut directly or if this is something people
along the way are responsible for... but so much for pizza people and tech-
nology. Maybe the dns records are so new that they are not advertised all
over the place yet. All our other connections route fine. hmmm
Tim