🚀 go-pugleaf

i guess you use NT server.  try to edit lmhost file. (I can not remember
exactly, long time ago.)
you might can find help from NT or from internet.  search it.


Morrison wrote:

> Who can give a quick lead how to install DNS in my network.
> I have a NT4.0-network and installed IIS. I'd like clients to be able to use
> names rather than IP-addresses to address local webservers.
>
> Further, our LAN is connected to an ISP for Internet (using NAT), so already
> DNS is installed on clients where it concerns resolving Internet-addresses.
> Obviously, the Intranet is a legal IP-range.
>
> How do I get both working ?
>
> Any tips books on this also appreciated. I couldn't resolve this using
> TCP/Ip from the MCSE course.
>
> Thanks!
>
> Morrison

-

If most of your clients are windows machines, I would suggest using a
WINS server for netbios name resolutions and set the wins clients to use
dns for hostname resolution.  This would cut down on your broadcast
traffic and limit the admin overhead of dns.



Morrison wrote:

> Who can give a quick lead how to install DNS in my network.
> I have a NT4.0-network and installed IIS. I'd like clients to be able
> to use
> names rather than IP-addresses to address local webservers.
>
> Further, our LAN is connected to an ISP for Internet (using NAT), so
> already
> DNS is installed on clients where it concerns resolving
> Internet-addresses.
> Obviously, the Intranet is a legal IP-range.
>
> How do I get both working ?
>
> Any tips books on this also appreciated. I couldn't resolve this using
>
> TCP/Ip from the MCSE course.
>
> Thanks!
>
> Morrison

Hello:

    I would consider the implications to running your own DNS, firstly is this
something that is provided as a free by your ISP. Secondly are you willing to
devote a server and your time to setup and maintain it. Are you aware of the
implications if your DNS server goes down,  ex. would the outside world be able
to get to your site? If you have a public web site and were unaware that your
DNS server was down this could cost you revenue.

    If these are an assigned IP address from your ISP you can have them setup
reverse DNS so you can map IP to address as well - at no additional time or cost
on your part!

Bill

Morrison wrote:

> Who can give a quick lead how to install DNS in my network.
> I have a NT4.0-network and installed IIS. I'd like clients to be able to use
> names rather than IP-addresses to address local webservers.
>
> Further, our LAN is connected to an ISP for Internet (using NAT), so already
> DNS is installed on clients where it concerns resolving Internet-addresses.
> Obviously, the Intranet is a legal IP-range.
>
> How do I get both working ?
>
> Any tips books on this also appreciated. I couldn't resolve this using
> TCP/Ip from the MCSE course.
>
> Thanks!
>
> Morrison

The following is an example of how my Microsoft DNS is  setup (remember to
point the DNS of the workstations to the DNS host!):

DNS host

168.148.3.1		
    cache
    0.in-addr.arpa		-auto genned
    127.in-addr.arpa	-auto genned
    255.in-addr.arpa	-auto genned
    3.148.168.in-addr.arpa			-reverse DNS
    mydomain.com			- primary zone
       mydomain.com     A               168.148.3.001
       mydomain.com     NS            hostname.mydomain.com
       mydomain.com     SOA         hostname.mydomain.com
       hostname               A               168.148.3.001
       hostname               MX            [10]    mail.mydomain.com
       mail                         CNAME             mydomain.com
       www                        CNAME             mydomain.com
      ns1                           CNAME             mydomain.com


For more info get:
Windows NT Server 4   Professional Reference   Second Edition
by Karanjit Siyan from New Riders          
also
DNS and Bind

Hope this helps
Charles Butler

"Morrison" <haveacigar@hotmail.com> wrote:

>Who can give a quick lead how to install DNS in my network.
>I have a NT4.0-network and installed IIS. I'd like clients to be able to use
>names rather than IP-addresses to address local webservers.
>
>Further, our LAN is connected to an ISP for Internet (using NAT), so already
>DNS is installed on clients where it concerns resolving Internet-addresses.
>Obviously, the Intranet is a legal IP-range.
>
>How do I get both working ?
>
>Any tips books on this also appreciated. I couldn't resolve this using
>TCP/Ip from the MCSE course.
>
>Thanks!
>
>Morrison
>

In <364d7b84.48248871@206.214.99.8> guru@ix.netcom.com.no.spam.maam writes:

>The following is an example of how my Microsoft DNS is  setup (remember to
>point the DNS of the workstations to the DNS host!):

>DNS host

>168.148.3.1		
>    cache
>    0.in-addr.arpa		-auto genned
>    127.in-addr.arpa	-auto genned
>    255.in-addr.arpa	-auto genned
>    3.148.168.in-addr.arpa			-reverse DNS
>    mydomain.com			- primary zone
>       mydomain.com     A               168.148.3.001
>       mydomain.com     NS            hostname.mydomain.com
>       mydomain.com     SOA         hostname.mydomain.com
>       hostname               A               168.148.3.001
>       hostname               MX            [10]    mail.mydomain.com
>       mail                         CNAME             mydomain.com
>       www                        CNAME             mydomain.com
>      ns1                           CNAME             mydomain.com


