Resolver not always resolving hostnames

[Jilles Tjoelker]

On Sun, Oct 22, 2006 at 04:23:48PM -0700, Doug Barton wrote:
> Simon L. Nielsen wrote:
> 
> >I also seen odd things happen with host(1).  These two commands were
> >run right after each other.  I don't know if it's related, but I
> >suspect it is.

> >$ host cvsup3.dk.freebsd.org
> >cvsup3.dk.freebsd.org is an alias for mirror03.inet.tele.dk.
> >cvsup3.dk.freebsd.org is an alias for mirror03.inet.tele.dk.

> You got a double answer here because by default host(1) searches for 
> both A and AAAA records for hostnames.

It usually gives three of them, for A, AAAA and MX.

> >$ host cvsup3.dk.freebsd.org
> >cvsup3.dk.freebsd.org is an alias for mirror03.inet.tele.dk.
> >mirror03.inet.tele.dk has address 195.41.53.219

> You got an answer for the A query here for mirror03.inet.tele.dk.

> >cvsup3.dk.freebsd.org is an alias for mirror03.inet.tele.dk.

> You got an answer here for the AAAA query for cvsup3.dk.freebsd.org.

> >cvsup3.dk.freebsd.org is an alias for mirror03.inet.tele.dk.

> This is probably an error, and if it's what I think it is this problem 
> is fixed in the latest version of BIND.

It is the answer to the MX query.

These triple "is an alias for" are since bind9's host or so.

-- 
Jilles Tjoelker