subdomain added but can't get to site part 2

[DarkShado]

continuation from
http://byet.net/showthread.php?16478...-t-get-to-site

Kevin stop closing the thread this matter isn't resolved. Are you that clueless that
you keep telling me to contact my ISP. This is OUTSIDE OF MY ISPS network!

what part of that don't you seem to understand! Bell is a major network
which stands on its own the same as what AT&T or Level 3 or one of your major
Networks in the USA.

The only connection between Bell and ATT.NET is that they obviously have
some peering agreement in place but that would be about it.

So contacting my ISP is NOT going to help this matter. This is OUTSIDE of my ISPs
network and appears to be on ATT.NET

This is YOUR Job as a Network Admin if one of your IPs is being null routed
by one of the major carriers it is your responsibility to contact that provider
and find out why it is being null routed and resolve the issue.

You do NOT put it back on the user again and tell them to contact their ISP
when their ISP can't do anything about the problem.

This has NOTHING TO do with my ISP It is your responsibility to find out why
ATT.NET has chosen to null route all traffic to that IP. NOT MINE!

My responsibility actually ended when I reported it to u.

I have done more then a typical end user would be able to do in
troubleshooting this problem.

You just don't want the work and are trying to put it back on the end user
to resolve YOUR issues!

[kevin_admin]

My responsibility actually ended when I reported it to u.

our responsibility ends when we see the traces fails before getting to our network, its an access problem for you using your isp, contact them not us.

Kev