Assuming this is correct then you can not register your domain with
nominet (all top level .uk domains). They state you must have two active
DNS servers. Just 1 server means no registration, period.

Even worse this configiration *VIOLATES THE INTERNET HOST
REQUIREMENTS*. mail.mydomain.com is a CNAME record and is used an
MX. MX records *MUST* use canonical host names. sendmail will handle
this misconfiguration, fortunately for you.

Further there are bad things about this configuration anyway. The A
record for mydomain.com is a probably mistake---mydomain.com probably
should be not a computer name. There are missing records that the SOA
needs (mail addr and serial, just as a start).

Here is edited DNS information from a secondary DNS server. The IP
numbers and names have been modified. The server runs bind 8.1.2 which
has support for dynamic upodate support, change notification, improved
zone transfers and per domain access control. There is a patch for DNS
SEC if you want that support (the KEY and SIG records, plus a sig
record generator). IPv6 AAAA records are also supported.

; BIND version named 8.1.2 Tue Jun 23 21:53:04 BST 1998
; BIND version root@munin:/u6/lssd/bld/bind-8.1.2/src/bin/named
; zone 'secretdom.co.uk'   last serial 98111303
$ORIGIN co.uk.
secretdom       IN      SOA     ns.secretdom.co.uk. private.secretdom.co.uk. (
                98111304 1000 3600 604800 86400 )
                IN      NS      ns.secretdom.co.uk.
                IN      NS      ns.anotherdom.net.
                IN      NS      ns.yetanotherdom.co.uk.
                IN      MX      10 mx1.secretdom.co.uk.
                IN      MX      20 relay1.secretdom.co.uk.
$ORIGIN secretdom.co.uk.
smtp            IN      A       127.42.63.3
papua           IN      A       127.42.63.9
news            IN      A       127.42.63.252
fiji            IN      A       127.42.63.1
dialup1         IN      A       127.42.63.1
hosting         IN      CNAME   web1.secretdom.co.uk.
mx1             IN      A       127.42.63.2
pop             IN      A       127.42.63.2
web1            IN      CNAME   solomon.secretdom.co.uk.
solomon         IN      A       127.42.63.10

and of course 127.42.63.2 needs multiple PTR records (one per name).
The domain in question is in the co.uk domain and the names are
real. All unix hosts run sshd of course.

The real domain name is registered with nominet. Bar the editing and
reducing the number of hosts this information is provided neat. smtp
and pop could be CNAMEs.

Read a few RFCs before setting up your DNS and do it correctly.

Duncan (-:

I am sure you are using either a firewall app or a proxy server to protect
your intranet from the internet, right?

If not, please post the URL of you web server soI can get you fired in about
5 minutes.

Your intranet SHOULD NOT BE ON A LEGAL ROUTABLE NETWORK. That is sheer
lunacy. Put yor intranet on a private network where it belongs and you are
another step closer to keeping your job. When you use a firewall, like
checkpoint, you tell it how to handle inbound traffic. So...when traffic
goes to your 1 legal IP address (the one your ISP gives you) it will look at
the port on which the request is being made. If the call is to port 80 (web
traffic, go to 192.168.0.56, the intranet webserver), if it is 21 (ftp
traffic, send it to 192.168.0.87, the ftp server) you get the idea. It gets
much more complicated from here. Say you have more than one web server, or
you have multiple Exchange bridgehead servers....it gets more tricky. Now
you are getting into scenarios where you need to have your own DNS that
shares the firewall so you can do load balancing with MX records and
stuff.......

Keep it simple. Use a firewall or an application that supports inbound NAT
or proxying, like checkpoint or MS Proxy 2.0.

But if you do nothing else, get your network off the internet....otherwise
you are asking for BIG TROUBLE!


Good luck,

Todd

PS> what was that URL...


Bill Tucek wrote in message <364A4FA6.A6531C9E@midtel.net>...
>Hello:
>
>    I would consider the implications to running your own DNS, firstly is
this
>something that is provided as a free by your ISP. Secondly are you willing
to
>devote a server and your time to setup and maintain it. Are you aware of
the
>implications if your DNS server goes down,  ex. would the outside world be
able
>to get to your site? If you have a public web site and were unaware that
your
>DNS server was down this could cost you revenue.
>
>    If these are an assigned IP address from your ISP you can have them
setup
>reverse DNS so you can map IP to address as well - at no additional time or
cost
>on your part!
>
>Bill
>
>Morrison wrote:
>
>> Who can give a quick lead how to install DNS in my network.
>> I have a NT4.0-network and installed IIS. I'd like clients to be able to
use
>> names rather than IP-addresses to address local webservers.
>>
>> Further, our LAN is connected to an ISP for Internet (using NAT), so
already
>> DNS is installed on clients where it concerns resolving
Internet-addresses.
>> Obviously, the Intranet is a legal IP-range.
>>
>> How do I get both working ?
>>
>> Any tips books on this also appreciated. I couldn't resolve this using
>> TCP/Ip from the MCSE course.
>>
>> Thanks!
>>
>> Morrison
>