[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1080
  • Last Modified:

DNS Issue

Hey all,

 Having an issue with internal DNS at a client site. Well, I suspect it is a DNS issue.

 SBS 2008 Domain

 Attempting to get to a website 'control.symform.com' - I just get a 404 error. From outside of our network, it works fine with no issues. I have run a dcdiag /fix, all tests passed. I cannot seem to find an issue,

 Anyone have any ideas?

Thanks!
0
LindsayCole
Asked:
LindsayCole
1 Solution
 
Chris DentPowerShell DeveloperCommented:

Run this and verify the IP Address you get back is correct (and matches the IP you get when used from outside your network):

NsLookup control.symform.com

If that happens to be your AD / SBS domain name then things get tricky.

Chris
0
 
LindsayColeAuthor Commented:
C:\Users\lcole>nslookup control.symform.com
Server:  spartansbs.spartan.local
Address:  192.168.1.2

Non-authoritative answer:
Name:    control-208587495.us-east-1.elb.amazonaws.com
Address:  184.72.95.238
Aliases:  control.symform.com

---------------

I get the same response when I do it from outside the network..
0
 
Chris DentPowerShell DeveloperCommented:

Something is going a bit wrong there then. The 404 response has to come from a web server, and unless you use a Proxy server it's come from the web server for that domain.

Do you use a Proxy?

If not, we're a bit stuck, you could attempt to prove the response comes from there with a packet sniffer, but unless you have some degree of administrative control over the site there's little you can do beyond that.

Chris
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
zazagorCommented:
Have you tried to flush DNS cache:
ipconfig /flushdns

//zaZagor
0
 
LindsayColeAuthor Commented:
Okay, so we do not use a proxy (I'm the Network Admin here).

It isn't a 404 we get, my mistake in saying that.

We get; (in firefox)

Problem Loading Page

Connection Timed Out

The server at control.symform.com is taking too long to respond.
0
 
Mike ThomasConsultantCommented:
So what is happening why you try http://184.72.95.238/ ? load? same error?
0
 
Chris DentPowerShell DeveloperCommented:

Then perhaps try:

telnet control.symform.com 80

If that doesn't connect, and I suspect it won't there's a networking problem somewhere along the path. That may be local to you, or somewhere in between you and them.

Chris
0
 
LindsayColeAuthor Commented:
Mojo: Same error.
0
 
LindsayColeAuthor Commented:
C:\Users\lcole>telnet control.symform.com 80
Connecting To control.symform.com...Could not open connection to the host, on port 80: Connect failed
0
 
LindsayColeAuthor Commented:
What is the best way for me to ascertain if the problem is my network or not?
0
 
Chris DentPowerShell DeveloperCommented:

Watch traffic on the borders of your network and see if the request is allowed out.

If it is, you could always try tracert, relies on ICMP, but it may be allowed, and if it is, it may give an indication of where it's breaking down.

Chris
0
 
LindsayColeAuthor Commented:
ICMP is blocked on their server. Cannot ping them from anywheres.

How would you watch the borders?
0
 
LindsayColeAuthor Commented:
C:\Users\lcole>tracert control.symform.com

Tracing route to control-208587495.us-east-1.elb.amazonaws.com [184.72.95.238]
over a maximum of 30 hops:

  1    <1 ms     6 ms     9 ms  192.168.1.1
  2    12 ms    10 ms    11 ms  loop0-wda.83w.ba12.hlfx.ns.aliant.net [142.176.50.78]
  3    11 ms    11 ms    12 ms  te-0-2-2-0-301.cr01.hlfx.ns.aliant.net [142.176.53.163]
  4    17 ms    13 ms    11 ms  xe-2-0-0.cr02.drmo.ns.aliant.net [142.166.181.142]
  5     *        *        *     Request timed out.

My ISP is Aliant. Looks like I cannot get out of the ISP's network.
0
 
Chris DentPowerShell DeveloperCommented:

Your firewalls / routers, do you have logging capabilities there?

You could watch it on the client, but it won't tell you anything that you don't know (i.e. it doesn't work). And since the routers / firewalls will be the last point you get to handle the traffic it would be nice to ensure all is well there.

Chris
0
 
LindsayColeAuthor Commented:
My edge router is unfortunately only a Cisco/Linksys RV042. Not much in the way of logging.
0
 
Chris DentPowerShell DeveloperCommented:

Hmm that does make it a bit tricky.

Well I recommend you run the Tracert command from both sites anyway. Even if the final hop doesn't respond to ICMP it should show you much of the path and that may highlight a problem.

The result from NsLookup proves it's not DNS at fault, so it's either your own network, or a network between you and them. It's not entirely common, but it's far from being unheard of, that the problem might be one of the intermediate service providers.

Chris
0
 
LindsayColeAuthor Commented:
Chris, when you say both sites, you mean from the server that control.symform.com sits on?
0
 
Chris DentPowerShell DeveloperCommented:

On-site and off-site, sorry.

Do you actually manage the web-service at all? Or is it completely unaffiliated with you?

Chris
0
 
LindsayColeAuthor Commented:
Offsite:
C:\Windows\system32>tracert control.symform.com

Tracing route to control-208587495.us-east-1.elb.amazonaws.com [184.72.95.238]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    49 ms    49 ms    49 ms  142.166.100.89
  3    51 ms    50 ms    91 ms  te-0-4-0-0-200.cr01.stjh.nb.aliant.net [142.166.
211.129]
  4    47 ms    15 ms     7 ms  xe-2-0-0.cr02.stjh.nb.aliant.net [142.166.181.11
0]
  5    51 ms    50 ms    51 ms  te-0-4-1-0.cr01.hlfx.ns.aliant.net [142.166.181.
149]
  6    37 ms    18 ms    51 ms  xe-2-0-0.cr02.drmo.ns.aliant.net [142.166.181.14
2]
  7    71 ms    64 ms    71 ms  xe-2-0-0.bx01.asbn.va.aliant.net [207.231.227.10
]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed -SNIP-

Onsite:

C:\Users\lcole>tracert control.symform.com

Tracing route to control-208587495.us-east-1.elb.amazonaws.com [184.72.95.238]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  192.168.1.1
  2   151 ms    11 ms    11 ms  loop0-wda.83w.ba12.hlfx.ns.aliant.net [142.176.5
0.78]
  3    12 ms    11 ms    11 ms  te-0-2-2-0-301.cr01.hlfx.ns.aliant.net [142.176.
53.163]
  4    15 ms    12 ms    19 ms  xe-2-0-0.cr02.drmo.ns.aliant.net [142.166.181.14
2]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out. -SNIP-

They are completely unaffiliated with us. A potential offsite backup solution.

I called the ISP today, Bell, and they were completely useless just as I expected them to be. Wouldn't even work with me on this issue.
0
 
LindsayColeAuthor Commented:
We never found the solution. However you were very helpful in trying :)
0

Featured Post

Take Control of Web Hosting For Your Clients

As a web developer or IT admin, successfully managing multiple client accounts can be challenging. In this webinar we will look at the tools provided by Media Temple and Plesk to make managing your clients’ hosting easier.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now