[prev in list] [next in list] [prev in thread] [next in thread] 

List:       djbdns
Subject:    Re: while Serving Multiple domains ?n
From:       prj () po ! cwru ! edu (Paul Jarc)
Date:       2001-09-27 17:56:35
[Download RAW message or body]

"dreamwvr@dreamwvr.com" <dreamwvr@dreamwvr.com> wrote:
>   Ok just wanted to make certain i_really_got what was discussed here.

You didn't get the part about not obscuring your data.

> .123.123.123.in-addr.arpa::ns?.mydomain1.com
> [...]
> .123.123.123.in-addr.arpa::ns?.myotherdom.com

It's unlikely that you would have that zone delegated to both sets of
server names.

> +ns[1-2].mydomain1.com:123.123.123.123-124
> +ns[1-2].myotherdom.com:123.123.123.123-124

tinydns-data will not understand these lines.  Perhaps you meant:
+ns1.mydomain1.com:123.123.123.123
+ns2.mydomain1.com:123.123.123.124
+ns1.myotherdom.com:123.123.123.123
+ns2.myotherdom.com:123.123.123.124

But you might as well remove these lines altogether and put the IP
addresses in the "." lines.

> ^.123.123.123.in-addr.arpa:123.123.123.123
> ^.123.123.123.in-addr.arpa:123.123.123.124

I don't know what these lines are supposed to do, but they're almost
certainly wrong.

> @mydomain1.com::mail.mydomain1.com:10:
> @myotherdom.com::mail.myohterdom.com:10:

You left out the IP addresses.  They might be provided elsewhere in
the data file, but you didn't show us that.  Also, since MX names
don't have to match another set somewhere else, you might as well use
the automatic names:
@mydomain1.com:1.2.3.4:a:10
@myotherdom.com:1.2.3.5:a:10


paul

[prev in list] [next in list] [prev in thread] [next in thread]