Re: Is it a DNS problem?
- From: "Greg Lindsay [MSFT]" <greglin@xxxxxxxxxxxxx>
- Date: Fri, 16 Mar 2007 18:43:25 -0700
That is an important result that you can get to their DNS servers using
telnet. Apparently there isn't a firewall blocking you as I suspected.
Try setting debug on nslookup and see what you get.
c:\> nslookup <return>
set d2 <return>
www.y92.com 207.230.144.18
This should give you some3 helpful debug information. You can also increase
the timeout with "set timeout=100" and see if this makes a difference.
To see all the options, type a "?" at the > prompt. To disable debug, you
would type "set nod2" then "set nodebug", etc.
This might just be a timeout problem. Do you have forwarders set up? Adding
the authoritative servers as forwarders for these specific domains might
solve your problem.
--
Greg Lindsay [MSFT]
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
"Richard" <rdumag@xxxxxxxxxxx> wrote in message
news:uz4tYGBaHHA.4520@xxxxxxxxxxxxxxxxxxxxxxx
Hi Greg,
I did the telnet command and can connect to all four of their dns servers
in an instant. We have a dsl line the we use for testing from the same
ISP and we can get to Clearchannel websites. So I'm assuming that our ISP
can get to their websites as well. Will probably give them a call and ask
anyway.
Back to the telnet command, since I can connect to their dns, is there
anything else I should try? Thanks for your assistance!
Richard
"Greg Lindsay [MSFT]" <greglin@xxxxxxxxxxxxx> wrote in message
news:OJk19$$ZHHA.5032@xxxxxxxxxxxxxxxxxxxxxxx
That is probably a result of the DNS timeout.
Try a telnet to port 53. If you just time out, then either there is a
firewall blocking you, or a routing problem. See below for an example.
C:\>telnet dns1.clearchannel.com 53
-- or --
C:\>telnet 207.230.136.193 53
When I do this, it connects and then the screen clears. To disconnect,
hit return.
If it just sits trying to connect, this is usually a firewall or access
list blocking the source or destination. It could also be a routing
problem, but this is less probable. I tried to verify routing to this DNS
server, but ICMP is blocked along the path. I would at least check
routing with tracert to make sure you can get off your LAN when you try
to traceroute to clearchannel.
It may still be a blacklist, but one that is used by an ISP between you
and clearchannel. It might be a good idea to call your ISP's support and
ask if they can get to clearchannel. If they don't have a problem, this
would narrow it down quite a bit.
--
Greg Lindsay [MSFT]
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
"Richard" <rdumag@xxxxxxxxxxx> wrote in message
news:OQf5PV$ZHHA.208@xxxxxxxxxxxxxxxxxxxxxxx
Hi Greg,
I called Clearchannel and they said our ip address is not on their
blacklist. So the ball is back on our end. One thing I noticed on our
dns servers is that eventhough there are entries in the cached lookups
for their sites, they only show dns info....nothing for host(A). Other
cached lookups show both dns and host info.
Any idea? Thanks!
Richard
"Richard" <rdumag@xxxxxxxxxxx> wrote in message
news:eLVHYQ1ZHHA.4396@xxxxxxxxxxxxxxxxxxxxxxx
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]
- Re: Is it a DNS problem?
- From: Richard
- Re: Is it a DNS problem?
- From: Richard
- Re: Is it a DNS problem?
- From: Greg Lindsay [MSFT]
- Re: Is it a DNS problem?
- From: Richard
- Is it a DNS problem?
- Prev by Date: Re: How to disable registering secondary interfce in 2003 DNS
- Next by Date: Re: SOA Serial Number out of sync - OK to change?
- Previous by thread: Re: Is it a DNS problem?
- Next by thread: Re: Is it a DNS problem?
- Index(es):
Relevant Pages
|
