|
|
I am running DNS servers to serve an internet domain name. 2 servers
running Server 2003 SP2. Each server is a different nameserver record on
the domain name.
It works fine and responds to requests - for example typing www.domain.com
redirects to the resource I have assigned the A record of www to. And
changes to the records (they have a short TTL) reflect online, so I know it
is working in that respect.
However, if I try and do an NSlookup against the domain name from outside of
our network it times out (DNS request timed out).
Any ideas why this might be?
Thanks
|
|
I'm sorry but I don't follow what is working and what isn't. You haven't
defined the scenario where it is working. Are you doing this internally and
have an internal resource resolving it for you? What about externally?
Please try and as complete as you can describe the topologies and where you
are having success and failure.
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
"K" <no[ at ]spam.net> wrote in message
news:%230PQX7GWJHA.1188[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] >I am running DNS servers to serve an internet domain name. 2 servers
>running Server 2003 SP2. Each server is a different nameserver record on
>the domain name.
>
> It works fine and responds to requests - for example typing www.domain.com
> redirects to the resource I have assigned the A record of www to. And
> changes to the records (they have a short TTL) reflect online, so I know
> it is working in that respect.
>
> However, if I try and do an NSlookup against the domain name from outside
> of our network it times out (DNS request timed out).
>
> Any ideas why this might be?
>
> Thanks
>
|
|
Sorry, I'll try and explain better.
We have an internet registered domain name which we use for our website.
This is held by our ISP but the name server records point to DNS servers
which are hosted in our DMZ so we can manage the zone ourselves.
If you type www.domain.com from the internet, our DNS servers respond and
give out the IP address to reach our server with. This works fine (port 53
open between DNS server and internet).
However, if you do an nslookup from the internet and try and view any
records associated with the zone you get a message which says: "DNS request
timed out".
[Quoted Text] > I'm sorry but I don't follow what is working and what isn't. You haven't
> defined the scenario where it is working. Are you doing this internally
> and have an internal resource resolving it for you? What about
> externally? Please try and as complete as you can describe the topologies
> and where you are having success and failure.
>
>>I am running DNS servers to serve an internet domain name. 2 servers
>>running Server 2003 SP2. Each server is a different nameserver record on
>>the domain name.
>>
>> It works fine and responds to requests - for example typing
>> www.domain.com redirects to the resource I have assigned the A record of
>> www to. And changes to the records (they have a short TTL) reflect
>> online, so I know it is working in that respect.
>>
>> However, if I try and do an NSlookup against the domain name from outside
>> of our network it times out (DNS request timed out).
>>
>> Any ideas why this might be?
>>
>> Thanks
>>
>
|
|
This sounds pretty normal if I understand you correctly. If you right click
on the zone and select properties, under the Name Servers tab you should
find the Name servers and there associated IP addresses. I assume that
looks correct.
When you do an nslookup are you providing the fqdn?
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
"K" <no[ at ]spam.net> wrote in message
news:e$5wjpdWJHA.1528[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > Sorry, I'll try and explain better.
>
> We have an internet registered domain name which we use for our website.
> This is held by our ISP but the name server records point to DNS servers
> which are hosted in our DMZ so we can manage the zone ourselves.
>
> If you type www.domain.com from the internet, our DNS servers respond and
> give out the IP address to reach our server with. This works fine (port
> 53 open between DNS server and internet).
>
> However, if you do an nslookup from the internet and try and view any
> records associated with the zone you get a message which says: "DNS
> request timed out".
>
>
>> I'm sorry but I don't follow what is working and what isn't. You haven't
>> defined the scenario where it is working. Are you doing this internally
>> and have an internal resource resolving it for you? What about
>> externally? Please try and as complete as you can describe the topologies
>> and where you are having success and failure.
>>
>>>I am running DNS servers to serve an internet domain name. 2 servers
>>>running Server 2003 SP2. Each server is a different nameserver record on
>>>the domain name.
>>>
>>> It works fine and responds to requests - for example typing
>>> www.domain.com redirects to the resource I have assigned the A record of
>>> www to. And changes to the records (they have a short TTL) reflect
>>> online, so I know it is working in that respect.
>>>
>>> However, if I try and do an NSlookup against the domain name from
>>> outside of our network it times out (DNS request timed out).
>>>
>>> Any ideas why this might be?
>>>
>>> Thanks
>>>
>>
>
>
|
|
In news:e$5wjpdWJHA.1528[ at ]TK2MSFTNGP03.phx.gbl,
K <no[ at ]spam.net> requesting assistance, typed the following:
[Quoted Text] > Sorry, I'll try and explain better.
>
> We have an internet registered domain name which we use for our
> website. This is held by our ISP but the name server records point to
> DNS servers which are hosted in our DMZ so we can manage the zone
> ourselves.
> If you type www.domain.com from the internet, our DNS servers respond
> and give out the IP address to reach our server with. This works
> fine (port 53 open between DNS server and internet).
>
> However, if you do an nslookup from the internet and try and view any
> records associated with the zone you get a message which says: "DNS
> request timed out".
When running an nslookup from the outside world, are you simply typing in
the FQDN of the domain, (As Paul had asked) such as domain.com, or are you
typing in www.domain.com?
What DNS servers are you using when you are running the nslookup from the
outside world? You can change server reference in nslookup by typing in:
server <ip of a DNS server>
Try changing it to your own server and re-run it.
Also, can you copy and paste an nslook session with the results so we can
take a closer look, please?
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
|
|
|