On 23/09/2011 00:39, Joachim Tingvold wrote:
Or replace :: with _,
'_' is an illegal character in hostnames in the DNS...
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP:
On Sep 23, 2011 3:06 AM, Chris Buxton chris.p.bux...@gmail.com wrote:
On Sep 22, 2011, at 3:50 PM, TMK wrote:
On 9/21/2011 5:00 PM, TMK wrote:
I have couple of questions.
bind cache memory limit is 4GB. can I increase it. or this is
hard-coded limit.
i'm running the x64 bit version.
Niall,
Thanks very much for linking me to that article. It turns out
extremehosting.ca blocks incoming connections on port 53 which also
originate on 53. I've disabled the outgoing source port restrictions and
all is well again.
Also, securing against a cache poisoning vulnerability is a
Thanks to everyone for the help.
Larry
On Sep 21, 2011, at 3:56 PM, Adamiec, Lawrence wrote:
Hi,
Is it possible to have one IP in multiple zone files for forward
lookups? What type of troubles would be encountered?
Larry
Lawrence Adamiec
Unix Manager/Web Support
2011/9/23 Kevin Darcyk...@chrysler.com:
You're almost certainly getting the NXDOMAIN because you're spoofing
the
root servers, and your fake root servers don't have the same
knowledge as
the real ones, so they'll return NXDOMAIN for some queries (whereas
dig
+trace does not, because it
On 22 Sep 2011 22:57:17 +0100, Chris Thompson c...@cam.ac.uk said:
There was some correspondence last year about this warning message, but
this seems to be caused by something new.
Back then it was due to a bug in dnssec-signzone that caused NSEC3
records to remain in the zone during
6 matches
Mail list logo