IP Problems

[ctheartiste]

Hi

I have a question about the IP management. Sometime ago it was working fine now the main server's ip is ok i can access directadmin andeverything but the sub domain's ip address that used to work correctly cannot be access.

When doing a tracert it dies at the router's ip.

Is this something that DirectAdmin handles or is there more to this?

example:

ip: 64.44.111.1 (server) works
one domain: 64.44.111.2 (used to work)
one domain: 64.44.111.3 (used to work)

router: 64.44.117.1
When doing a tracert it hangs at the router for the one domain numberws that was assigned via DA. But it is reachable at the server level.

 

[skruf]

Hey,

If it's routing issues you're seeing, then the place to start is with your hosting provider.

Make sure the IPs they have assigned to you are still routed properly.

Right now, from here

http://www.net.berkeley.edu/cgi-bin/traceroute

All of the IPs you listed are failing the traceroute.

David

 

[ctheartiste]

Hi sorry to forgot to mention this but that was an example so the IP addresses were not the real ones. Due to the nature of the domain and nature of whats being develop on the actual server i cannot publisht he real IP i was just giving an example of numbers that i have and what was happening.

Though after posting it....i've rebooted some services...i've also waited like a good 10mins and then i got some responses.

Though i wanted to know anyways where would my hunt would have begun...as i have stated that it would block at one level before reaching the server's ip when using a distributed IP (ie if my server is 6, my subs and free ips were 7 and 8) and those were getting stuck

so if i do a tracert from that site..what does that tell me more than what i do on the command prompt?

 

[skruf]

Hey,

Well, first off... If you do not want to use the real IP addresses... That's your choice.

It does make it harder for anyone trying to answer/troubleshoot your problems...

Using traceroute from another point on the Internet simply gives you more info in an attempt to pin point your issue.

An issue could simply be on the network you are on and not on others. Additional traceroute points will help give you a bigger picture.

David

 

[ctheartiste]

Thanks for the insight.

Odd part...after just rebooting name and httpd (just to jump start things) it started to go through again...
very very odd.

But when i ran that particular tracert..it was blocking at the same IP still the one prior hitting the server machine.