search for: formerr

...8 Address: 8.8.8.8#53 Aliases: mirror.centos.org has address 69.167.139.9 # host mirror.centos.org mirror.centos.org has address 66.109.26.212 Host mirror.centos.org not found: 2(SERVFAIL) Host mirror.centos.org not found: 2(SERVFAIL) # tail -F /var/named/chroot/var/named/data/named.run error (FORMERR) resolving 'mirror.centos.org/AAAA/IN': 85.12.30.226#53 error (FORMERR) resolving 'mirror.centos.org/AAAA/IN': 93.113.36.66#53 error (FORMERR) resolving 'mirror.centos.org/AAAA/IN': 94.46.190.42#53 error (FORMERR) resolving 'mirror.centos.org/AAAA/IN': 85.12.30.226#5...

...'s are throwing up error after error constantly. They seem to be having difficulty contacting the root servers, I think, but I'm not really sure what is going on but I'm assuming it's a Bind issue. Here are the errors. Can anyone help? Thank you! Sep 10 12:01:01 dc02 named[1617]: FORMERR resolving './NS/IN': 193.0.14.129#53 Sep 10 12:01:01 dc02 named[1617]: DNS format error from 192.5.5.241#53 resolving ./NS: non-improving referral Sep 10 12:01:01 dc02 named[1617]: FORMERR resolving './NS/IN': 192.5.5.241#53 Sep 10 12:01:01 dc02 named[1617]: DNS format error from 19...

...gt; ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 > ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 > ;; UPDATE SECTION: > my.domain.tld. 900 IN A IP_of_2nd_DC > > ; TSIG error with server: tsig verify failure > update failed: FORMERR > Failed nsupdate: 2 > Calling nsupdate for SRV _ldap._tcp.my.domain.tld DC2.my.domain.tld > 389 (add) > Outgoing update query: > ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 > ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 > ;; UPDATE SECTI...

On 10/12/15 14:00, Ole Traupe wrote: > > > Am 10.12.2015 um 14:38 schrieb Rowland penny: >> On 10/12/15 13:25, Ole Traupe wrote: >>> Is it possible that kdc server is always the SOA, at least if >>> derived from DNS and not specified *explicitly* in the krb5.conf? >>> >>> In my DNS-Manager console I find that >>> >>>

..._DC (add) Outgoing update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 ;; UPDATE SECTION: my.domain.tld. 900 IN A IP_of_2nd_DC ; TSIG error with server: tsig verify failure update failed: FORMERR Failed nsupdate: 2 Calling nsupdate for SRV _ldap._tcp.my.domain.tld DC2.my.domain.tld 389 (add) Outgoing update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 ;; UPDATE SECTION: _ldap._tcp.my.domain.tld. 900 I...

...t;<- opcode: UPDATE, status: NOERROR, id: 0 >> ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 >> ;; UPDATE SECTION: >> my.domain.tld. 900 IN A IP_of_2nd_DC >> >> ; TSIG error with server: tsig verify failure >> update failed: FORMERR >> Failed nsupdate: 2 >> Calling nsupdate for SRV _ldap._tcp.my.domain.tld DC2.my.domain.tld >> 389 (add) >> Outgoing update query: >> ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 >> ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL...

...: NOERROR, id: 0 > >> ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 > >> ;; UPDATE SECTION: > >> my.domain.tld. 900 IN A IP_of_2nd_DC > >> > >> ; TSIG error with server: tsig verify failure > >> update failed: FORMERR > >> Failed nsupdate: 2 > >> Calling nsupdate for SRV _ldap._tcp.my.domain.tld DC2.my.domain.tld > >> 389 (add) > >> Outgoing update query: > >> ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 > >> ;; flags:; ZONE: 0, PRE...

...status: NOERROR, id: 0 >>> ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 >>> ;; UPDATE SECTION: >>> my.domain.tld. 900 IN A IP_of_2nd_DC >>> >>> ; TSIG error with server: tsig verify failure >>> update failed: FORMERR >>> Failed nsupdate: 2 >>> Calling nsupdate for SRV _ldap._tcp.my.domain.tld DC2.my.domain.tld >>> 389 (add) >>> Outgoing update query: >>> ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 >>> ;; flags:; ZONE: 0, PREREQ:...

...; >> ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 > > >> ;; UPDATE SECTION: > > >> my.domain.tld. 900 IN A IP_of_2nd_DC > > >> > > >> ; TSIG error with server: tsig verify failure > > >> update failed: FORMERR > > >> Failed nsupdate: 2 > > >> Calling nsupdate for SRV _ldap._tcp.my.domain.tld DC2.my.domain.tld > > >> 389 (add) > > >> Outgoing update query: > > >> ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 > > &g...

