On Sat, 5 Sep 1998, Dwight Johnson wrote:
But now my local host names--how closely can I follow the DNS HOWTO?
Pretty closely if you want to learn how a dns server is setup ;)
I see a couple of immediate variances: no /etc/named.conf and
/etc/named.conf is the Bind 8.*.* version of the /etc/named.boot file used in earlier releases of Bind. It does much the same thing, but uses a very different (new and improved) syntax.
/var/named/root.cache appears to serve the same function as /var/named/root.hints.
You can name the data files anything you want. The "hints" file loads the "." domain. This is a necessary part of most all nameservers (there are exceptions). Look at the 'directory' directive in your /etc/named.boot or /etc/named.conf. It will tell you (or allow you to configure) the location of your zone (data) files that you wish to load into your dns server. There should be one for every domain which you wish to load into your dns. To add another primary zone, you will add another 'primary' line to your /etc/named.boot: primary domain.com domain.db .. or master zone to your /etc/named.conf (if Bind 8.*.*) : zone "domain.com" { type master; file "domain.db"; }; ... where "domain.com" is the domain's dns which you wish to load, and "domain.db" is the zone file that contains that domain's dns information. You would then have to create that zone file and place it in the /var/named directory (or wherever you've listed in the 'directory' directive of your boot file).
What I need is actually *just one* additional local host name so Netscape will see it and not go looking for it on the Internet.
Sounds like the /etc/hosts file (as Zens suggested) might be your best bet. The dns way gets complicated if there are other hosts that live in that particular dns domain. You will have to have data for all hosts in that domain or your nameserver will answer authoritatively that the host does not exist. For example, you try to go to <A HREF="http://host1.domain.com"><A HREF="http://host1.domain.com</A">http://host1.domain.com</A</A>> in your browser. You've loaded 'domain.com' into your nameserver and it contains one A (address) record for host1, so you get to host1.domain.com in your web browser. But, there are other machines that also live in the domain.com domain that another nameserver loads. Your machine will see host1.domain.com, but will not see host2, host3, or host4 that the other dns server has loaded. Of course, the results would be exactly opposite if your /etc/resolve.conf points at your isp's nameserver instead of at 127.0.0.1 (your local machine) first.
Can anyone help me with that?
Yep. You're welcome to email me offline. Jim Fischer Altavista Software Compaq
Thanks, Dwight
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e