Sorry for the delayed Summary, but I was quite busy troubleshooting
the DNS new configuration files and getting the new set up working.
The problem was not because of the configuration file, but mainly
with in.named using the wrong named.conf file. By default, in.named
uses
/etc/named.conf file (but can be changed with -f option), and I thougth
all
along that it was using the named.conf file in /etc/named directory, where
all my DNS records are kept.
Thanks so much to the following:
Dave Maupin
Matthew Fanser
Brian Laughton
Jim Musso
Buddy Lumpkin
Misha Pavlov
Dana@dtn.com
Michael DeSimone
Kent Perrier
John Heasley
Zareh Aratoon
Ray Trzaska
Bill Fay
Robert Alexander (gave great example as below)
and especially to Erin Jones who spent some time analyzing my
DNS configuration files.
I needed to add a new record to named.conf (Bind 8.x), a new zone
file with SOA, NSes, A, and CNAME (and eventually MX for sendmail).
The forward file of the newdomain would have identical information
with the exeception of the domainname. For example:
zone "currentdomain.com" {
type master;
file "/path/to/currentdomain.com.file";
};
zone "newdomain.com" {
type master;
file "/path/to/newdomain.com.file";
};
For example, let's say this is the file for currentdomain.com:
===========================================
currentdomain.com. IN SOA nameserver.currentdomain.com.
user.currentdomain.com. (
2000030507
43200
3600
3600000
259200 )
currentdomain.com. IN NS nameserver.currentdomain.com.
currentdomain.com. IN NS another.nameserver.com.
currentdomain.com. IN NS yetanother.nameserver.com.
currentdomain.com. IN MX 10 mail.currentdomain.com
currentdomain.com. IN MX 20 mail.alternatemailserver.com.
currentdomain.com. IN A xxx.xxx.yy.zz
www.currentdomain.com. IN A xxx.xxx.yy.zz
ftp.currentdomain.com. IN A xxx.xxx.yy.zz
===========================================
then the file for newdomain.com would be the same except you'd put
'newdomain.com' in place of 'currentdomain.com' like this:
===========================================
newdomain.com. IN SOA nameserver.currentdomain.com.
user.currentdomain.com. (
2000030507
43200
3600
3600000
259200 )
newdomain.com. IN NS nameserver.currentdomain.com.
newdomain.com. IN NS another.nameserver.com.
newdomain.com. IN NS yetanother.nameserver.com.
newdomain.com. IN MX 10 mail.currentdomain.com
newdomain.com. IN MX 20 mail.alternatemailserver.com.
newdomain.com. IN A xxx.xxx.yy.zz
www.newdomain.com. IN A xxx.xxx.yy.zz
===========================================
same IPs, mail server, name servers, everything... :>
-Ernie
==========================================================
Ernest Cespedes wrote:
> We just registered another domainname to our company and would
> like to include [or point] to our existing domain. So, for example,
> if one were to go to www.newdomain.com, I want it to go
> to www.currentdomain.com website.
>
> I read the new edition of DNS and BIND book by Albitz & Liu (O'Reilly),
> but didn't find any information of having two domainnames pointing to
> one.
>
> Here's what I did so far on the DNS server:
>
> /etc/named/named.forward:
>
> added: www.newdomainname.com IN CNAME
> dns-server.currentdomain.com
>
> Restarted named, but nslookup failed to resolve the www.newdomain.com.
>
> Do I need to include, IN, A, and NS for the www.newdomain.com?
>
> Here are my files in /etc/named directory:
>
> named.boot
> named.cache
> named.forward
> named.reverse
> named.loopback
>
> Thanks in advanced for your help/suggestions.
>
> -Ernie
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:06 CDT