interesting dns behavior

[David Botham]

> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of J.M.Roth
> Sent: Tuesday, February 18, 2003 9:56 AM
> To: comp-protocols-dns-bind at isc.org
> Subject: interesting dns behavior
> 
> Hello there,
> I had the following problem over the weekend.
> I solved it now but I still don't really know where it came from.
> I had a zone file that started like this:
> 
> $ORIGIN x.y.
> $TTL    86400
> @       IN      SOA     ns1.x.y.     noc.x.y.     (
>                         2003021802
>                         2H
>                         15M
>                         2W
>                         1H      )
>         NS      ns1.x.y.
>         NS      ns2.x.y.
> lan     NS      ns1.x.y.
> lan     NS      ns2.x.y.
>         MX      10      mail
>         TXT     48

If the Left field is *blank*, it will be *repeated* in subsequent RR's.
Therefore, if you where trying to do this:
lan     NS      ns1.x.y.
lan     NS      ns2.x.y.
lan     MX      10      mail
lan     TXT     48

Then, the MX an TXT RR's are out of zone data in the x.y zone, and they
should be moved to the lan.x.y zone.

However, if you were trying to do this:
lan     NS      ns1.x.y.
lan     NS      ns2.x.y.
@       MX      10      mail
@       TXT     48

I think you can now see why you were not doing what you think you were
doing.


> 
> Note the 2 delegations for the subdomain "lan"
> BIND didn't choke on this but the TXT an MX records weren't visible to
the
> outer world, which caused major mayhem.
> Changing it to
> 
>         NS      ns1.x.y.
>         NS      ns2.x.y.
>         MX      10      mail
> lan     NS      ns1.x.y.
> lan     NS      ns2.x.y.
>         TXT     48

Note that want you have here is this (assuming that the soa RR is the
same as above):
@       NS      ns1.x.y.
@       NS      ns2.x.y.
@       MX      10      mail
lan     NS      ns1.x.y.
lan     NS      ns2.x.y.
lan     TXT     48

I am not sure if you intended to have the text RR in the lan.x.y zone.
If you did, it is *out of zone data* in the x.y zone.  It should be
moved.


By moving the MX RR above the lan.x.y RR's (and leaving the first field
blank), you have actually changed the real domain name.


Dave...


> 
> fixed the issue.
> I'm just wondering why
> 
> Greets
> -jm
>