TO KEN: or anyone else who know anything about BIND and WIN NT
Gregory EISENBERG
Dear whomever may get this
I am struggling to perform some systems admin tasks on Win NT 3.51
which I never had trouble with on UNix machines before. The problem is
BIND and DNS
our Domain is ycs.net,
205.236.152.8 is our DNS aptley named NS
205.236.152.2 is our world wide web server called www
(there are two Netscape Enterprise servers running on this machine
one called prime - bound to port 443 is a secure server and
one called www - is bound to port 80 is the common server)
I am trying to map another domain name to 205.236.152.2 and this is the
problem - ie I am trying to set up a virtual server
(I used to use Microsofts Internet Imformation server with the same BIND
package and WinNT 3.51 just fine and did this very same task several times
- but that was at another place of employment - here they are using
Enterprise Server )
We want to call 205.236.152.2 www.baronsport.com as well as what is
already known as
I have properly set up a virtual server, using Enterprise Server 2.0 - I followed the manual to the "T" - all 2 pages on virtual servers! The virtual server is running on www. I set up the vitual host name -
www.baronsport.com - and linked it to it's proper home directory.
to test it worked, I force another computer in the lan to
know where www.baronsport.com is - by adding an entry into the
winnt\system32\drivers\etc\hosts file - the virtual server picks up and sends me to the right directory - hence the virtual server
is not the problem - but that was static routing
If from anywhere where the domain name must be resolved tries to get at
www.baronsport.com they get no DNS entry.
So what have I done to the BIND files ie ycs.host and ycs.rev? I will show
you both in a moment
A note: the ycs.host and ycs.rev files are properly loaded by DNS as I
have checked the event log very carefully and can fully tell that
that the DNS loads the database with out errors and the DNS
properly resolves other addresses.
so here is the ycs.host the file
------------------------------------------------------------------
;ycs.hosts:
;or domain mappings!
@ IN SOA ns.ycs.net. root.ycs.net. (
1996121399 ; serial number
43200 ; refresh every 12 hours
7200 ; retry after 2 hours
1209600 ; expire after 2 weeks
172800) ; default ttl is 2 days
;
IN NS ns.ycs.net.
IN NS jupiter.worldlinx.com. ; our secondary NS
localhost IN A 127.0.0.1
ns IN A 205.236.152.8
prime IN A 205.236.152.2
www IN A 205.236.152.2
hero IN A 205.236.152.3
homer IN A 205.236.152.5
baron IN A 205.236.152.2
www.baron.com IN CNAME baron
;baron.com IN CNAME baron
----------------------------------------------------------------
another note - from what I understand the only computer on our lan
which is internet visible is our DNS 205.236.152.8
So it is our DNS which points the query for home.ycs.net to the proper IP
and I can do nslookup on homer.ycs.net from anywhere and get an answer
Also as I understand it we did register www.baronsport.com to be assigned to
205.236.152.8 So an internet query for baronsport should hit our DNS
which will then point it to the computer which has the virtual server on
it - namely www
Anyway I appreciate you reading all of this
If you know where my mistake is please write me!!
Oh yeah the .rev file I am sure is okay the only thing you might be
interested to know is that I only use one reference to baronsport in the
rev file
baronsport IN PTR www.ycs.net.
no reference for the CNAME as I understand there should not be
Thanx again
-----------------------------------------------------------------------------
GREGORY A EISENBERG
te...@cs.mcgill.ca Computer Science Student / Music Freak
http://www.cs.mcgill.ca/~tele
President of DynaCom -> Dynamic Computer Solutions
"She is descended from a long line that her mother listened to."
-- Gypsy Rose Lee
Thu Apr 3 00:32:36 EST 1997
Cricket Liu
>;ycs.hosts:
>;or domain mappings!
>
>@ IN SOA ns.ycs.net. root.ycs.net. (
> 1996121399 ; serial number
> 43200 ; refresh every 12 hours
> 7200 ; retry after 2 hours
> 1209600 ; expire after 2 weeks
> 172800) ; default ttl is 2 days
>;
> IN NS ns.ycs.net.
> IN NS jupiter.worldlinx.com. ; our secondary NS
>
>localhost IN A 127.0.0.1
>ns IN A 205.236.152.8
>prime IN A 205.236.152.2
>www IN A 205.236.152.2
>hero IN A 205.236.152.3
>homer IN A 205.236.152.5
>
>baron IN A 205.236.152.2
>www.baron.com IN CNAME baron
This record is in the wrong file. As written, it's interpreted as
www.baron.com.ycs.com (it's missing a trailing dot). What you meant
is
and even then, it's in the wrong file, since this file describes
ycs.net. You need to create another zone data file for baron.com and
instruct the server to load it with a primary directive.
>;baron.com IN CNAME baron
Ditto for this. Also, baron.com, once set up correctly, can't be a
CNAME, since it'll have an SOA record and multiple NS records. You
should use an A record instead.
>Also as I understand it we did register www.baronsport.com to be assigned to
>205.236.152.8 So an internet query for baronsport should hit our DNS
>which will then point it to the computer which has the virtual server on
>it - namely www
baronsport.com is indeed delegated to ns.ycs.net and
ns1.bellglobal.com, but neither server seems to know anything about
it. (ns.ycs.net doesn't respond, and ns1.bellglobal.com responds with
a SERVFAIL error.)
>Oh yeah the .rev file I am sure is okay the only thing you might be
>interested to know is that I only use one reference to baronsport in the
>rev file
>
>baronsport IN PTR www.ycs.net.
That's not the proper format for a PTR record. The domain name that
owns the PTR record is normally an inverted IP address followed by
"in-addr.arpa."
cricket
Acme Byte & Wire | http://www.acmebw.com/
cri...@acmebw.com | (303) 449-0484
Kenneth Penttinen
Gregory EISENBERG wrote:
>-----
> ;ycs.hosts:
> ;or domain mappings!
>
> @ IN SOA ns.ycs.net. root.ycs.net. (
> 1996121399 ; serial number
> 43200 ; refresh every 12 hours
> 7200 ; retry after 2 hours
> 1209600 ; expire after 2 weeks
> 172800) ; default ttl is 2 days
> ;
> IN NS ns.ycs.net.
> IN NS jupiter.worldlinx.com. ; our secondary NS
>
$origin ycs.net.
> localhost IN A 127.0.0.1
> ns IN A 205.236.152.8
> prime IN A 205.236.152.2
> www IN A 205.236.152.2
> hero IN A 205.236.152.3
> homer IN A 205.236.152.5
>
> baron IN A 205.236.152.2
$origin baron.com.
> www.baron.com IN CNAME baron
> ;baron.com IN CNAME baron
>
> ----------------------------------------------------------------
> rev file
>
> baronsport IN PTR www.ycs.net.
>
OK, first of all, it doesn't look like you have an entry for
www.baronsport.com. This is why you would get those "no address records
available" message. Second, If you are going to be referencing multiple
domains in one zone file, you should reference the actual domain name as
I have added above.
What does your boot file look like for named?
You should make sure that you have entries for each of the domains that
you have authority for and point them all to the file:
primary ycs.net file
primary baron.com file
primary baronsport.com file
(file= zone file)
Let me know if I missed something...OH yeah update the serial # too...
==========================================================
Kenneth F Penttinen H O S T M A S T E R
G O O D N E T Pent...@name-server.net
==========================================================
Douglas M. MacFarlane
On Thu, 3 Apr 1997, Gregory EISENBERG wrote:
You need to setup the baronsport domian on your DNS server. It's
named.boot file shouuld have a line:
primary baronsport.com baronsport.hosts
then in baronsport.hosts, you'd have your typical SOA, NS and MX
entries, and then the following:
www IN A 205.236.152.2
Also, in your ycs.rev file, assuming an origin of
152.236.205.in-addr.arpa, you should have:
2 IN PTR www.ycs.net
Now, you appear to be trying to s setup a virtual server at the same
IP address as the www.ycs.net server. In general , the virtual
server has a different IP address. For example, www.ycs.net would
be at 205.236.152.2, adn www.baronsprot.com would be at
205.236.152.3. Then you would be able to have the following entry
in your ycs.rev file:
3 IN PTR www.baronsport.com
> ;ycs.hosts:
> ;or domain mappings!
>
> @ IN SOA ns.ycs.net. root.ycs.net. (
> 1996121399 ; serial number
> 43200 ; refresh every 12 hours
> 7200 ; retry after 2 hours
> 1209600 ; expire after 2 weeks
> 172800) ; default ttl is 2 days
> ;
> IN NS ns.ycs.net.
> IN NS jupiter.worldlinx.com. ; our secondary NS
>
> localhost IN A 127.0.0.1
> ns IN A 205.236.152.8
> prime IN A 205.236.152.2
> www IN A 205.236.152.2
> hero IN A 205.236.152.3
> homer IN A 205.236.152.5
>
> baron IN A 205.236.152.2
> www.baron.com IN CNAME baron
of upui want ww.baron.com to point to baron.ycs.net, you need to put
a terminating . after www.baron.com in ths line. Otherwise it
really represents www.baron.com.ycs.net.
> ;baron.com IN CNAME baron
>
> ----------------------------------------------------------------
> another note - from what I understand the only computer on our lan
> which is internet visible is our DNS 205.236.152.8
> So it is our DNS which points the query for home.ycs.net to the proper IP
> and I can do nslookup on homer.ycs.net from anywhere and get an answer
>
> Also as I understand it we did register www.baronsport.com to be assigned to
> 205.236.152.8 So an internet query for baronsport should hit our DNS
> which will then point it to the computer which has the virtual server on
> it - namely www
>
> Anyway I appreciate you reading all of this
> If you know where my mistake is please write me!!
>
> Oh yeah the .rev file I am sure is okay the only thing you might be
> interested to know is that I only use one reference to baronsport in the
> rev file
>
> baronsport IN PTR www.ycs.net.
This is way woring. See above.
Douglas M. MacFarlane
mad...@mcs.net
Kenneth Penttinen
Kenneth Penttinen wrote:
> > rev file
> >
> > baronsport IN PTR www.ycs.net.
> >
I forgot to add that the reverse file is for address to domain name
mapping, so you should have the in-addr.arpa followed by IN PTR then
baronsports.com. If you want www.baronsports.com to point to
www.ycs.net, you should just set up a CNAME in the forward zone.
--