Thanks for the response. =)
I've got it working already. All I had to do was stop and restart the
service while I was connected to my ISP. This made the DNS server
auto-detect the available interfaces, which it used to have access outside
my domain.
Will let you know if I have any more problems.
- Danny
----------
> From: Jeff Binkley <jeff.binkley@asacomp.com>
> To: ntisp@emerald.iea.com
> Subject: Re: DNS Problem
> Date: Wednesday, June 11, 1997 8:37 AM
>
> -> >I am using NT's built-in DNS server. Are you sure it can use
NAMED.ROOT ? I
> -> >looked at the contents of NAMED.ROOT and they are the same as those
in the
> -> >DNS server's Cache ( Cache.dns ).
> -> >
> -> >- Danny Sinang
> ->
> -> I will not lie to you, That is one DNS program I have not used, so I
am
> -> afraid I can not be of any further assistance.
>
> I run NT's DNS as a secondary to a Unix primary but there are two files
you
> need to setup: cache.dns and boot. Here is how I started:
>
> Here was my boot file:
>
> ;
> ; DNS boot file
> ;
> ; NOTE: It is NOT necessary to use a boot file to run the DNS server.
> ;
> ; The Microsoft DNS server is capable of reading configuration, zone
> ; and cache information from a "boot" file or from the NT registry.
> ;
> ; To take full advantage of the capabilities of the Microsoft DNS
> ; server we suggest using the DNS Administration tool (dnsadmin.exe).
> ; If you are new to DNS or are setting up a new installation, then we
> ; strongly recommend using the Admin tool, in which case you need not
> ; setup a boot file.
> ;
> ; However, if you are porting an existing BIND DNS installation, then
> ; the DNS server will be able to read your existing boot file. Note,
> ; that the file MUST be named "boot".
> ;
>
> ;
> ; Boot file syntax:
> ;
>
> ;
> ; Interoperation with UNIX DNS servers running BIND:
> ;
> ; Most BIND versions do not accept properly formatted zone transfers
> ; unless they contain only a single resource record in each message
> ; of the zone transfer. This transfer method is grossly inefficient
> ; both in terms of speed and bandwidth. New BIND versions may not
> ; have this bug.
> ;
> ; The Microsoft DNS server will accept (receive) any properly formatted
> ; zone transfer message, and is configured to send in either fashion.
> ; Hence this issue ONLY relates to BIND recieving zone transfers -
> ; i.e. BIND server as a secondary.
> ;
> ; YOU SHOULD CHANGE:
> ; - uncomment BindSecondaries, if have BIND secondaries for
> ; some of your zones
> ; - uncomment NoBindSecondaries, if have ONLY Microsoft or
> ; other non-BIND DNS servers as your secondaries or if
> ; you do not have secondaries for any of these zones
> ;
>
> ;BindSecondaries
>
> ;NoBindSecondaries
>
>
> ;
> ; CACHE FILE
> ;
> ; The "cache" file contains information necessary to contact the ROOT
> ; domain name servers.
> ;
> ; The syntax of this command is:
> ;
> ; cache . <filename>
> ;
> ; YOU SHOULD CHANGE:
> ;
> ; => Nothing - do NOT change this line, if you are NOT a root domain
> ; server.
> ; (Note: if you are not connected to the Internet, be sure and
edit
> ; the cache file to point at the root servers for your intranet.)
> ;
> ; OR
> ;
> ; => Comment out this line, if this DNS server is the ROOT domain
> ; server for a private intranet.
> ;
>
> cach . cache.dns
>
>
> ;
> ; PRIMARY DOMAINS
> ;
> ; "Primary" domains are listed below. The second column is the name of
the
> ; domain for which this name server is authoritative. The third column
is
> ; the name if the database file which contains the authoritative data.
> ;
> ; The syntax of this command is:
> ;
> ; primary <domain> <filename>
> ;
> ; YOU SHOULD CHANGE:
> ; - The names of the domains.
> ; - The names of the database files.
> ; - Comment out domains for which server will be secondary.
> ;
>
> ;primary asacomp.com asacomp.hosts
> ;primary 136.178.199.IN-ADDR.ARPA asacomp.rev
>
>
> ;
> ; SECONDARY DOMAINS
> ;
> ; "Secondary" domains are listed below.
> ;
> ; The syntax of this command is:
> ;
> ; secondary <domain> <master DNS ip address> <filename>
> ;
> ; YOU SHOULD CHANGE:
> ; - The names of the domains.
> ; - The names of the database files.
> ; - The IP address of the primary DNS server (192.255.255.7).
> ; - Uncomment domains for which server will be secondary, then
> ; comment out the primary statement for that domain above.
> ;
>
> secondary asacomp.com 199.178.136.5 asacomp.dns
> secondary 136.178.199.in-addr.arpa 199.178.136.5 199.dns
>
> Here was my cache.dns file:
>
> ;
> ; cache.dns -- DNS CACHE FILE
> ;
> ; Initial cache data for root domain servers.
> ;
> A records for the DNS server authoritative for the
> ; root domain at your site.
> ;
> ; Note, if you are a root domain server, for your own private intranet,
> ; no cache is required, and you may edit your boot file to remove
> ; it.
> ;
>
> ;
> ; Internet root name server records:
> ; last update: Sep 1, 1995
> ; related version of root zone: 1995090100
> ;
>
> ;
> ; formerly NS.INTERNIC.NET
> ;
> . 3600000 IN NS A.ROOT-SERVERS.NET.
> A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
> ;
> ; formerly NS1.ISI.EDU
> ;
> . 3600000 NS B.ROOT-SERVERS.NET.
> B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107
> ;
> ; formerly C.PSI.NET
> ;
> . 3600000 NS C.ROOT-SERVERS.NET.
> C.ROOT-SRVERS.NET. 3600000 A 192.33.4.12
> ;
> ; formerly TERP.UMD.EDU
> ;
> . 3600000 NS D.ROOT-SERVERS.NET.
> D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
> ;
> ; formerly NS.NASA.GOV
> ;
> . 3600000 NS E.ROOT-SERVERS.NET.
> E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
> ;
> ; formerly NS.ISC.ORG
> ;
> . 3600000 NS F.ROOT-SERVERS.NET.
> F.ROOT-SERVERS.NET. 3600000 A 39.13.229.241
> ;
> ; formerly NS.NIC.DDN.MIL
> ;
> . 3600000 NS G.ROOT-SERVERS.NET.
> G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
> ;
> ; formerly AOS.ARL.ARMY.MIL
> ;
> . 360000 NS H.ROOT-SERVERS.NET.
> H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
> ;
> ; formerly NIC.NORDU.NET
> ;
> . 3600000 NS I.ROOT-SERVERS.NET.
> I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
> ;
> ; End of File
>
> I hope this helps.
>
> Jeff Binkley
> ASA Network Computing
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com
>