Herb Martin
Guest
|
 Posted:
Wed Jan 19, 2005 10:28 pm Post subject:
Re: Choice of DNS version in mixed Windows NT 4 domain Envir |
|
|
"Jason" <Jason@discussions.microsoft.com> wrote in message
news:0C478320-6817-48BA-B462-7F40AA5B9F74@microsoft.com...
| Quote: | I need to get stuck into the DNS software so I know the terminology and
the
software better. I'll get back on the message boards if I get stuck again
(i'm sure that I will
|
One of the best tricks I can show you is in the BUILT-IN HELP:
[ checklist DNS ]
--
Herb Martin
"Jason" <Jason@discussions.microsoft.com> wrote in message
news:0C478320-6817-48BA-B462-7F40AA5B9F74@microsoft.com...
| Quote: | I need to get stuck into the DNS software so I know the terminology and
the
software better. I'll get back on the message boards if I get stuck again
(i'm sure that I will
Thanks Herb
"Herb Martin" wrote:
"Jason" <Jason@discussions.microsoft.com> wrote in message
news:30EDFCE2-C934-4EA9-B2AD-2E45664DF563@microsoft.com...
Thanks Herb
I'll bury my head ina DNS book or 2
That's fine, but most of this stuff is spread over
100s of pages if even included an any DNS book.
You might wish to just ask for a clarification on
anything that isn't clear.
--
Herb Martin
Best Regards
"Herb Martin" wrote:
You're losing me a bit there. My DNS knowledge is limited, but as
long
as
I
know that I have to set up a internal Win 2k DNS server. I''ll
read
up on
DNS and re-read your advice
The DNS server will only be for internal clients to use the
correct
URL
adddress for websites hosted on my DMZ. IIS can then point them to
the
right
area of the web server using Host Headers info
So manually add those (external or DMZ) addresss to the
internal names server IF you are using the same zone name
both internally and externally.
Internal clients must use ONLY your internal DNS name
servers. If the internal name servers are missing records for
external resource in the same zone, the internal server will
STOP looking since it holds the zone (it's authoritative)
and KNOWS there are no other entries (even if it is wrong.)
Thanks
"Herb Martin" wrote:
"Jason" <Jason@discussions.microsoft.com> wrote in message
news:80C1355E-8995-4CAA-8FBF-0DDD1CBFD734@microsoft.com...
Hi Herb
Thanks for your reply:
So, in summary my best option is to
1) set up an internal Win2k DNS server for internal
workstations
to
access
websites on my DMZ
If it is ONLY for thd DMZ it wouldn't be necessary,
but rather setup an internal DNS name server (set)
for ALL internal names and manually add the DMZ
or any other names from your public servers. (This
is so your internal users can reach your own public
servers.)
2) Currently my ISP acts as my registrar's agent, so that
should
work
OK.
I
don't have any complaints with them anyway so I'll leave the
external
internet DNS with them.
That's ok, not quite as good as a quality registrar in MOST
cases, but if you are happy don't move it back to the registrar
until the next time you change ISPs.
--
Herb Martin
Have I understood you correctly?
Thanks again
"Herb Martin" wrote:
"Jason" <Jason@discussions.microsoft.com> wrote in message
news:209E0770-CE82-4351-933A-67E9EA55761E@microsoft.com...
I have set up an IIS web server on my DMZ and I want my
clients
on
the
internal trusted network to access the websites on the
server
using
the
correct domain name www.sitesample.com.
Generally things in your DMZ (for external access)
generally should be in a SEPARATE EXTERNAL
DNS and another Internet DNS (for your internal
users.)
The external DNS is best left at your Registrar in
most cases.
I am currently using my ISP's DNS, so when the web request
is
resolved, my
ISP directs the request to my DMZ.
That is an Ok, method, but in the long run the the
Registrar is a better location for most people than
the ISP.
However, my firewall doesn't allow this
kind of request redirection. The easiest solution is to
install a
DNS
server
to forward the request to the server on the DMZ without
querying
the
ISP's
DNS.
Internal DNS should run on separate completely
INTERNAL DNS servers.
Finally, my question is as I am running a Windows NT4
domain
but
have
Windows 2000 and NT4 servers in the domain, I am wondering
whether
to
use
an
NT4 server's DNS software or a Windows 2000 server's DNS?
If you have a choice, use the Win2000 -- it has better
DNS features and will help you prepare should you ever
upgrade to a Win2000+ domain where the NT4 would be
an issue.
--
Herb Martin
Thanks for any help
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in