TRiG's questions

我希望 Apache 上的域名纯粹作为重定向存在。为此，我创建了/etc/apache2/sites-available/redirect.example.info.conf以下内容：

<VirtualHost *:80>
    ServerName redirect.example.info
    ServerAdmin webmaster@localhost
    Redirect / https://example.com/

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

当我运行的时候certbot --apache，它被重写为：

<VirtualHost *:80>
    ServerName redirect.example.info
    ServerAdmin webmaster@localhost
    Redirect / https://example.com/

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

RewriteEngine on
RewriteCond %{SERVER_NAME} =redirect.example.info
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

/etc/apache2/sites-available/redirect.example.info-le-ssl.conf并创建一个新文件：

<IfModule mod_ssl.c>
<VirtualHost *:443>
    ServerName redirect.example.info
    ServerAdmin webmaster@localhost
    Redirect / https://example.com/

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

SSLCertificateFile /etc/letsencrypt/live/ca-webs.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/ca-webs.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>
</IfModule>

这确实按预期工作。重定向运行http://redirect.example.info→ https://redirect.example.info→ https://example.com。但我不清楚它是如何工作的。重写的文件既有Redirect命令，又有RewriteRule命令，我本以为Redirect（先来）会优先。这个文件实际上是如何评估的？

这是一个在 Apache 上运行 PHP 7 的 Ubuntu 服务器，其网站强制执行 TLS（使用标准端口）。据我了解，https://example.com并且https://example.com:443完全等效（实际上，在我的浏览器中，当我输入端口号时，端口号会从地址栏中消失）。然而，HTTP_HOST 通常只包含域名，但有时还包含端口号。这可能适用于机器人访问者（我没有分析日志），但即便如此我也不知道如何。有什么实际区别吗？

（这会导致一些问题，因为我们的一些日志和工作队列以及服务器端缓存是用 分隔的HTTP_HOST，所以在不同的主机上拥有相同的站点报告会令人困惑。）

我刚刚在我的 Ubuntu 服务器上安装了一些更新。其中一些是内核和 Linux 标头，所以我怀疑需要重新启动，但我想确定。所以，根据这个网站的推荐，我安装了checkrestart.

$ checkrestart
ERROR: This program must be run as root in order to obtain information
about all open file descriptors in the system.

$ sudo !!
sudo checkrestart
Found 0 processes using old versions of upgraded files

唔。不需要重启？这似乎很奇怪。

$ exit
logout
Connection to example.net closed.

$ ssh [email protected] && alert
[email protected]'s password: 
Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-92-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

0 packages can be updated.
0 updates are security updates.


*** System restart required ***

哦。所以需要重启吗？你为什么不这么说？

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"

如何知道安装更新后是否需要重新启动？

我已经在我的小型 Ubuntu 服务器上设置了 Let's Encrypt，并在其上的所有非 IDN 站点上使用它。它可以选择自动将 HTTP 站点重定向到 HTTPS。我选择了那个选项。

Let's Encrypt 守护进程在每个域 conf 中添加了三行，并为每个域创建了一个新的 domain-le-ssl.conf。

这是timothy.green.name.conf：

<VirtualHost *:80>
    # The ServerName directive sets the request scheme, hostname and port that
    # the server uses to identify itself. This is used when creating
    # redirection URLs. In the context of virtual hosts, the ServerName
    # specifies what hostname must appear in the request's Host: header to
    # match this virtual host. For the default virtual host (this file) this
    # value is not decisive as it is used as a last resort host regardless.
    # However, you must set it for any further virtual host explicitly.

    ServerName timothy.green.name
    ServerAdmin [email protected]
    DocumentRoot /var/www/vhosts/timothy.green.name/web

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf
RewriteEngine on
RewriteCond %{SERVER_NAME} =timothy.green.name
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
</VirtualHost>

我创建了这个文件，但是 Let's Encrypt 守护进程在最后添加了重写规则。它还创建了新文件timothy.green.name-le-ssl.conf，内容如下：

