Date: Thu, 01 Aug 2013 10:44:11 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-stable@freebsd.org Subject: Re: Strange sendmail behaviour after upgrade to 9.1-BETA2 Message-ID: <51FA2DEB.40106@infracaninophile.co.uk> In-Reply-To: <CAAoTqfuBxCpbXON-aa98BgVQz6mZyG-yTkO7630p74eV%2BQvTmQ@mail.gmail.com> References: <CAAoTqfvmsYc=fE9AZyzf9GKBtbazdu%2B3jmD5TjhMqQHDnrtrkw@mail.gmail.com> <CAAoTqfsftjLQMLZpnwtPJYV2gKEn3kumYVycKroi5%2BaEbjEoJQ@mail.gmail.com> <CAAoTqftbCS_g45e6m9tXhR0wc3Q5-9kWmUDCANX597h8DRQakg@mail.gmail.com> <CAAoTqfuqYkgHg9--wev8Qji7fVvDVB-BVdP1hO=KD4SfuP-RXw@mail.gmail.com> <CAAoTqftW2KJtQnZpk=DV6snXyu21agdaX_8ku0%2B623FDVW71gw@mail.gmail.com> <CAAoTqfv_XAwCUkBh4WFhdNTEe7wZ4_Sbpis3OCacUrwoT-p4NA@mail.gmail.com> <CABXB=RQdycdQKGbOh2tNvzyTpOGSyq6hCAFj=5BAHPMtg90YKQ@mail.gmail.com> <CAAoTqfu%2BYt5cd%2BOwXqesNcJqatLiZgOssYgLB0CD6ot%2BEp6-KQ@mail.gmail.com> <CAAoTqfuBxCpbXON-aa98BgVQz6mZyG-yTkO7630p74eV%2BQvTmQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/08/2013 09:41, Pavel Timofeev wrote: > to Matthew Seaman > No luck > > root@test:/etc/mail # grep ip /etc/rc.conf > #ipv6_activate_all_interfaces="NO" > #ipv6_network_interfaces="none" > ip6addrctl_enable="YES" > ip6addrctl_policy="ipv4_prefer" > > root@test:/etc/mail # ip6addrctl > Prefix Prec Label Use > ::1/128 50 0 0 > ::/0 40 1 0 > ::ffff:0.0.0.0/96 100 4 0 <<<----**** > 2002::/16 30 2 0 > 2001::/32 5 5 0 > fc00::/7 3 13 0 > ::/96 1 3 0 > fec0::/10 1 11 0 > 3ffe::/16 1 12 0 > Why do you think this hasn't worked? The line I indicate there is for IPv4 mapped addresses in IPv6 (RFC r6052). ie. it says that IPv4 mapped addresses have the highest precedence out of all of the IPv6 routable blocks. For your original problem, where sendmail is asking for an AAAA record for an MX -- you're seeing a sequence of queries where sendmail asks first for the MX and then an AAAA record but no explicit query for an A record? This is not necessarily ignoring the A record: if you look up an MX, usually an A record will be returned in the Additional section. eg: rufus:~:% dig infracaninophile.co.uk IN MX ; <<>> DiG 9.8.4-P2 <<>> infracaninophile.co.uk IN MX ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9434 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; QUESTION SECTION: ;infracaninophile.co.uk. IN MX ;; ANSWER SECTION: infracaninophile.co.uk. 86400 IN MX 10 smtp.infracaninophile.co.uk. infracaninophile.co.uk. 86400 IN MX 10 smtp6.infracaninophile.co.uk. ;; ADDITIONAL SECTION: smtp.infracaninophile.co.uk. 86400 IN A 81.2.117.97 <<<---** ;; Query time: 29 msec ;; SERVER: 192.168.0.252#53(192.168.0.252) ;; WHEN: Thu Aug 1 10:34:28 2013 ;; MSG SIZE rcvd: 99 so no separate query for the A record required. (This behaviour appears to be OS/resolver dependent: on another host that happens to be runnign Linux, I see the A and AAAA records for the domain name servers in the Additional section, rather than the A (or AAAA) records for the MX. Perhaps it's more to do with the version of bind (or unbound or whatever) you're using as your recursive resolver rather than anything else.) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matthew@infracaninophile.co.uk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51FA2DEB.40106>