| |
subdomain iconbar |
| |
Revin Kevin (19:51 21/9/2004)
rich (15:53 22/9/2004)
alpha (19:51 24/9/2004)
rich (09:48 27/9/2004)
Phlamethrower (13:53 27/9/2004)
Revin Kevin (20:18 27/9/2004)
alpha (21:41 27/9/2004)
Phlamethrower (22:18 27/9/2004)
Phlamethrower (21:44 6/10/2004)
Phlamethrower (22:57 6/10/2004)
rich (12:35 7/10/2004)
Phlamethrower (12:53 7/10/2004)
rich (12:58 7/10/2004)
rich (11:49 8/10/2004)
|
| |
|
Kevin Wells |
Message #58046, posted by Revin Kevin at 19:51, 21/9/2004 |
Member
Posts: 644
|
All the subdomains seem to be down.
________
I did not do it. |
| |
 [ Log in to reply ] |
| |
|
Richard Goodwin |
Message #58047, posted by rich at 15:53, 22/9/2004, in reply to message #58046 |
 Dictator for life
Posts: 6828
|
No, they seem to be still there (I'm testing by VNCing from work to home, and web browsing there  )
I think there were some network problems which might have stopped DNS working, unless you've got the DNS cached - which is how I presume you got here.
Try doing a traceroute to subdomains that don't work, and see what error you get - if it's going to the old server (213.161.67.197) or just can't resolve the address at all.
________
 Cheers,
Rich.
|
| |
[ Log in to reply ] |
| |
|
Tim Fountain |
Message #58048, posted by alpha at 19:51, 24/9/2004, in reply to message #58047 |
Forum bod
Posts: 570
|
TIB itself seems to be down now. Something to do with DNS, I got here by hard coding the IP into my hosts file. Been like this for a few days I think... |
| |
[ Log in to reply ] |
| |
|
Richard Goodwin |
Message #58049, posted by rich at 09:48, 27/9/2004, in reply to message #58048 |
Dictator for life
Posts: 6828
|
II still need to know where it's failing - what address is it pointing to when you do a DNS query? 213.161.75.250 or 213.161.67.197?
________
Cheers,
Rich.
|
| |
[ Log in to reply ] |
| |
|
Jeffrey Lee |
Message #58050, posted by Phlamethrower at 13:53, 27/9/2004, in reply to message #58049 |
 Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot stuff
Posts: 15100
|
II still need to know where it's failing - what address is it pointing to when you do a DNS query? 213.161.75.250 or 213.161.67.197? 213.161.75.250 for me. |
| |
[ Log in to reply ] |
| |
|
Kevin Wells |
Message #58077, posted by Revin Kevin at 20:18, 27/9/2004, in reply to message #58050 |
Member
Posts: 644
|
All seem to work. 
________
I did not do it. |
| |
[ Log in to reply ] |
| |
|
Tim Fountain |
Message #58080, posted by alpha at 21:41, 27/9/2004, in reply to message #58049 |
Forum bod
Posts: 570
|
.75.250 again now - all seems to be well.
Edit: http://www.dnsreport.com/tools/dnsreport.ch?domain=iconbar.com - always useful for debugging DNS stuff.
[Edited by alpha at 21:45, 27/9/2004] |
| |
[ Log in to reply ] |
| |
|
Jeffrey Lee |
Message #58081, posted by Phlamethrower at 22:18, 27/9/2004, in reply to message #58080 |
Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot stuff
Posts: 15100
|
.75.250 again now - all seems to be well.
Edit: http://www.dnsreport.com/tools/dnsreport.ch?domain=iconbar.com - always useful for debugging DNS stuff.
[Edited by alpha at 21:45, 27/9/2004] http://spf.pobox.com/
Interesting! |
| |
[ Log in to reply ] |
| |
|
Jeffrey Lee |
Message #58233, posted by Phlamethrower at 21:44, 6/10/2004, in reply to message #58047 |
Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot stuff
Posts: 15100
|
I think there were some network problems which might have stopped DNS working, unless you've got the DNS cached - which is how I presume you got here. The server hasn't been responding to anything for the last half hour or so, on either the old or new IP address. Traceroutes revealed the last working hop as 213.161.67.219. Although I've just checked again now, and the hop between that and the server doesn't respond to pings anyway - so I might have just been a bit hasty and stopped the trace before it reached something broken. |
| |
[ Log in to reply ] |
| |
|
Jeffrey Lee |
Message #58237, posted by Phlamethrower at 22:57, 6/10/2004, in reply to message #58233 |
Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot stuff
Posts: 15100
|
And again!
The trace certainly seems to be getting stuck on the hop just after 213.161.67.219, or on the server itself. |
| |
[ Log in to reply ] |
| |
|
Richard Goodwin |
Message #58241, posted by rich at 12:35, 7/10/2004, in reply to message #58237 |
Dictator for life
Posts: 6828
|
And again!
The trace certainly seems to be getting stuck on the hop just after 213.161.67.219, or on the server itself. The server is no longer on the 213.161.67.* network; what is the IP that the traceroute is reporting as your destination?
Edit: Plus, I probably have traceroute and ping disabled from most places anyway.
________
Cheers,
Rich.
|
| |
[ Log in to reply ] |
| |
|
Jeffrey Lee |
Message #58242, posted by Phlamethrower at 12:53, 7/10/2004, in reply to message #58241 |
Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot Hot stuff
Posts: 15100
|
And again!
The trace certainly seems to be getting stuck on the hop just after 213.161.67.219, or on the server itself. The server is no longer on the 213.161.67.* network; what is the IP that the traceroute is reporting as your destination?
213.161.75.250. If the server isn't on the 67.* network, would this explain why the hop between 67.219 and 75.250 isn't working? I.e. it's looking for the server on an old route, failing, then looking on the new route and finding it.
Also I've just checked the old IP (67.197), and it seems that a reverse DNS lookup on it returns neo.onepointnought.com. |
| |
[ Log in to reply ] |
| |
|
Richard Goodwin |
Message #58243, posted by rich at 12:58, 7/10/2004, in reply to message #58242 |
Dictator for life
Posts: 6828
|
Yes, I haven't got round to giving it it's own name yet - it requires re-writing of the DNS updaters to not rewrite it's address to the new server. I was supposed to be switching it off entirely, but it's doing a sort of tertiary DNS. The secondary failed just when we were having problems, and had to be reinstalled from an old backup, which caused some of the recent problems.
The routing thing might be something to look in to, but I'll have to wait until the main sysadmin is back in - Monday 
________
Cheers,
Rich.
|
| |
[ Log in to reply ] |
| |
|
Richard Goodwin |
Message #58283, posted by rich at 11:49, 8/10/2004, in reply to message #58243 |
Dictator for life
Posts: 6828
|
I've thought it - the gateway for the whole office was down about then (I was actually logging in to it and named was running at 50% CPU for some reason) but I didn't put two and two together. And the office connectivity comes down a leased line from London, hence the 213.161.67.foo hop.
If it helps, here's my traceroute from home to the server:
Tracing route to iconbar.com [213.161.75.250] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.richardgoodwin.net [10.0.0.138]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 353 ms 316 ms 370 ms 213.161.75.250
Trace complete.
________
Cheers,
Rich.
|
| |
[ Log in to reply ] |
| |
|
