Resolve all domains to one name?

[Barry Margolin]

In article <88d3kb$80s$1 at nntp6.u.washington.edu>,
M. Oesterwinter <marcuso at saul2.u.washington.edu> wrote:
>Kevin Darcy (kcd at daimlerchrysler.com) wrote:
>: M. Oesterwinter wrote:
>
>: > Forgive me ignorance (the DNS and Bind book is on the way).
>: > I am not sure what the root zone is.
>: > By root zone file, do you mean the named.conf?
>
>: No, that's the configuration file for named. The DNS database is divided into
>: zones in a hierarchy, and the "root zone" is the top zone of that hierarchy.
>: Not something to be tinkered with casually.
>
>Would the named.root be my root zone file?
>
>Can I simply add	*	IN	A	192.168.1.1
>
>If I want all the names that I don't have zone files for to resolve to
>192.168.1.1?

You want:

zone "." {
  type master;
  file "named.root";
};

Then in named.root you would have:

@ IN SOA ...
  IN NS  yourserver.yourdomain.com.

* IN A 192.168.1.1


>
>: > Also, I inquired before, but haven't received a response.  What is the
>: > difference between have the IN in zone files.  Example:
>: >
>: > www     IN      A       192.168.1.1
>: > versus
>: > www     A               192.168.1.1
>
>: DNS supports multiple "classes" or namespaces. The "Internet" class, ("IN") is
>
>: by far the most widely used. If you don't specify a class in a Resource Record
>
>: ("RR"), then the IN class is assumed. So those 2 RRs are functionally
>: identical.
>
>
>Which would be better to use (stylistically)?

I think most people put the IN in simply out of habit.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.