Either way - it breaks Sendmail, some versions of Exchange, and possibly
other MTA's. The proper answer to a non-existent AAAA record is
NOERROR, with ANSWER 0.
Hanging or refusing to answer doesn't result in another attempt to look
for an A record since the name server failed to respond to a valid
query. Given that the whole point of the domain is to enable email
printing, HP isn't making it easy.
Mark
On 5/3/14, 4:18 PM, Scott Howard wrote:
On Sat, May 3, 2014 at 6:27 AM, Mark Radabaugh <m...@amplex.net
<mailto:m...@amplex.net>> wrote:
Dear HP:
If your not going to support IPv6 can you at least not return
SRVFAIL when asked for an AAAA record:
They aren't. Your resolver is - or at least, that's what it looks
like for me.
Sending an AAAA query to their nameservers times out for me - no
response at all. Sending the same query through certain resolvers
(eg, Google) seems to result in the timeout being turned into a SERVFAIL.
$ dig AAAA onramp01.hpeprint.com <http://onramp01.hpeprint.com>
; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> AAAA onramp01.hpeprint.com
<http://onramp01.hpeprint.com>
;; global options: +cmd
;; connection timed out; no servers could be reached
Same via Google :
$ dig AAAA onramp01.hpeprint.com <http://onramp01.hpeprint.com>
@8.8.8.8 <http://8.8.8.8>
; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> AAAA onramp01.hpeprint.com
<http://onramp01.hpeprint.com> @8.8.8.8 <http://8.8.8.8>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 26319
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
Scott
--
Mark Radabaugh
Amplex
m...@amplex.net 419.837.5015 x 1021