soem strangeness with 8.2.2 under A/UX with MX records
jim at devsys.jaguNET.com
Fri Nov 5 18:45:21 UTC 1999
Just noticed some strangeness with resolving MX records with 8.2.2
under A/UX. Sometimes named will return just the A records for
a host/domain and not the MX records (when doing, for example,
'host foobar.com'). Other times we'll see something like 'host blarf.com'
return an IP address which is, in fact NOT the A record of the host, but
rather the A record for it's highest priority MX record. For
example, if blarf.com has no A record, but 2 MX records as such:
blarf.com IN MX 10 mx1.blarf.com
blarf.com IN MX 20 mx2.blarf.com
mx1.blarf.com IN A 184.108.40.206
mx2.blarf.com IN A 220.127.116.11
a 'host blarf.com' will return 'has address 18.104.22.168'
Trying to track this down...
Jim Jagielski [|] jim at jaguNET.com [|] http://www.jaguNET.com/
"Are you suggesting coconuts migrate??"
More information about the bind-workers