asked on 3/8/2017

Specific Web Page does times out

Our network is unable to access bankofamerica.com. They were able to access last week but nobody can access now.
Steps taken to t-shoot

contacted ISP (Windstream) who said that they can hit from router. Confirmed internal DNS servers have the correct windstream auto-forwarders, barracuda has confirmed that there are no policies that are preventing me from going to that site, restarted DNS services, ipconfig/flush/registerdns, added manual DNS server on client (8.8.8.8), checked blacklist (clean),

.
Despite all of this checking out - nobody can access. Request timed out in browser. I have tried different browsers, flushed cache, different machines etc. Tried with or without www and https and http....
We can resolve any subdomain.bankofamerica.com but not the actual site's domain name.

Any other t-shooting steps or insights? Very frustrating,

DNS Networking

Last Comment

datzit

3/21/2017

Dave Baldwin

3/8/2017

What browser are you using? From here, 'bankofamerica.com' automatically redirects to 'https://www.bankofamerica.com/' in Firefox.

masnrock

3/8/2017

Have you tried from the servers themselves? Also, do you get the correct results when doing nslookup?

cnsspd

3/8/2017

can you connect by ip http://171.161.148.150 is the ip

footech

3/8/2017

First test with nslookup whether the name is resolving correctly from a client using your DNS server. If it is, then try a traceroute (often the site isn't set up to respond to a ping, but you can get a feel for whether the traffic is being routed correctly - it can help to compare with the results from another location where you can get to the site).

datzit

3/8/2017

ASKER

Tried using chrome and IE.
I was on the DNS server itself and the page did not display there either.

nslookup results
bankofamerica.com
Non-authoritative answer:
Name: bankofamerica.com
Addresses: 171.161.148.150
171.159.228.150
> www.bankofamerica.com
Non-authoritative answer:
Name: wwwui.ecglb.bac.com
Address: 171.161.206.100
Aliases: www.bankofamerica.com
Addresses: 171.159.228.15
171.161.148.150

interesting entry for the www results...not sure what to make of it..

masnrock

3/8/2017

Nothing to really be made of it. However, I do get the exact same results that you do. However, have you tried the traceroute suggestion? And also, have you tried setting a workstation to only use external DNS servers and NOT any of the internal ones? If that works, try setting a workstation only to use the Windstream (guess I should now be saying CenturyLink) DNS servers. If that doesn't work, you've found your issue. With clients in the past, I've used Google and Level 3 DNS servers over the ISP's DNS servers when circumstances justified it.

datzit

3/8/2017

ASKER

I have set a workstation to use ONLY the 8.8.8.8 google dns servers as well as the windstream dns server...and did the flush/registerdns before trying...I get the same results (page does not load).
I have done a tracert - but the managed router does not seem to allow any tracerts out as they time out after they hit the gateway.
I am unable to get to the site via IP address as requested above as well (I can from another network...just not the one in question here).

masnrock

3/8/2017

What type of firewall or web filtering is in use there?

datzit

3/8/2017

ASKER

barracuda

masnrock

3/8/2017

You might want to take a look at some of the rules in the Barracuda to see if that's impacting things.

datzit

3/8/2017

ASKER

My call into barracuda and their monitoring of their logs against my internal IP address - showed that there is nothing that is preventing me to access the site. That said - I may escalate to re-confirm.
there is a note above by you masnrock - that you state that if this does NOT resolve using the windstream dns servers manually entered into client IP settings....then this will point to Windstream?

masnrock

3/8/2017

If that works, try setting a workstation only to use the Windstream (guess I should now be saying CenturyLink) DNS servers.

You mean this comment? I made an error in the way that I wrote it. I meant to say Level 3, not Windstream. (Couldn't fix when I noticed because you had posted by then)

But regardless, if you're able to use Windstream's DNS servers directly and have no issues, then the problem involves internal DNS. If it works when using Level 3's DNS but not Windstream's, then the problem points to Windstream. However, you've used Google's as the primary (and I assume your nslookup results came from there, not the Windstream server), so that may not be the issue.

datzit

3/8/2017

ASKER

Thank you for that clarification....that makes sense. thank you..
I cannot access when I am using internal DNS, External DNS (Google), and external DNS (Windstream).

masnrock

3/8/2017

What if you were able to connect a computer directly to the internet, not being behind the Barracuda? So it would be configured with a public IP address (and using external DNS servers). If at that point, things work fine. then you know the issue most likely ties to the firewall. If it doesn't work, then you could point directly at Windstream.

datzit

3/8/2017

ASKER

Thanks - I will give that a test. Heading out for the day here - I will test tomorrow and reply then.
thanks for your speedy replies....more to come...

ASKER CERTIFIED SOLUTION

datzit

3/16/2017

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

masnrock

3/16/2017

Sometimes you will end up closing out questions with your answer as the best (with assisted answers if appropriate), explaining out that the issue went away by itself.

datzit

3/16/2017

ASKER

thanks masnrock...

datzit

3/21/2017

ASKER

Issue resolved itself with no action taken by myself or via any of the suggested items.