Re: Is it a DNS problem?
- From: "Richard" <rdumag@xxxxxxxxxxx>
- Date: Thu, 15 Mar 2007 15:48:42 -0700
Thanks Greg. Yes, we can browse and do nslookup from a different ip. I
have Clearchannel's contact info so I'll give them a call. Thank again!
"Greg Lindsay [MSFT]" <greglin@xxxxxxxxxxxxx> wrote in message
news:ex$LzpzZHHA.1220@xxxxxxxxxxxxxxxxxxxxxxx
Hi Richard,
The most likely problem is that your IP address range is on a blacklist
that Clearchannel is using. A way to test this would be to try to nslookup
or browse to those web sites from a different IP address.
--
Greg Lindsay [MSFT]
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
"Richard" <rdumag@xxxxxxxxxxx> wrote in message
news:uLHHCDyZHHA.4000@xxxxxxxxxxxxxxxxxxxxxxx
We have internal and external dns servers (2003). We can browse and do
nslookup on any sites except for sites that are hosted by
"clearchannel.com".
Clearchannel has the following dns and web servers and they host many
radio and tv stations on the same web servers:
dns servers:
dns1.clearchannel.com
dns2.clearchannel.com
ns1.clearchannel.com
ns2.clearchannel.com
web servers:
207.230.150.254
207.230.154.254
207.230.156.254
Here are some of their sites that we cannot get to:
www.kbig104.com
www.foxsports610.com
www.y92.com
www.talk960.com
When we do an nslookup we get the following:
DNS request timed out.
timeout was 2 seconds.
We can get to their sites using our separate dsl line that we use for
testing.
We have no filtering set in our firewall for their ip addresses. Could
this be an issue with our dns? Any help is appreciated. Thanks!
Richard
.
- Follow-Ups:
- Re: Is it a DNS problem?
- From: Richard
- Re: Is it a DNS problem?
- References:
- Is it a DNS problem?
- From: Richard
- Re: Is it a DNS problem?
- From: Greg Lindsay [MSFT]
- Is it a DNS problem?
- Prev by Date: Re: How to disable registering secondary interfce in 2003 DNS
- Next by Date: Re: 2 second time out when using nslook on FQDN
- Previous by thread: Re: Is it a DNS problem?
- Next by thread: Re: Is it a DNS problem?
- Index(es):
Relevant Pages
|
Loading