Hi all.
Sometimes I can't resolve some addresses and, in the logs, I can find the
message in the title:
lame-servers: error (FORMERR) resolving [something]
(where `something` is the address I'm trying to resolve).
What does it means?
And how can I resolve this problem?
Thank you!
Daniele,
On Tuesday, 2013-01-08 09:49:57 +0100,
Daniele wrote:
> Hi all.
>
> Sometimes I can't resolve some addresses and, in the logs, I can find
> the message in the title:
>lame-servers: error (FORMERR) resolving [something]
> (where `something` is the address I'm trying to resolve).
>
Thank you.
So it's not my responsibility to resolve the problem, right?
The point is that, sometimes, I can't resolve an address because of this
lame servers, and dig (for example) fails.
Is it possible?
2013/1/8 Shane Kerr
> Daniele,
>
> On Tuesday, 2013-01-08 09:49:57 +0100,
> Daniele wro
1. Should ISC change the default logging for lame servers to disabled?
Well, since you asked: the lame server logging goes back to when the
internet was a small, collegial place and one wrote a quick note to a
friend to fix these issues. And people who accidentally had a lame
server were em
On 08/01/13 14:19, Timothe Litt wrote:
>> 1. Should ISC change the default logging for lame servers to disabled?
>
> Well, since you asked: the lame server logging goes back to when the
> internet was a small, collegial place and one wrote a quick note to a
> friend to fix these issues. And peop
Timothe Litt wrote on 01/08/2013 08:19:56 AM:
> What I think would be more useful is if named actually reported the
> issues to where they'd do some good. Perhaps a DNS extension "I got an
> invalid message from you" - so it shows up in the log of the server (and
> administrator) with the pr
You might as well solve world poverty and cure cancer while you're at it. :-)
Maybe tomorrow.
How do you notify someone -- good luck getting valid contact data for the
domain holder
As I suggested - if we put data into a database/trouble list, shame
should work. Or their customers will find i
If I use BIND9 forwarding all the queries not belonging to my local zones,
it works.
But if I don't forward those queries, `dig` sometimes (and this is weird)
fails (with "connection timed out; no servers could be reached") and the
logs are full of "lame server", "FORMERR".
Why?
_
My first thought would be lack of firewall rules and connectivity to the
Internet.
On Jan 8, 2013 9:35 AM, "Daniele" wrote:
> If I use BIND9 forwarding all the queries not belonging to my local zones,
> it works.
>
> But if I don't forward those queries, `dig` sometimes (and this is weird)
> fail
On 1/8/2013 9:35 AM, Daniele wrote:
If I use BIND9 forwarding all the queries not belonging to my local
zones, it works.
But if I don't forward those queries, `dig` sometimes (and this is
weird) fails (with "connection timed out; no servers could be
reached") and the logs are full of "lame s
https://github.com/pubyun/gitnamed
GitNamed
GitNamed is a project that manage name server by git. you can clone
the git repo to any workstation, edit zone file, commit and push it.
the data will push to the master and slave name server on the fly.
you don't need to touch name server any more, yo
> Sometimes I can't resolve some addresses and, in the logs, I can find
> the message in the title:
>lame-servers: error (FORMERR) resolving [something]
> (where `something` is the address I'm trying to resolve).
>
> What does it means?
2013/1/8 Shane Kerr
When acting as a recursive resol
Can this option be used in a 'slave' config to prevent out-bound transfers?
Transfers-out 0;
The 9.9.2 ARM is ambiguous.
Thanks
John Manson
CAO/HIR/NAF Data-Communications | U.S. House of Representatives | Washington,
DC 20515
Desk: 202-226-4244 | TCC: 202-226-6430 |
john.man...@mail.house.gov<
On Jan 8, 2013, at 1:24 PM, Manson, John wrote:
> Can this option be used in a ‘slave’ config to prevent out-bound transfers?
> Transfers-out 0;
> The 9.9.2 ARM is ambiguous.
Wouldn't it be simpler to just write this instead, in your options statement?
allow-transfer { none; };
Chris Buxton
Blu
> GitNamed is a project that manage name server by git. you can clone
> the git repo to any workstation, edit zone file, commit and push it.
> the data will push to the master and slave name server on the fly.
Very interesting; thanks for sharing.
I hear the Fedora Project does something along si
-Original Message-
From: Jan-Piet Mens
Date: Tuesday, January 8, 2013 4:35 PM
To: "bind-users@lists.isc.org"
Subject: Re: gitnamed, a project to manage name server by git
>> GitNamed is a project that manage name server by git. you can clone
>> the git repo to any workstation, edit zone
On 1/8/2013 13:48, Mike Hoskins (michoski) wrote:
Thanks for sharing both.
Like the built-in sanity checks...Wonder why the fedora folks don't
automate the serial number update, since in my experience that seems to be
one of the top silly mistakes with BIND updates?
Our push process sets that t
> When I built my DNS zone creator, I got tired of users complaining that
> their zones has "errors" and so I re-coded my serials to start with
> followed by six digits based on the current date/time.
>
> Oddly, that seems to fool most (although not all) of the DNS validation
> tools out th
Hi Team,
Thanks for help.
My Firewall was dropping packet size larger than 512 bytes.
Cisco 5580 having ASA 8.3. It is by default blocking my EDNS0 Packet.
Thanks and Regards,
Gaurav Kansal
On 12/31/12, Sten Carlsen wrote:
>
>
>
>
> With the replies you have shown, the limitation is v
19 matches
Mail list logo
