Name Resolution question

  • Thread starter Thread starter Chris Hall
  • Start date Start date
C

Chris Hall

Good afternoon,

We are running A.D. on Win2000 network and at this point have a small
implementation. We have 13 physical locations, three of which have DCs and
the others with Neware 5.1. We have all clients pointing to the DCs for name
resolution and all of the appropriate records are recorded. Users on remote
networks are having problems trying to connect to our Intranet server. They
connect fine after we remote control into their machines and ping the server
by name. This doesn't happen on the network where the webserver is located.
All clients are either w2k (sp4) or xp.(sp2). It would appear that the
queries are timing out. Outside of implementing host files, any suggestions?
 
Good afternoon,

We are running A.D. on Win2000 network and at this point have
a small
implementation. We have 13 physical locations, three of which
have DCs and
the others with Neware 5.1. We have all clients pointing to
the DCs for name
resolution and all of the appropriate records are recorded.
Users on remote
networks are having problems trying to connect to our Intranet
server. They
connect fine after we remote control into their machines and
ping the server
by name. This doesn't happen on the network where the
webserver is located.
All clients are either w2k (sp4) or xp.(sp2). It would appear
that the
queries are timing out. Outside of implementing host files,
any suggestions?
Click to expand...

You could run a DNS server on the remote networks, which just farward
the DNS of the primary DNS server. Once you get that to contact the
primary DNS, there should be no problems with the clients talking to
the DNS fawarder.
 
Chris Hall said:
Good afternoon,

We are running A.D. on Win2000 network and at this point have a small
implementation. We have 13 physical locations, three of which have
DCs and the others with Neware 5.1. We have all clients pointing to
the DCs for name resolution and all of the appropriate records are
recorded. Users on remote networks are having problems trying to
connect to our Intranet server. They connect fine after we remote
control into their machines and ping the server by name. This doesn't
happen on the network where the webserver is located. All clients are
either w2k (sp4) or xp.(sp2). It would appear that the queries are
timing out. Outside of implementing host files, any suggestions?
Click to expand...

How do the remote networks get name resolution for the Intranet server?
 
Kevin D. Goodknecht Sr. said:
How do the remote networks get name resolution for the Intranet server?
Click to expand...
They get name resolution from one of the three remote dns serves. I do not
have a dns server in each location, as some are Netware servers and it's
likely we will migrate them to windows servers next year.
 
in message

They get name resolution from one of the three remote dns
serves. I do not
have a dns server in each location, as some are Netware
servers and it's
likely we will migrate them to windows servers next year.
Click to expand...

Dose it matter that they are netware servers?
I go to a college that uses Novel Open Enterprise servers, and they
have an ordinary DNS, I don’t see why you carnt set up another DNS
at each location, and tell them to use the main DNS as there server,
and then go on to configure the clients at each location, of course.
 
Chris Hall said:
They get name resolution from one of the three remote dns serves. I
do not have a dns server in each location, as some are Netware
servers and it's likely we will migrate them to windows servers next
year.
Click to expand...
Each site should have a DNS server local to it.
On one of the Windows DNS servers, on the zone for your AD domain, allow
zone transfers to the Netware servers, then create a secondary for the AD
zone on the Netware DNS. Be aware though, the Default zone expire time on
Windows DNS is one day, I would certainly increase this to at least a week.
 
In
Chris Hall said:
They get name resolution from one of the three remote dns serves. I
do not have a dns server in each location, as some are Netware
servers and it's likely we will migrate them to windows servers next
year.
Click to expand...

Other than the latest Netware version, the older version's DNS cannot
support AD's required SRV records. I know Kevin suggested to create a
secondary, but I'm not entirely sure Netware DNS will support a zone
transfer and allow to transfer and support the SRV resource type records.

Kevin, do you know if it will work?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
 
Ace Fekay [MVP]
In

Other than the latest Netware version, the older version's DNS cannot
support AD's required SRV records. I know Kevin suggested to create a
secondary, but I'm not entirely sure Netware DNS will support a zone
transfer and allow to transfer and support the SRV resource type
records.

Kevin, do you know if it will work?
Click to expand...

Not without knowing what version he's using, It may not support SRV records,
he could also use a stub zone. But, I don't know when BIND added support for
Stub Zones.
 
In
Kevin D. Goodknecht Sr. said:
Not without knowing what version he's using, It may not support SRV
records, he could also use a stub zone. But, I don't know when BIND
added support for Stub Zones.
Click to expand...

He's using Netware 5.1. I know it doesn't support SRVs, but not sure if it
will take a transfer from another DNS that does have SRV record types in the
zone. My guess is no.

As far as Stubs for BIND, I think back to 8.3, but not sure.

Ace
 
Thanks Ace & Kevin! I think I may just try to speed up the migration;->
Chris

"Ace Fekay [MVP]"
 
Back
Top