1 msgMarshal V Langlois is out of the office.
3 msgWhy does host Command in bind9.3.2 Repeat Itself?
5 msgwildcard reverse lookups?
3 msgunable to find masters list
1 msgOk: BIND 9.4.0rc1 is now available: Unifix Linu...
3 msgDisabling queries over IPv6
3 msgSecondary - SERVFAIL
5 msgCaching nameserver
8 msgForce Clients to *always* use authoritative

rrset-order fixed not working in bind 9.4.0b4
\ Dinu Bogdan (18 Dec 2006)
. \ Stephane Bortzmeyer (19 Dec 2006)

2 msgis this correct ?
6 msgResolving a domain
25 msgDomain not resolve but resolve with other ISP d...
2 msgReverse Lookups from Slaves on Private Network
7 msgNXDOMAIN returned on while updating
9 msgnsupdate and round robin
2 msgmigration from bind8 to bind9
1 msgRE: BIND 9.3.3 RC3 is now available.
2 msgBest practice for zone with resonable amount of...
6 msgbig problem - possibly dns?
Subject:Re: rrset-order fixed not working in bind 9.4.0b4
Group:Bind-users
From:Stephane Bortzmeyer
Date:19 Dec 2006


 
On Mon, Dec 18, 2006 at 08:03:25AM -0800,
Dinu Bogdan <dinub_at_home> wrote
a message of 26 lines which said:

> I've just updated to bind-9.4.0b4 in order to get support for
> rrset-order fixed which is not implemented in previous versions.
> now i don't get any error but the dns still sends ips in a random
> way.

You did not post what command you used to check. So, be sure to ask
directly the authoritative name server ("dig @a.b.c.d NS
foobar.example."): if, instead, you go through a recursive nameserver
somewhere, it may be responsible for the shuffling of records.




© 2004-2008 readlist.com