<IfModule mod_ssl.c>
<VirtualHost *:443>
    # The ServerName directive sets the request scheme, hostname and port that
    # the server uses to identify itself. This is used when creating
    # redirection URLs. In the context of virtual hosts, the ServerName
    # specifies what hostname must appear in the request's Host: header to
    # match this virtual host. For the default virtual host (this file) this
    # value is not decisive as it is used as a last resort host regardless.
    # However, you must set it for any further virtual host explicitly.

    ServerName timothy.green.name
    ServerAdmin [email protected]
    DocumentRoot /var/www/vhosts/timothy.green.name/web

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf
RewriteEngine on
RewriteCond %{SERVER_NAME} =timothy.green.name
# Some rewrite rules in this file were were disabled on your HTTPS site,
# because they have the potential to create redirection loops.
# RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
SSLCertificateFile /etc/letsencrypt/live/myh2g2.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/myh2g2.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
</IfModule>

这一切看起来都不错。并且mod_rewrite已经到位：

$ a2enmod rewrite
Module rewrite already enabled

然而，虽然https://timothy.green.name工作正常，但http://timothy.green.name给了我一个 Apache 默认站点。这里可能出了什么问题？我要重申，我自己并没有添加这些重写规则：Let's Encrypt 守护进程做到了。所以我假设语法是正确的。

注册商指向我们的名称服务器，我们的名称服务器指向它们自己。如果您查询注册商或我们自己的名称服务器，您会得到相同的响应。但它们有不同的 TTL。客户会尊重哪个 TTL？

$ dig dotser.ie ns @b.iedr.ie

; <<>> DiG 9.8.1-P1 <<>> dotser.ie ns @b.iedr.ie
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1393
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;dotser.ie.         IN  NS

;; AUTHORITY SECTION:
dotser.ie.      172800  IN  NS  ns0.reg365.net.
dotser.ie.      172800  IN  NS  ns2.reg365.net.
dotser.ie.      172800  IN  NS  ns1.reg365.net.

;; Query time: 27 msec
;; SERVER: 77.72.72.34#53(77.72.72.34)
;; WHEN: Thu Sep 11 13:46:12 2014
;; MSG SIZE  rcvd: 91

$ dig dotser.ie ns @ns0.reg365.net

; <<>> DiG 9.8.1-P1 <<>> dotser.ie ns @ns0.reg365.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64285
;; flags: qr aa rd; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;dotser.ie.         IN  NS

;; ANSWER SECTION:
dotser.ie.      86400   IN  NS  ns2.reg365.net.
dotser.ie.      86400   IN  NS  ns1.reg365.net.
dotser.ie.      86400   IN  NS  ns0.reg365.net.

;; Query time: 41 msec
;; SERVER: 85.233.160.79#53(85.233.160.79)
;; WHEN: Thu Sep 11 13:46:28 2014
;; MSG SIZE  rcvd: 91

已经提出了一个非常相似的问题，但它接受的（也是唯一的）答案建议了针对特定问题的解决方法，而不是实际回答理论问题。

另一个类似的问题实际上并不完全相同：它询问名称服务器是否将被缓存比 A 记录更长的时间。（无论如何，那里的答案似乎都没有回答我的问题。）

我的印象是只有子域可以有 CNAME 记录：主域需要定义自己的所有记录。但是，apt-get.com似乎只有一个 CNAME 记录。这怎么行？

$ dig apt-get.com 

; <<>> DiG 9.8.1-P1 <<>> apt-get.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45743
;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;apt-get.com.           IN  A

;; ANSWER SECTION:
apt-get.com.        86336   IN  CNAME   thie5ku9.dsgeneration.com.
thie5ku9.dsgeneration.com. 60   IN  A   208.73.211.242
thie5ku9.dsgeneration.com. 60   IN  A   208.73.211.246
thie5ku9.dsgeneration.com. 60   IN  A   208.73.211.166
thie5ku9.dsgeneration.com. 60   IN  A   208.73.211.232
thie5ku9.dsgeneration.com. 60   IN  A   208.73.211.161
thie5ku9.dsgeneration.com. 60   IN  A   208.73.210.233
thie5ku9.dsgeneration.com. 60   IN  A   208.73.211.186
thie5ku9.dsgeneration.com. 60   IN  A   208.73.211.188

;; Query time: 59 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jun 10 15:05:48 2014
;; MSG SIZE  rcvd: 193


