On 10/15/2013 05:03 PM, Blake Hudson wrote:
Wietse Venema wrote the following on 10/15/2013 9:55 AM:
Wietse Venema:
The DNS query is made by the SYSTEM LIBRARY functions getnameinfo()
and getaddrinfo(). Postfix has no control over how they work.
When I test this with Postfix test programs for these functions:
% ./getnameinfo 216.163.249.229
Hostname: ms.metlifeleads.com
Address: 216.163.249.229
% ./getaddrinfo ms.metlifeleads.com
Hostname: ms.metlifeleads.com
Addresses: 216.163.249.229
(The test programs are in the Postfix source code distribution
under auxiliary/name-addr-test/)
My non-Linux system returns one PTR result (ms.metlifeleads.com);
the A record for this name is 216.163.249.229, and Postfix would
be satisfied with the result.
I get a similar result on a Linux box:
$ ./getnameinfo 216.163.249.229
Hostname: ms2.smrsmetlife.com
Address: 216.163.249.229
$ ./getaddrinfo ms2.smrsmetlife.com
Hostname: ms2.smrsmetlife.com
Addresses: 216.163.249.229
Again, Postfix should work OK with this.
I'm starting to suspect that the OP may have a bad DNS implementation.
Maybe some cheap router?
I suspect that it doesn't work this way on your system. Some Linux
distributions require extra configuration to handle more than reply
per query. I have forgotten what the option is.
This is the "multi on" option in /etc/host.conf; documentation
says that this affects /etc/hosts lookups, so not applicable to
DNS queries.
Wietse
This is utterly reproducible for me; running a local BIND 9.9.2 on
Slackware 14.0/kernel 3.2.29:
root@fusion:~# dig @ns.metlife.com -x 216.163.249.229 +ignore
; <<>> DiG 9.9.2-P2 <<>> @ns.metlife.com -x 216.163.249.229 +ignore
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
root@fusion:~# dig -v
DiG 9.9.2-P2
root@fusion:~# dig @ns3.metlife.com -x 216.163.249.229 +ignore
; <<>> DiG 9.9.2-P2 <<>> @ns3.metlife.com -x 216.163.249.229 +ignore
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
root@fusion:~# dig @ns2.metlife.com -x 216.163.249.229 +ignore
; <<>> DiG 9.9.2-P2 <<>> @ns2.metlife.com -x 216.163.249.229 +ignore
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55576
;; flags: qr aa tc rd ra; QUERY: 1, ANSWER: 38, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;229.249.163.216.in-addr.arpa. IN PTR
;; ANSWER SECTION:
229.249.163.216.in-addr.arpa. 1800 IN PTR ms.tlcmetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.metaddisppm.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.metcommpipedev.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.met_smartoffice.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.metcaretngprodmetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.massmetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.metecap.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.instmetdba.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms.metcommpipe.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms.metconnect.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.metbusiness.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.metlifeitrisk.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms.wpsgenamerica.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.metsdo.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.orangesmmetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.crcsurfmetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.meteas.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.metpaybase.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.pmacsmetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.instmetdbaqa.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.nbcwebsitemetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR entlic.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.ctxprod.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.prod-erpdbametlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.efabusobj.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.dmmetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.qeintranetmetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.csametlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms.metdeploy.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms.metlifeleads.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.lifemetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR
www.fegli2004.com.249.163.216.in-addr.arpa.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms1.metlifeforms.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms.meteservice.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms.metcommercialservices.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.internallidmetlife.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR
ms.mao-ev15fixedannualstatements.com.
229.249.163.216.in-addr.arpa. 1800 IN PTR ms2.qeconsumermetlife.com.
;; Query time: 132 msec
;; SERVER: 216.163.240.251#53(216.163.240.251)
;; WHEN: Wed Oct 16 00:22:11 2013
;; MSG SIZE rcvd: 1247
It seems totally random, and apparently bound by geographic location (I
am not in the US).
The previous query to ns2 returned over 120 records, and different ones
kept showing up for every repeat query.
Let's hope they are better at guarding your insurance money :)
--
J.
