Thanks everybody. Views is what I was looking for.
Rodolfo, to answer your question as to why the internal and external domain
names needed to be the same, many of my technically challenged users
connect through our network via laptops which also connect from the
outside. In order to function inside and outside they need to be able to
use the same domain name for our e-mail server. There are workarounds, but
they require more than a button click which is more than some of my users
can or want to deal with. Anyhow, the problem is solved :)
I do have another question though. Another purpose I had for setting up an
internal DNS server was because our primary DNS server was being provided
by Qwest. Qwest did not have a PTR record for our mail server, and a phone
call to them has resulted in nothing but frustrating conversations with
people who don't understand what I'm talking about. The missing PTR causes
our mail to be rejected by companies such as AOL and MSN. I set up the
internal DNS server, changed the listing with the root servers so that our
primary DNS server is our ISP's server, my server is the slave. I removed
any reference to Qwest from the primary and slave servers. I added all the
needed PTR records. Unfortunately when I do a reverse DNS lookup on my mail
server from www.dnsstuff.com I get the following output:
Searching for 51.118.230.63.in-addr.arpa PTR at g.root-servers.net: Got
referral to ARROWROOT.ARIN.NET. (zone: 63.in-addr.arpa.)
Searching for 51.118.230.63.in-addr.arpa PTR at ARROWROOT.ARIN.NET.: Got
referral to NS1.USWEST.NET. (zone: 230.63.in-addr.arpa.)
Searching for 51.118.230.63.in-addr.arpa PTR at NS1.USWEST.NET.: Reports
that no PTR records exist.
Answer:
No PTR records exist for 63.230.118.51. [Neg TTL=86400 seconds]
Details:
NS1.USWEST.NET. (an authoritative nameserver for 230.63.in-addr.arpa.,
which is in charge of the reverse DNS for 63.230.118.51)
says that there are no PTR records for 63.230.118.51.
Now my question. Is there anyway to circumvent dealing with Qwest to get my
PTR records recognized for my IP address? If not, does anybody have a phone
number that will get me a Qwest technician who actually knows what a PTR
record is? Is there a setting that I'm not thinking of on my DNS servers?
Thanks for your help.
Lee Griffin
IT Support Analyst
Varsity Contractors, Inc.
Tel:208.232.8598 ext 365
--- Begin Message ---
At 4/10/2002 11:54 AM -0600, you wrote:
>My internal and external host names need to be the same.
OK, but why? (Not a big deal, just curious.)
>Thus, in order for my local users to access our mail server,
>mail.varsitycontractors.com, dns must map to a private 10.x.x.x, while my
>remote users will need dns to map them to a public IP via the same hostname.
I'm not so sure. You could, for example, have it map only to the public IP,
and allow port 25/110/143 (smtp/pop/imap) traffic out from your office only
to that single IP address. Since it's on the same box, your users still
don't get out to the Internet. From the above, no reason you *must* have
the name on an internal IP.
>I'm told I need split dns, but I'm having trouble getting it to work. For
>example, I can't get more than one named daemon to run.
You shouldn't have more than one daemon. BIND 9 has "views" which allow you
to present different information to people coming from different points.
You'll have to read the docs, though, as I don't yet know how to do it.
There seems to be finally a manual or book for BIND 9 on the ISC's website
that you can download.
--
Rodolfo J. Paiz
[EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
--- End Message ---