$ dig apt-get.com ns

; <<>> DiG 9.8.1-P1 <<>> apt-get.com ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 43831
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;apt-get.com.           IN  NS

;; Query time: 26 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jun 10 15:12:37 2014
;; MSG SIZE  rcvd: 29


$ dig apt-get.com ns @b.gtld-servers.net

; <<>> DiG 9.8.1-P1 <<>> apt-get.com ns @b.gtld-servers.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38228
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;apt-get.com.           IN  NS

;; AUTHORITY SECTION:
apt-get.com.        172800  IN  NS  ns1.domainrecover.com.
apt-get.com.        172800  IN  NS  ns2.domainrecover.com.

;; ADDITIONAL SECTION:
ns1.domainrecover.com.  172800  IN  A   66.45.232.66
ns2.domainrecover.com.  172800  IN  A   65.23.159.179

;; Query time: 70 msec
;; SERVER: 192.33.14.30#53(192.33.14.30)
;; WHEN: Tue Jun 10 15:07:05 2014
;; MSG SIZE  rcvd: 111

域确实解析。我得到以下标题：

GET / HTTP/1.1
User-Agent: Testing_Sniffer/4.15
Host: apt-get.com
Accept: */*

HTTP/1.0 200 (OK)
Cache-Control: private, no-cache, must-revalidate
Connection: Keep-Alive
Pragma: no-cache
Server: Oversee Turing v1.0.0
Content-Length: 1347
Content-Type: text/html
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Keep-Alive: timeout=3, max=96
P3P: policyref="http://www.dsparking.com/w3c/p3p.xml", CP="NOI DSP COR ADMa OUR NOR STA"
Set-Cookie: parkinglot=1; domain=.apt-get.com; path=/; expires=Wed, 11-Jun-2014 14:10:37 GMT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
<!-- turing_cluster_prod -->
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

    <title>apt-get.com</title>
    <meta name="keywords" content="apt-get.com" />
    <meta name="description" content="apt-get.com" />
    <meta name="robots" content="index, follow" />
    <meta name="revisit-after" content="10" />


    <meta name="viewport" content="width=device-width, initial-scale=1.0" /> 



    <script type="text/javascript">
      document.cookie = "jsc=1";
    </script>

  </head>
  <frameset rows="100%,*" frameborder="no" border="0" framespacing="0">
    <frame src="http://apt-get.com?epl=5PfLSSqWrYDAt-gbwMDK_rA3b1UJCYVTJHfxTzr9FTDQV84b6vAgVhU3FTeCRQNiuRNv79Ni0V3mkEVNRhpqo2gpMjp5iOIR1w2_EISPENaqzoXohVXl2QI3ryXlRCB4FaIIaxynnWXWY6QBgBgNiIZ6agD1NBoNGg0ajXpUCXUAIJDer78AAOB_AwAAQIDbCwAAe_NWlVlTJllBMTZoWkKPAAAA8A" name="apt-get.com">
  </frameset>
  <noframes>
    <body><a href="http://apt-get.com?epl=5PfLSSqWrYDAt-gbwMDK_rA3b1UJCYVTJHfxTzr9FTDQV84b6vAgVhU3FTeCRQNiuRNv79Ni0V3mkEVNRhpqo2gpMjp5iOIR1w2_EISPENaqzoXohVXl2QI3ryXlRCB4FaIIaxynnWXWY6QBgBgNiIZ6agD1NBoNGg0ajXpUCXUAIJDer78AAOB_AwAAQIDbCwAAe_NWlVlTJllBMTZoWkKPAAAA8A">Click here to go to apt-get.com</a>.</body>
  </noframes>
</html>

我在example.com. MX 记录是10 cp.example.net. 这些域位于两个不同的 IP 地址上。假设它example.com位于 198.51.100.0 上，而example.net和cp.example.net位于 203.0.113.0 上。外发邮件也来自cp.example.net.

在我看来，我可以通过几种不同的方式在 SPF 记录中指出这些信息：

传出邮件与传入邮件来自同一个地方：

v=spf1 mx -all

外发邮件来自cp.example.net：

v=spf1 a:cp.example.net -all

外发邮件来自 203.0.113.0：

v=spf1 ip4:203.0.113.0 -all

这些表示相同信息的不同方式之间有什么区别吗？有什么理由更喜欢其中一个吗？（我倾向于支持第一个，因为它更短，但如果有任何技术原因更喜欢其他一个，我会全力以赴。）

我无法连接到 Tullamore Toastmasters 网站。

对 A 记录或 NS 记录的 DiG 请求不返回任何结果。（如下所示的请求。）但是，WHOIS 查询确实列出了名称服务器。直接发送到这些名称服务器的 DiG 请求确实 按预期解决。因此，即使在 WHOIS 响应中列出了这些名称服务器，也不会以某种方式对其进行检查。这里会发生什么？

大约一个月前该域工作正常，然后突然停止，我想不出什么原因。

trig@trig:~$ dig tullamoretoastmasters.org a

; <<>> DiG 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu1 <<>> tullamoretoastmasters.org a
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40050
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tullamoretoastmasters.org. IN  A

;; AUTHORITY SECTION:
org.            50  IN  SOA a0.org.afilias-nst.info. noc.afilias-nst.info. 2010795773 1800 900 604800 86400

;; Query time: 90 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Sat Nov 30 22:54:36 GMT 2013
;; MSG SIZE  rcvd: 117

trig@trig:~$ dig tullamoretoastmasters.org ns

; <<>> DiG 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu1 <<>> tullamoretoastmasters.org ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24884
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tullamoretoastmasters.org. IN  NS

;; AUTHORITY SECTION:
org.            47  IN  SOA a0.org.afilias-nst.info. noc.afilias-nst.info. 2010795773 1800 900 604800 86400

;; Query time: 85 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Sat Nov 30 22:54:39 GMT 2013
;; MSG SIZE  rcvd: 117

trig@trig:~$ whois tullamoretoastmasters.org
Access to .ORG WHOIS information is provided to assist persons in 
determining the contents of a domain name registration record in the 
Public Interest Registry registry database. The data in this record is provided by 
Public Interest Registry for informational purposes only, and Public Interest Registry does not 
guarantee its accuracy.  This service is intended only for query-based 
access. You agree that you will use this data only for lawful purposes 
and that, under no circumstances will you use this data to: (a) allow, 
enable, or otherwise support the transmission by e-mail, telephone, or 
facsimile of mass unsolicited, commercial advertising or solicitations 
to entities other than the data recipient's own existing customers; or 
(b) enable high volume, automated, electronic processes that send 
queries or data to the systems of Registry Operator, a Registrar, or 
Afilias except as reasonably necessary to register domain names or 
modify existing registrations. All rights reserved. Public Interest Registry reserves 
the right to modify these terms at any time. By submitting this query, 
you agree to abide by this policy. 

Domain ID:D163285005-LROR
Domain Name:TULLAMORETOASTMASTERS.ORG
Created On:11-Sep-2011 04:20:33 UTC
Last Updated On:26-Oct-2013 23:00:20 UTC
Expiration Date:11-Sep-2014 04:20:33 UTC
Sponsoring Registrar:Blacknight Internet Solutions Ltd. (R1806-LROR)
Status:CLIENT TRANSFER PROHIBITED
Status:HOLD
Status:PENDINGDELETE
Registrant ID:BK-33567
Registrant Name:Jennifer Dillon
Registrant Street1:Ballycommon
Registrant Street2:
Registrant Street3:
Registrant City:Tullamore
Registrant State/Province:Co. Offaly
Registrant Postal Code:00000
Registrant Country:IE
Registrant Phone:+353.877608117
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant Email:[email protected]
Admin ID:BK-33567
Admin Name:Jennifer Dillon
Admin Street1:Ballycommon
Admin Street2:
Admin Street3:
Admin City:Tullamore
Admin State/Province:Co. Offaly
Admin Postal Code:00000
Admin Country:IE
Admin Phone:+353.877608117
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin Email:[email protected]
Tech ID:BK-33567
Tech Name:Jennifer Dillon
Tech Street1:Ballycommon
Tech Street2:
Tech Street3:
Tech City:Tullamore
Tech State/Province:Co. Offaly
Tech Postal Code:00000
Tech Country:IE
Tech Phone:+353.877608117
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech Email:[email protected]
Name Server:NS1.YOURDOTSER.COM
Name Server:NS2.YOURDOTSER.COM
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
DNSSEC:Unsigned


trig@trig:~$ dig tullamoretoastmasters.org a @ns1.yourdotser.com

; <<>> DiG 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu1 <<>> tullamoretoastmasters.org a @ns1.yourdotser.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29954
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tullamoretoastmasters.org. IN  A

;; ANSWER SECTION:
tullamoretoastmasters.org. 86400 IN A   79.140.130.6

;; AUTHORITY SECTION:
tullamoretoastmasters.org. 86400 IN NS  ns2.tullamoretoastmasters.org.
tullamoretoastmasters.org. 86400 IN NS  ns1.tullamoretoastmasters.org.

;; ADDITIONAL SECTION:
ns1.tullamoretoastmasters.org. 86400 IN A   79.140.130.4
ns2.tullamoretoastmasters.org. 86400 IN A   79.140.130.5

;; Query time: 79 msec
;; SERVER: 79.140.130.4#53(79.140.130.4)
;; WHEN: Sat Nov 30 22:54:52 GMT 2013
;; MSG SIZE  rcvd: 138

trig@trig:~$ dig tullamoretoastmasters.org a @ns2.yourdotser.com

; <<>> DiG 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu1 <<>> tullamoretoastmasters.org a @ns2.yourdotser.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18957
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;tullamoretoastmasters.org. IN  A

;; ANSWER SECTION:
tullamoretoastmasters.org. 86400 IN A   79.140.130.6

;; AUTHORITY SECTION:
tullamoretoastmasters.org. 86400 IN NS  ns2.tullamoretoastmasters.org.
tullamoretoastmasters.org. 86400 IN NS  ns1.tullamoretoastmasters.org.

;; ADDITIONAL SECTION:
ns1.tullamoretoastmasters.org. 86400 IN A   79.140.130.4
ns2.tullamoretoastmasters.org. 86400 IN A   79.140.130.5

;; Query time: 99 msec
;; SERVER: 79.140.130.5#53(79.140.130.5)
;; WHEN: Sat Nov 30 22:54:57 GMT 2013
;; MSG SIZE  rcvd: 138

我们在邮件队列中有很多来自某个地址的邮件。我想删除很多。我找到了按主题行删除的方法，但我想按发件人地址搜索，这似乎要棘手得多。（注意：这些主要是传出消息。）

一些谷歌搜索在HowToForge上找到了我这个命令，但没有解释它的作用。

postqueue -p | tail -n +2 | awk 'BEGIN { RS = "" } / spammer@example\.net/ { print $1 }' | tr -d '*!' | postsuper -d - 

我试图使用mailqueuemng，但并没有走得太远（它没有--help，一方面）。

在共享主机上，当服务器的/tmp目录已满时，我们偶尔会遇到问题。我们的托管公司建议我们将会话保存路径更改为对每个站点都是唯一的。

ini_set('session.save_path', DOCUMENT_ROOT . '/_SESSIONS/');

是的，这将我们的会话置于网络根目录中。.htacces我们通过在该文件夹中包含一个文件来处理潜在的隐私问题：

deny from all

这行得通。

我们现在已经转移到我们自己的托管服务器。此服务器上的默认会话保存路径是/var/lib/php/session. 是否有充分的理由继续将其覆盖到/var/www/vhosts/example.net/httpdocs/_SESSIONS/？

假设我有一个域“example.com”，它可以在有和没有“www”的情况下使用。字首。

假设我有一个名为“extra”的文件夹。

当有人访问 www.example.com/extra 时，我希望 Apache 将他们重定向到 www.example.com/extra/。但不是！相反，它们被发送到 example.com/extra/。失去 www。前缀意味着（a）新会话生成，用户退出，（b）安全证书失效。

我在共享托管平台（hsphere）上使用 Apache。

.htaccess 文件如下：

ErrorDocument 500 "<h2>Application error</h2>Web application failed to start properly"

<IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.+)$ index.php/$1
</IfModule>