- --------
Hi
Thanks for all the help from everyone. I was finally able to solve the problem
by recreating the primary bind setup, and making corrections to the 'namedb'
files. Although setting up the namedb files were rather complicated, I got a
great deal of help from the 'TCP/IP Network Administration' by Craig Hunt,
published by O'Reilly and Associates, Inc. My problem was also complicated by pointers from the PSI server, which was an
original name server for npcc.
The original message and responses:
I am trying to setup a bind server under osf-v3.2. Although I was able to setup
the primary server, I am having trouble with a client server. Two isuues at
hand:
1. when i try to mail myself a message (ltun_at_npcc.org) from a client, it had
trouble locating host (hostname lookup failure). But if i tell it send the mail
a specific machine (ltun_at_neptune.npcc.org), it works.
2. i was trying bouncer_at_nic.near.net, also from a client. Although the mail
got there, i did not get a bounce receipt.
---------
Here is what I got when I did an lookup on your domain:
******************************
; <<>> DiG 2.0 <<>> npcc.org mx
;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6
;; flags: qr rd ra ; Ques: 1, Ans: 4, Auth: 2, Addit: 7
;; QUESTIONS:
;; npcc.org, type = MX, class = IN
;; ANSWERS:
npcc.org. 86362 MX 5000 mx3.smtp.psi.net.
npcc.org. 86362 MX 5 npcc.org.
npcc.org. 86362 MX 5000 mx.smtp.psi.net.
npcc.org. 86362 MX 5000 mx2.smtp.psi.net.
*******************************
The first problem here is that if you want mail addressed to npcc.org to
go to the neptune machine then you need a MX record for this. The record
you have here pointing npcc.org to npcc.org won't work.
The next problem is the other records with the 5000 weight. Every record
should have a differnet weight with the first machine you want sendmail
to check having the lowest address.
Here is another setup you have that I've never been a fan of:
*****************************
; <<>> DiG 2.0 <<>> npcc.org
;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6
;; flags: qr rd ra ; Ques: 1, Ans: 1, Auth: 2, Addit: 3
;; QUESTIONS:
;; npcc.org, type = A, class = IN
;; ANSWERS:
npcc.org. 85826 A 204.7.32.2
neptune.npcc.org. 86256 CNAME npcc.org.
*****************************
NPCC.ORG is your _domian_. Unless you want people to telnet to 'npcc.org'
without a machine listed in front of it (not a good idea in my opinion)
you shouldn't give the domain an IP address. Instead, give
neptune.npcc.org the 204.7.32.2 address and give npcc.org an MX pointer
to it.
I have similar problems with 3.0, and I am interested in your summary!
I can add 1) that it seems to be an intermittant problem for me; many smtp
requests to user_at_intranet.com work, but some fail, and I have never seen
user_at_host.intranet.com fail; and 2) when I send a message to bouncer with
% mailx -v bouncer_at_nic.near.net
I always get back, "you are a charlatain" (sp?)
-----------------
------------------
lin tun
ltun_at_npcc.org
Received on Wed May 03 1995 - 08:51:10 NZST