• 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
  • 相关阅读:
    Qt4.7.4下单独编译QtWebkit
    CronHowto Community Ubuntu Documentation
    菜鸟学Python(9):给文件添加内容,得到文件信息
    yet another software souring company based on san franciso
    Get Started With Chickenfoot
    Berkeley DB(四) DB Environment
    搭建SSH框架链接Oracle数据库
    Linux下手动编译安装Apache2.x
    Errore HTTP 404.2 Not Found" IIS 7.5 请求的内容似乎是脚本,因而将无法由静态文件处理程序来处理
    关于二分法中取中间值时向下和向上取整的问题(由大白LA3971想到的)
  • 原文地址:https://www.cnblogs.com/randomlee/p/Saltstack_module_dig.html
Copyright © 2020-2023  润新知