...3.5 Outgoing update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 ;; flags: ; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 ;; UPDATE SECTION: gaara.kazekage.net. 900 IN A 192.168.93.5 ; TSIG error with server: tsig verify failure update failed: FORMERR Failed nsupdate: 2 Calling nsupdate for A shuka-ku.gaara.kazekage.net 192.168.93.5 Outgoing update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 ;; flags: ; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 ;; UPDATE SECTION: shuka-ku.gaara.kazekage.net. 900 IN A...

...sdcs.adi.com koi.adi.com Outgoing update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 ;; UPDATE SECTION: ef382a43-092e-4cda-acb1-e7ba70e9253e._msdcs.adi.com. 900 IN CNAME koi.adi.com. dns_request_getresponse: FORMERR Failed nsupdate: 1 Calling nsupdate for SRV _kpasswd._tcp.adi.com koi.adi.com 464 Outgoing update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 ;; UPDATE SECTION: _kpasswd._tcp.adi.com. 900 IN SRV...

...me pointer > sambaDC.domain.com. > > >And > >dig a $(hostname -s) > > ; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> a ThisDC-SambaDC-we-want-to-join > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 20641 > ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 > ;; WARNING: recursion requested but not available > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 4096 > ; COOKIE: 852b24514a370e2a (echoed) > ;; QUESTION SECTION: > ; sambaDC....

...ff, I copied the whole list out of lib/dns/result.c, in an attempt to put an end to my headache. If you insist on using an enumeration instead of ".*", here's the complete list (aside from NOERROR, obviously): ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ named\[[0-9]+\]: unexpected RCODE \((FORMERR|SERVFAIL|NXDOMAIN|NOTIMP|REFUSED|YXDOMAIN|YXRRSET|NXRRSET|NOTAUTH|NOTZONE|BADVERS|<rcode [[:digit:]]+>|[[:digit:]]+)\) resolving '[^[:space:]]+': [.[:digit:]]+#[0-9]+$ (Remember that this is both a violations and a normal ignore rule.) The source sets undefined rcodes such as 15 as...

...and for which I shouldn't. Now that I'm digging, there also seem to be some generic WERR_BADFILE DRS replication errors that our automated monitoring somehow didn't catch; and one DC apparently no longer has the DNS entries it should have, and samba_dnsupdates alternates between "FORMERR" and "GSS-TSIG unsuccessful" which apparently is only supposed to appear with the BIND9 DNS backend, which we aren't using. These are probably related, but again I have no idea where these come from or how to debug them. So how was your morning? -- Mit freundlichen Grüßen, /...

...;KOI.adi.com' [2014/03/02 14:31:58.910948, 0] ../source4/lib/tls/tlscert.c:166(tls_cert_generate) TLS self-signed keys generated OK [2014/03/02 14:31:59.262744, 0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler) /opt/local/samba4/sbin/samba_dnsupdate: dns_request_getresponse: FORMERR [2014/03/02 14:32:18.706897, 0] ../source4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT [2014/03/02 14:41:59.042163, 0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler) /opt/local/samba4/sbin/sa...

Processing commands for control at bugs.debian.org: > tags 383112 wontfix Bug#383112: logcheck generates a security alert for bind FORMERR entries, regardless of regex There were no tags set. Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

...'t. > > Now that I'm digging, there also seem to be some generic WERR_BADFILE > DRS replication errors that our automated monitoring somehow didn't > catch; and one DC apparently no longer has the DNS entries it should > have, and samba_dnsupdates alternates between "FORMERR" and "GSS-TSIG > unsuccessful" which apparently is only supposed to appear with the BIND9 > DNS backend, which we aren't using. These are probably related, but > again I have no idea where these come from or how to debug them. > > > So how was your morning? >...

...med[1765]: error (network unreachable) resolving 'software.majix.org/A/IN': 2001:503:ba3e::2:30#53 I believe that this line was intended to match it. ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ named\[[[:digit:]]+\]: ((network|host) (unreachable|down)|connection refused|unexpected RCODE \((FORMERR|SERVFAIL|NXDOMAIN|NOTIMP|REFUSED|YXDOMAIN|YXRRSET|NXRRSET|NOTAUTH|NOTZONE|BADVERS|<rcode [[:digit:]]+>|[[:digit:]]+)\)) resolving '[^[:space:]]+': [.:[:xdigit:]]+#[[:digit:]]+$ The Lenny form of the syslog line would have been: May 17 07:39:43 localhost named[2395]: network unreac...

Hai, I had a quick look. Barry, can you get this script and run it. https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Then post the results to the list. It collects all info i need to have a better look. I have a few ideas, this might be a resolving order problem, i've based on the errors below. Can you also post the output of bind from the point its

I tried to compile Samba 2.0 beta with cc under SCO 3.2. I seem to be missing the inet.h and netdb.h include files. Does anyone know if they are publicly available? Steve Grose Sgrose@cmps.com Continental Managed Pharmacy Services - www.preferrx.com Voice - 216-459-2025 Ext. 208 Fax - 216-485-8615 Any opinions expressed are my own and not necessarily those of my employers.