> fyi, DLZ external has been broken post 9.8.1p1. fails to compile with
> an undefined reference to main. both for 9.8.2 and 9.9.0
Thanks for the heads-up. Please open a bug ticket at bind9-b...@isc.org,
and include information about the OS you're building on. I expect this is
going to turn
fyi, DLZ external has been broken post 9.8.1p1. fails to compile with
an undefined reference to main. both for 9.8.2 and 9.9.0
-david
make[4]: Entering directory
`/usr/vport/portage/net-dns/bind-9.9.0/work/bind-9.9.0/bin/tests/system/dlzexternal'
/bin/sh /usr/vport/portage/net-dns/bind-9.9.0
A cosmetic flaw was found in BIND 9.8.2 after publication: the
release notes for BIND 9.8.1 were inadvertedly left in the tarball.
As this caused confusion among some users, ISC is re-publishing
BIND 9.8.2 with the spurious files removed. Absolutely no other
changes have been made to the release
I will take this opportunity now to point out that upgrading to 9.9.X from any
release prior to it might cause problems if you have any slave zones. 9.9.X by
default saves slave zone files using "masterfile-format raw;", and 9.8.X and
earlier defaults to "masterfile-format text;".
It's easy to
> In order to save me poring through lots of archives and posts for the answer
> to a simple question: Are there any differences between 9.7x and 9.8x that
> require a change in named.conf configuration? The bottom line is that if I
> want to upgrade from 9.7 to 9.8, are there any "Gotchas" that I
In order to save me poring through lots of archives and posts for the answer
to a simple question: Are there any differences between 9.7x and 9.8x that
require a change in named.conf configuration? The bottom line is that if I
want to upgrade from 9.7 to 9.8, are there any "Gotchas" that I need to
On Tue, Apr 10, 2012 at 2:56 AM, rams wrote:
> Hi,
> When i queried domain with capital letters , In answer section domain name
> is displaying small letters. Is it expected? any RFC for this?
>
> dig @localhost D.ashwintrail.com
>
>
> ; <<>> DiG 9.2.4 <<>> @localhost D.ashwintrail.com
> ; (1 serv
On 10.04.12 19:24, rams wrote:
When I get TC flag for UDP query?
when the answer is too big to fit into the UDP packet of sice 512
(default) or client-provided (when your client advises bigger buffer size)
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish
The TC flag is set when the response is larger than your max udp packet
size. 512 bytes with no edns0 and up to 4096 bytes with edns0 fully
functioning.
On Apr 10, 2012 9:55 AM, "rams" wrote:
> When I get TC flag for UDP query?
>
> ___
> Please visit ht
http://www.ietf.org/rfc/rfc4343.txt
Some resolvers use 0x20 tricks to encode additional entropy into queries.
This works by randomly adding 0x20 to characters in the qname and then making
sure they are the same when they come back (e.g: example.com -> eXAmpLe.coM)...
W
On Apr 10, 2012, at 5:5
On 09.04.12 16:55, Marseglia, Michael wrote:
I'm troubleshooting a DNS issue we recently experienced where records
were unresolveable, response NXDOMAIN, from the caching DNS server.
I flushed the cache using rndc flush and I received the host's ip.
There were no errors in the system log so I
11 matches
Mail list logo
