Formerr
Barry Margolin
barmar at alum.mit.edu
Sat Oct 15 13:30:20 UTC 2005
In article <diqgt2$1rr0$1 at sf1.isc.org>,
Andy Pieters <x_terminat_or_3 at yahoo.fr> wrote:
> Hi List
> I am seeing a lot of these style of errors in my logs
>
> Oct 13 11:21:02 giga named[29413]: FORMERR resolving 'ns1.anwoo.com/AAAA/IN':
> 222.51.53.170#53
>
> Anything to worry about, and if not, can I make bind stop reporting them?
It's only something you need to worry about if you manage the
wildcard.com nameservers, since the problem is theirs, not yours.
I don't get a FORMERR response when I query that server, but the
response is still wrong. I ask for an AAAA record, but it returns an A
record instead.
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
More information about the bind-users
mailing list