DNS error

  • Thread starter Thread starter Carmen
  • Start date Start date
C

Carmen

when i perform a nslookup it comes back with:cant find
server name or address. 172.17.5.29 unavaible
default server:unknown
address: 172.17.5.29

the forwarder is setup pointing the a linksys router
(192.168.1.1) which is the isp. I dont understand if this
is a broken delegation or what can someone help.
 
In
Carmen said:
when i perform a nslookup it comes back with:cant find
server name or address. 172.17.5.29 unavaible
default server:unknown
address: 172.17.5.29

the forwarder is setup pointing the a linksys router
(192.168.1.1) which is the isp. I dont understand if this
is a broken delegation or what can someone help.
Click to expand...

You do not have a PTR record for that IP address in your DNS server.
 
Make sure your reverse lookup zone(s) are working.
NSLOOKUP deals stricly with these zones.
ajd
 
im not too confident on how to go about and add the
pointer to the reverse lookup zone. some assistance if
possible?
 
also would the pointer address be that of the forwarder or
that of the DNS server IP. and is the forwarder IP
address that of the Linksys router(192.168.1.1) or the
internal DNS of the Linksys. Im lost on this

Thank you.
i know this is a bit vague sorry
 
I think this is more in detail of my issue:

This is the situation. I have a 4 port linksys cable
router w/ of course a built in 10/100 switch. I have
twenty machines on it now 2000 pro,98se and a 2000 server
as my DC,DNS and active directory. I also have another
router in the network 172.17.5.30. My setup as far as ip
addresses are as follows: all the machines are .2-20 I
made the gateway the ip of the server to each client and
the DNS is to the Name of the DNS SERVER. I want the dns
to handle any request to internet which is to the Linksys
router and the DNS is that of the SERVER ADDRESS
172..17.5.29.. What I want to do is setup this Windows
2000 server so that it runs a DNS server along with Active
Directory. Currently I have the Default Gateway of the
Server pointing to the Linksys router and I changed the
routing table of the Server to the other Router. Because
of the Pointer that I didn't put into the Reverse lookup
zone would that be the case that my dns isn't resolving
the request to the Linksys that I put as the Forwarder.
 
In
CARMEN said:
I think this is more in detail of my issue:

This is the situation. I have a 4 port linksys cable
router w/ of course a built in 10/100 switch. I have
twenty machines on it now 2000 pro,98se and a 2000 server
as my DC,DNS and active directory. I also have another
router in the network 172.17.5.30. My setup as far as ip
addresses are as follows: all the machines are .2-20 I
made the gateway the ip of the server to each client and
the DNS is to the Name of the DNS SERVER. I want the dns
to handle any request to internet which is to the Linksys
router and the DNS is that of the SERVER ADDRESS
172..17.5.29.. What I want to do is setup this Windows
2000 server so that it runs a DNS server along with Active
Directory. Currently I have the Default Gateway of the
Server pointing to the Linksys router and I changed the
routing table of the Server to the other Router. Because
of the Pointer that I didn't put into the Reverse lookup
zone would that be the case that my dns isn't resolving
the request to the Linksys that I put as the Forwarder.
Click to expand...




Search for the section on how to create a reverse zone. Then create a PTR
for your DNS server, give it the IP and then the name and this message when
using nslookup will go away. Yes, it's just a message and NOT an error.

308201 - HOW TO Create a New Zone on a DNS Server in Windows 2000:
http://support.microsoft.com/?id=308201

Everything else seems fine. You;re clients are only using your DNS sever,
which is good. Forwarding is set, which is good. Of course the gateway has
to be the router, otherwise they can't get to the Internet. As far as
multiple routers which implies you have mutliple subnets, keep in mind that
default gateway ALWAYS points towards the door (Internet). You would
configure static routes on your routers to be able to communicate to the
other subnets.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
You would
configure static routes on your routers to be able to
communicate to the
other subnets.


What do you mean by this?
 
sent this to the wrong post sorry
can i set the default gateway to all clients pointing to
my other router and have them resolve the linksys router
through dns? which all clients would have to resolve.
Wouldnt that be possible once i have my pointer setup?

How should that look: DNS:Forwarder should have the
Linksys ip:192.168.1.1 or the INTERNAL DNS?

Each client should have the prefered DNS: 172.17.5.29 and
the name of the DNS SERVER correct?

