What tool are you using to check on the correctnes of a new deployment if you're not using ConfigAdvisor?
Best,
Alexander Griesser Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: AGriesser@anexia-it.com Web: http://www.anexia-it.com
Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
-----Ursprüngliche Nachricht----- Von: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Im Auftrag von Jan-Pieter Cornet Gesendet: Donnerstag, 7. September 2017 14:03 An: John Stoffel john@stoffel.org Cc: toasters@teaparty.net Betreff: Re: DNS Configured Check - High Impact on ConfigAdvisor
On 6-9-17 02:43, John Stoffel wrote:
I agree it could be smarter, but setting up DNS isn't hard either. Just point it to some DNS servers you don't care about, or which are
It can be quite hard to setup DNS.
For example, we have a bunch of SVMs in a metrocluster environment.
Metrocluster needs strechted VLANs, and we really don't like strechting VLANs across sites, so we set it up so that the only VLANs that are strechted, are the NFS VLANs. Those use RFC1918 IP addresses and are not routed.
As a result, those SVMs *cannot* have an IP address that is globally reachable. And they don't need to, either. Using NFSv3 and IP-based access control, and this way the NFS server is properly isolated from everything else.
The only way to set up DNS would be to run a special DNS server inside those VLANs with an extra port to the outside world. However, the SVMs don't need DNS, so we obviously won't do that just to silence a silly warning.
(It's one of the reasons I hardly ever look at configAdvisor. Fortunately hardly anyone wants to look at those reports anyway, mainly netapp support staff).