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
  • 相关阅读:
    从零实现一个http服务器
    服务器端编程心得(七)——开源一款即时通讯软件的源码
    服务器端编程心得(六)—— 关于网络编程的一些实用技巧和细节
    服务器编程心得(五)—— 如何编写高性能日志
    以芯片直读方式得到的Android全盘镜像解析——DOS分区
    一款开源数据恢复工具——scalpel
    以芯片直读方式得到的全盘镜像解析及ext4日志区域解析——GPT分区
    Linux程序设计之shell程序设计
    算法——蛮力法之最近对问题和凸包问题
    算法——蛮力法之顺序查找和蛮力字符串匹配
  • 原文地址:https://www.cnblogs.com/randomlee/p/Saltstack_module_dig.html
Copyright © 2011-2022 走看看