Also the Server shouldnt the server have its Default
gateway pointing to the other server and have it resolve
the internet by goin to the DNS also?

Thank You so much, just a bit confused.
 
sent this to the wrong post sorry
can i set the default gateway to all clients pointing to
my other router and have them resolve the linksys router
through dns? which all clients would have to resolve.
Wouldnt that be possible once i have my pointer setup?
Click to expand...

No. You need to all point to the one gateway, normally we select the one
pointing towards the door. This is a network design fact.

Analogize that to as if you are sitting in a building. You are in a room.
There is one door in the room. You *know* that door is the doorway to get
out of the building. Of course you also know that you have to walk down the
hall to the main door to get out of the building. You know this, just by
visualizing it. If there were two doors in the room, how do you know which
one is the way out? Well, once again, you know which door it is.

That can be looked at as the same as a computer sitting on the network with
two gateways out. How does it know which is the way out? It doesn't, you
have to tell it. So you give it the one gateway, the gateway pointing out.
If you want to get to the other door in the room, say that's the door to get
to 192.168.1.0, and it's IP is 172.16.0.2, and your computer is sitting on a
172.16.0.0 netowork, with it's IP 172.16.0.52, then the packet is sent to
the main gateway anyway first, which in this case we'llk say 172.16.0.1,
where we create a rule on that router saying that to get to 192.168.1.0 ,
we'll send all the packets to 172.16.0.2 and let that router handle it.

Ace
 
Thank you for your explanation it was very insightful and
made sense to me. But I can not go in and change the
router settings to point to the other gateway. the linksys
is a third party that wasnt purchased from me so we would
like to keep the server to act as the router if possible

Thanks i know this is just a pain.
 
But you can't have two gateways on any machine. You'll have to talk to the
person that adminsters the Linksys and explain what you are trying to do.
They will be able to help you out.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Carmen said:
So the Dns server can not have the forward to the linksys?
Click to expand...

No, forward to your ISP. The Linksys router is NOT a DNS server. Make sure
since you have AD that you don;t point to the Linksys for DNS either. Not
sure if I mentioned that earlier or not, since this thread has grown, but
just wanted to reiterate that. Also, that wouldn't be the cause of the
nslookup messages you orignally stated and thought were errors.

Ace
 
I should just change the configuration of the Linksys
router and make it join the 172.17.5.0 network correct?


thank you very much ACE you ve been a great help.
this is the first network ive done just seem to second
guess myself constatly
 
In
Carmen said:
I should just change the configuration of the Linksys
router and make it join the 172.17.5.0 network correct?
Click to expand...

Actually just leave the router alone. All you want it to do is connect your
network to the Internet, which it's already doing, it's routing. :-)
Nothing else to do on it, just leave it alone. Your machines only reference
to the router should only be the gateway address in their IP properties,
nothing else.
thank you very much ACE you ve been a great help.
this is the first network ive done just seem to second
guess myself constatly
Click to expand...

That's why it's good to ask questions!
:-)

Ace
 
yes they do access the internet but then they dont access
the other router. they should access both routers.
 
In
Carmen said:
yes they do access the internet but then they dont access
the other router. they should access both routers.
Click to expand...
Let me get this straight. You have two routers. One is for Internet access,
the other is for another subnet in yuor network? Or is the other for
Internet access also?

If the second router is for an internal subnet, then as I said, it sounds
like you need to create a static route to access the other router.

If the other is for Internet access for a failover in case the first goes
down, then it would be either beneficial to get a router with mutliple
interfaces to allow you to change the default gateway on the router or maybe
the dead gateway detection feature. I haven't used this, but here are some
articles on it.

(for NT, but the idea is the same):
http://support.microsoft.com/default.aspx?scid=kb;en-us;205027

http://support.microsoft.com/default.aspx?scid=kb;en-us;299540

Sorry, can't find too many articles on this one.

At this point I have exhausted all possible suggestions on this. This part
is basically straying away from a DNS issue but rather becoming a network
design issue.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
NSLOOKUp tries to perform a reverse lookup against the IP address of your DNS server. If it's unable to do this, it returns that error. This isn't a critical error
and can be safely ignored. NSLOOKUP will work even though it cannot get the PTR record for you DNS server. No big deal.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
Back
Top