zoukankan      html  css  js  c++  java
  • Saltstack module dig 详解

    dig.mx

    Return a list of lists for the MX of ``domain``.
    
    If the ``resolve`` argument is True, resolve IPs for the servers.
    
    It's limited to one IP, because although in practice it's very rarely a
    round robin, it is an acceptable configuration and pulling just one IP lets
    the data be similar to the non-resolved version. If you think an MX has
    multiple IPs, don't use the resolver here, resolve them in a separate step.
    
    CLI Example:
    
        salt ns1 dig.MX google.com
    

    dig.AAAA

    Return the AAAA record for ``host``.
    
    Always returns a list.
    
    CLI Example:
    
        salt ns1 dig.AAAA www.google.com
    

    dig.a

    Return the A record for ``host``.
    
    Always returns a list.
    
    CLI Example:
    
        salt ns1 dig.A www.google.com
    

    dig.A

    Return the A record for ``host``.
    
    Always returns a list.
    
    CLI Example:
    
        salt ns1 dig.A www.google.com
    

    dig.ns

    Return a list of IPs of the nameservers for ``domain``
    
    If ``resolve`` is False, don't resolve names.
    
    CLI Example:
    
        salt ns1 dig.NS google.com
    

    dig.spf

    Return the allowed IPv4 ranges in the SPF record for ``domain``.
    
    If record is ``SPF`` and the SPF record is empty, the TXT record will be
    searched automatically. If you know the domain uses TXT and not SPF,
    specifying that will save a lookup.
    
    CLI Example:
    
        salt ns1 dig.SPF google.com
    

    dig.aaaa

    Return the AAAA record for ``host``.
    
    Always returns a list.
    
    CLI Example:
    
        salt ns1 dig.AAAA www.google.com
    

    dig.NS

    Return a list of IPs of the nameservers for ``domain``
    
    If ``resolve`` is False, don't resolve names.
    
    CLI Example:
    
        salt ns1 dig.NS google.com
    

    dig.MX

    Return a list of lists for the MX of ``domain``.
    
    If the ``resolve`` argument is True, resolve IPs for the servers.
    
    It's limited to one IP, because although in practice it's very rarely a
    round robin, it is an acceptable configuration and pulling just one IP lets
    the data be similar to the non-resolved version. If you think an MX has
    multiple IPs, don't use the resolver here, resolve them in a separate step.
    
    CLI Example:
    
        salt ns1 dig.MX google.com
    

    dig.SPF

    Return the allowed IPv4 ranges in the SPF record for ``domain``.
    
    If record is ``SPF`` and the SPF record is empty, the TXT record will be
    searched automatically. If you know the domain uses TXT and not SPF,
    specifying that will save a lookup.
    
    CLI Example:
    
        salt ns1 dig.SPF google.com
    

    dig.check_ip

    Check if address is a valid IP. returns True if valid, otherwise False.
    
    CLI Example:
    
        salt ns1 dig.check_ip 127.0.0.1
        salt ns1 dig.check_ip 1111:2222:3333:4444:5555:6666:7777:8888
    

    dig.TXT

    Return the TXT record for ``host``.
    
    Always returns a list.
    
    CLI Example:
    
        salt ns1 dig.TXT google.com
  • 相关阅读:
    Data Structure(2)
    CoreAnimation —— CALayer
    [置顶] android AIDL 进程间通信
    UVA 10057 A mid-summer night's dream. 仲夏夜之梦 求中位数
    基于mini2440的IIC读写(裸机)
    外媒关注:中国法庭用新浪微薄直播薄熙来审判
    [置顶] 吃论扯谈---吃货和Office 365订阅的关系
    小智慧42
    机器学习如何选择模型 & 机器学习与数据挖掘区别 & 深度学习科普
    【Todo】【转载】Spark学习 & 机器学习(实战部分)-监督学习、分类与回归
  • 原文地址:https://www.cnblogs.com/randomlee/p/Saltstack_module_dig.html
Copyright © 2011-2022 走看看