On Tue, 30 Mar 2010, Matthew Pounsett wrote:
named-checkzone doesn't only check the internal consistency of a zone, it also
tries to see that it is externally consistent. e.g. that names referred to in
other zones also exist.
I was amused the day that feature came in without me realising it
:
;smtpedge1.uspto.gov. IN A
;; ANSWER SECTION:
smtpedge1.uspto.gov.7200IN A 151.207.243.76
-Original Message-
From: Matthew Pounsett [mailto:m...@conundrum.com]
Sent: Tuesday, March 30, 2010 5:15 PM
To: Lear, Karen (Evolver)
Cc: 'bind-users@lists.isc.or
On 2010/03/30, at 16:57, Lear, Karen (Evolver) wrote:
>
> I'm adding a new domain to my existing authoritative name servers, and need
> to add an MX record for a device residing on existing domain. When I run
> named-checkzone, I get a message about the MX record being out of zone and
> not
Hello,
named-checkzone is warning you that the MX has a different FQDN than the zone
it is in.
This is fine so long as the "out of zone" MX record is valid, but
named-checkzone wants you to know that it can't verify for sure.
So, it is a heads up message and why the ultimate response is "OK".
I
4 matches
Mail list logo
