Guten Abend Freunde,
ich wollte gerne einmal wissen, ob es bei meinem Pi-hole Debug Log etwas zu beanstanden gibt, weil ich gesehen habe das ziemlich weit unten Warnungen drinstehen. Muss ich mir da Sorgen machen wie kann ich diese Warnungen beheben. Jetzt erstmal zu meinem Setup: Ich habe einen Raspberry Pi 3B+ und eine FRITZ!Box 6590 Cable. Auf dem Pi laufen neben dem Pi-hole noch Unbound, Hyperlocal und WireGuard. Bei der FRITZ!Box habe ich unter Heimnetzwerk -> Netzwerkeinstellungen- IPv4 Adressen die IP vom Pi-hole eingetragen und beim Rebind Schutz pi.hole eingetragen. Außerdem habe ich unter Internet -> Zugangsdaten noch die beiden IPv4 Adressen von Cloudflare eingetragen. Desweiteren habe ich bei den DNS Einstellungen des Pi-holes die IP Adresse 127.0.0.1#5335 für Unbound eingetragen und alle Häkchen bis auf Never forward non-FQDNs und Conditional Forwarding deaktiviert und in die Kästchen einmal die IP des Routers eingetragen und fritz.box. Dann habe ich als Nächstes den Punkt Listen on all interfaces
Allows only queries from devices that are at most one hop away (local devices) aktiviert, weil das bei der Installationsanleitung von WireGuard empfohlen wurde. Falls ihr noch weitere Fragen zu meinem Setup habt immer her damit! Anbei eine Kopie vom Debug Log. Ich habe die von mir gemeinte Stelle mit dicker Schrift markiert. Ich bedanke mich schon Mal im Voraus für eure Antworten
Gruß
Sercan
This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.
The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.
NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.
*** [ INITIALIZING ]
[i] 2020-02-05:22:58:33 debug log has been initialized.
*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...
*** [ DIAGNOSING ]: Core version
[i] Core: v4.3.2 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v4.3.2-0-ge41c4b5
*** [ DIAGNOSING ]: Web version
[i] Web: v4.3.2 (How do I update Pi-hole?)
[i] Branch: master
[i] Commit: v4.3.2-0-g38d8e77
*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.3.1
*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.53
*** [ DIAGNOSING ]: php version
[i] 7.3.11
*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 10 (buster)
*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected
*** [ DIAGNOSING ]: Processor
[✓] armv7l
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth1 interface:
192.168.178.xx/24 matches the IP found in /etc/pihole/setupVars.conf
[✓] IPv6 address(es) bound to the eth1 interface:
fe80::e3a8:1e49:c8bc:xxxx does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)
^ Please note that you may have more than one IP address listed.
As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.
The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.
[i] Default IPv4 gateway: 192.168.178.xx
- Pinging 192.168.178.xx...
[✓] Gateway responded.
*** [ DIAGNOSING ]: Ports in use
:22 sshd (IPv4)
:22 sshd (IPv6)
127.0.0.1:5335 unbound (IPv4)
[:80] is in use by lighttpd
[:80] is in use by lighttpd
[:53] is in use by pihole-FTL
[:53] is in use by pihole-FTL
[127.0.0.1:4711] is in use by pihole-FTL
[[::1]:4711] is in use by pihole-FTL
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] tu.connect.wunderloop.net is 0.0.0.0 via localhost (127.0.0.1)
[✓] tu.connect.wunderloop.net is 0.0.0.0 via Pi-hole (192.168.178.xx)
[✓] doubleclick.com is 172.217.22.110 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Pi-hole processes
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active
*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth1
IPV4_ADDRESS=192.168.178.xx/24
IPV6_ADDRESS=
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
BLOCKING_ENABLED=true
HOSTRECORD=raspberrypivonsercan.xxxxx.de,192.168.178.xx
DNSMASQ_LISTENING=local
PIHOLE_DNS_1=127.0.0.1#5335
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=false
DNSSEC=false
CONDITIONAL_FORWARDING=true
CONDITIONAL_FORWARDING_IP=192.168.178.xx
CONDITIONAL_FORWARDING_DOMAIN=fritz.box
CONDITIONAL_FORWARDING_REVERSE=178.168.192.in-addr.arpa
*** [ DIAGNOSING ]: Dashboard and block page
[✓] Block page X-Header: X-Pi-hole: A black hole for Internet advertisements.
[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!
*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 2899034 Feb 3 06:40 /etc/pihole/gravity.list
-----head of gravity.list------
0.0.0.0
0.nextyourcontent.com
0.r.msn.com
0.start.bz
-----tail of gravity.list------
zzz.clickbank.net
zzzezeroe.fr
zzzpooeaz-france.com
zzzrtrcm2.com
*** [ DIAGNOSING ]: contents of /etc/pihole
-rw-r--r-- 1 root root 313 Jan 26 16:21 /etc/pihole/adlists.list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
https://hosts-file.net/ad_servers.txt
-rw-r--r-- 1 root root 0 Feb 1 16:31 /etc/pihole/blacklist.txt
-rw-r--r-- 1 root root 50 Feb 3 06:40 /etc/pihole/local.list
192.168.178.xx raspberrypi
192.168.178.xx pi.hole
-rw-r--r-- 1 root root 234 Jan 26 16:23 /etc/pihole/logrotate
/var/log/pihole.log {
su root root
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole-FTL.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}
-rw-r--r-- 1 root root 0 Jan 26 16:49 /etc/pihole/whitelist.txt
*** [ DIAGNOSING ]: contents of /etc/dnsmasq.d
-rw-r--r-- 1 root root 1524 Feb 5 18:21 /etc/dnsmasq.d/01-pihole.conf
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=0
log-queries
log-facility=/var/log/pihole.log
local-ttl=2
log-async
server=127.0.0.1
domain-needed
host-record=raspberrypivonsercan.xxxxx.de,192.168.178.Xx
local-service
server=/fritz.box/192.168.178.xx
server=/178.168.192.in-addr.arpa/192.168.178.xx
*** [ DIAGNOSING ]: contents of /etc/lighttpd
-rw-r--r-- 1 root root 3499 Jan 26 16:23 /etc/lighttpd/lighttpd.conf
server.modules = (
"mod_access",
"mod_accesslog",
"mod_auth",
"mod_expire",
"mod_compress",
"mod_redirect",
"mod_setenv",
"mod_rewrite"
)
server.document-root = "/var/www/html"
server.error-handler-404 = "/pihole/index.php"
server.upload-dirs = ( "/var/cache/lighttpd/uploads" )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname = "www-data"
server.port = 80
accesslog.filename = "/var/log/lighttpd/access.log"
accesslog.format = "%{%s}t|%V|%r|%s|%b"
index-file.names = ( "index.php", "index.html", "index.lighttpd.html" )
url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" )
static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( "application/javascript", "text/css", "text/html", "text/plain" )
mimetype.assign = ( ".png" => "image/png",
".jpg" => "image/jpeg",
".jpeg" => "image/jpeg",
".html" => "text/html",
".css" => "text/css; charset=utf-8",
".js" => "application/javascript",
".json" => "application/json",
".txt" => "text/plain",
".svg" => "image/svg+xml" )
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include "%p"
' 2>/dev/null"
$HTTP["url"] =~ "^/admin/" {
setenv.add-response-header = (
"X-Pi-hole" => "The Pi-hole Web interface is working!",
"X-Frame-Options" => "DENY"
)
$HTTP["url"] =~ ".ttf$" {
setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
}
}
$HTTP["url"] =~ "^/admin/.(.*)" {
url.access-deny = ("")
}
include_shell "cat external.conf 2>/dev/null"
*** [ DIAGNOSING ]: contents of /etc/cron.d
-rw-r--r-- 1 root root 1704 Jan 26 16:23 /etc/cron.d/pihole
56 3 * * 7 root PATH="$PATH:/usr/local/bin/" pihole updateGravity >/var/log/pihole_updateGravity.log || cat /var/log/pihole_updateGravity.log
00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet
@reboot root /usr/sbin/logrotate /etc/pihole/logrotate
*/10 * * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker local
46 13 * * * root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote
@reboot root PATH="$PATH:/usr/local/bin/" pihole updatechecker remote reboot
*** [ DIAGNOSING ]: contents of /var/log/lighttpd
-rw-r--r-- 1 www-data www-data 2373 Feb 5 20:52 /var/log/lighttpd/error.log
2020-02-02 00:00:40: (server.c.1759) logfiles cycled UID = 0 PID = 3475
2020-02-02 11:22:34: (server.c.2059) server stopped by UID = 0 PID = 1
2020-02-02 11:22:51: (server.c.1464) server started (lighttpd/1.4.53)
2020-02-02 11:22:51: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
2020-02-02 22:46:23: (server.c.2059) server stopped by UID = 0 PID = 1
2020-02-02 22:46:45: (server.c.1464) server started (lighttpd/1.4.53)
2020-02-02 22:46:45: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
2020-02-02 23:08:22: (server.c.2059) server stopped by UID = 0 PID = 1
2020-02-02 23:08:39: (server.c.1464) server started (lighttpd/1.4.53)
2020-02-02 23:08:39: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
2020-02-02 23:59:04: (server.c.2059) server stopped by UID = 0 PID = 1
2020-02-02 23:59:21: (server.c.1464) server started (lighttpd/1.4.53)
2020-02-02 23:59:21: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
2020-02-03 00:21:50: (server.c.2059) server stopped by UID = 0 PID = 1
2020-02-03 00:22:06: (server.c.1464) server started (lighttpd/1.4.53)
2020-02-03 00:22:06: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
2020-02-04 06:45:00: (server.c.2059) server stopped by UID = 0 PID = 1
2020-02-04 06:45:15: (server.c.1464) server started (lighttpd/1.4.53)
2020-02-04 06:45:15: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
2020-02-05 17:11:14: (server.c.2059) server stopped by UID = 0 PID = 1
2020-02-05 17:11:30: (server.c.1464) server started (lighttpd/1.4.53)
2020-02-05 17:11:30: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
2020-02-05 17:25:33: (server.c.2059) server stopped by UID = 0 PID = 1
2020-02-05 17:25:49: (server.c.1464) server started (lighttpd/1.4.53)
2020-02-05 17:25:49: (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
*** [ DIAGNOSING ]: contents of /var/log
-rw-r--r-- 1 pihole pihole 27308 Feb 5 20:53 /var/log/pihole-FTL.log
-----head of pihole-FTL.log------
[2020-02-05 01:11:59.274 691] Resizing "/FTL-strings" from 24576 to 28672
[2020-02-05 15:11:24.013 691] Resizing "/FTL-strings" from 28672 to 32768
[2020-02-05 17:11:14.399 691] Shutting down...
[2020-02-05 17:11:14.710 691] Finished final database update
[2020-02-05 17:11:14.711 691] ########## FTL terminated after 123955104.0 ms! ##########
[2020-02-05 17:11:34.705 692] Using log file /var/log/pihole-FTL.log
[2020-02-05 17:11:34.706 692] ########## FTL started! ##########
[2020-02-05 17:11:34.706 692] FTL branch: master
[2020-02-05 17:11:34.706 692] FTL version: v4.3.1
[2020-02-05 17:11:34.706 692] FTL commit: b60d63f
[2020-02-05 17:11:34.706 692] FTL date: 2019-05-25 21:37:26 +0200
[2020-02-05 17:11:34.706 692] FTL user: pihole
[2020-02-05 17:11:34.707 692] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2020-02-05 17:11:34.707 692] SOCKET_LISTENING: only local
[2020-02-05 17:11:34.707 692] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2020-02-05 17:11:34.707 692] MAXDBDAYS: max age for stored queries is 90 days
[2020-02-05 17:11:34.707 692] RESOLVE_IPV6: Resolve IPv6 addresses
[2020-02-05 17:11:34.707 692] RESOLVE_IPV4: Resolve IPv4 addresses
[2020-02-05 17:11:34.707 692] DBINTERVAL: saving to DB file every 3600 seconds
[2020-02-05 17:11:34.707 692] DBFILE: Using /etc/pihole/pihole-FTL.db
[2020-02-05 17:11:34.707 692] MAXLOGAGE: Importing up to 24.0 hours of log data
[2020-02-05 17:11:34.707 692] PRIVACYLEVEL: Set to 0
[2020-02-05 17:11:34.707 692] IGNORE_LOCALHOST: Show queries from localhost
[2020-02-05 17:11:34.707 692] BLOCKINGMODE: Null IPs for blocked domains
[2020-02-05 17:11:34.707 692] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
[2020-02-05 17:11:34.707 692] DBIMPORT: Importing history from database
[2020-02-05 17:11:34.707 692] PIDFILE: Using /var/run/pihole-FTL.pid
[2020-02-05 17:11:34.707 692] PORTFILE: Using /var/run/pihole-FTL.port
[2020-02-05 17:11:34.707 692] SOCKETFILE: Using /var/run/pihole/FTL.sock
[2020-02-05 17:11:34.707 692] WHITELISTFILE: Using /etc/pihole/whitelist.txt
[2020-02-05 17:11:34.708 692] BLACKLISTFILE: Using /etc/pihole/black.list
[2020-02-05 17:11:34.708 692] GRAVITYFILE: Using /etc/pihole/gravity.list
[2020-02-05 17:11:34.708 692] REGEXLISTFILE: Using /etc/pihole/regex.list
[2020-02-05 17:11:34.708 692] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
[2020-02-05 17:11:34.708 692] AUDITLISTFILE: Using /etc/pihole/auditlog.list
-----tail of pihole-FTL.log------
[2020-02-05 20:53:02.675 693] REGEXLISTFILE: Using /etc/pihole/regex.list
[2020-02-05 20:53:02.675 693] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
[2020-02-05 20:53:02.675 693] AUDITLISTFILE: Using /etc/pihole/auditlog.list
[2020-02-05 20:53:02.675 693] MACVENDORDB: Using /etc/pihole/macvendor.db
[2020-02-05 20:53:02.675 693] PARSE_ARP_CACHE: Active
[2020-02-05 20:53:02.675 693] Finished config file parsing
[2020-02-05 20:53:02.681 693] Database version is 3
[2020-02-05 20:53:02.681 693] Database successfully initialized
[2020-02-05 20:53:02.708 693] New forward server: 127.0.0.1 (0/512)
[2020-02-05 20:53:02.708 693] New forward server: 192.168.178.1 (1/512)
[2020-02-05 20:53:02.711 693] Resizing "/FTL-strings" from 4096 to 8192
[2020-02-05 20:53:02.722 693] Resizing "/FTL-strings" from 8192 to 12288
[2020-02-05 20:53:02.736 693] Resizing "/FTL-strings" from 12288 to 16384
[2020-02-05 20:53:02.749 693] Resizing "/FTL-strings" from 16384 to 20480
[2020-02-05 20:53:02.763 693] Resizing "/FTL-strings" from 20480 to 24576
[2020-02-05 20:53:02.764 693] Resizing "/FTL-queries" from 196608 to 393216
[2020-02-05 20:53:02.768 693] Imported 4424 queries from the long-term database
[2020-02-05 20:53:02.768 693] -> Total DNS queries: 4424
[2020-02-05 20:53:02.768 693] -> Cached DNS queries: 22
[2020-02-05 20:53:02.768 693] -> Forwarded DNS queries: 2679
[2020-02-05 20:53:02.769 693] -> Exactly blocked DNS queries: 1723
[2020-02-05 20:53:02.769 693] -> Unknown DNS queries: 0
[2020-02-05 20:53:02.769 693] -> Unique domains: 915
[2020-02-05 20:53:02.769 693] -> Unique clients: 8
[2020-02-05 20:53:02.769 693] -> Known forward destinations: 2
[2020-02-05 20:53:02.769 693] Successfully accessed setupVars.conf
[2020-02-05 20:53:02.775 695] PID of FTL process: 695
[2020-02-05 20:53:02.775 695] Listening on port 4711 for incoming IPv4 telnet connections
[2020-02-05 20:53:02.776 695] Listening on port 4711 for incoming IPv6 telnet connections
[2020-02-05 20:53:02.776 695] Listening on Unix socket
[2020-02-05 20:53:02.780 695] Received SIGHUP, reloading cache
[2020-02-05 20:53:02.781 695] Blocking status is enabled
[2020-02-05 20:53:02.781 695] Compiled 0 Regex filters and 0 whitelisted domains in 0.2 msec (0 errors)
[2020-02-05 20:53:02.783 695] /etc/pihole/black.list: parsed 0 domains (took 0.1 ms)
[2020-02-05 20:53:04.417 695] /etc/pihole/gravity.list: parsed 124928 domains (took 1631.9 ms)
*** [ DIAGNOSING ]: contents of /dev/shm
-rw------- 1 pihole pihole 323584 Feb 5 20:53 /dev/shm/FTL-clients
-rw------- 1 pihole pihole 108 Feb 5 20:53 /dev/shm/FTL-counters
-rw------- 1 pihole pihole 65536 Feb 5 20:53 /dev/shm/FTL-domains
-rw------- 1 pihole pihole 12288 Feb 5 20:53 /dev/shm/FTL-forwarded
-rw------- 1 pihole pihole 28 Feb 5 20:53 /dev/shm/FTL-lock
-rw------- 1 pihole pihole 53248 Feb 5 20:53 /dev/shm/FTL-overTime
-rw------- 1 pihole pihole 393216 Feb 5 20:59 /dev/shm/FTL-queries
-rw------- 1 pihole pihole 12 Feb 5 20:53 /dev/shm/FTL-settings
-rw------- 1 pihole pihole 24576 Feb 5 20:53 /dev/shm/FTL-strings
*** [ DIAGNOSING ]: Locale
LANG=
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 1413392 Feb 5 22:58 /var/log/pihole.log
-----head of pihole.log------
Feb 5 00:00:11 dnsmasq[691]: query[A] dc.di.atlas.samsung.com from 192.168.178.xx
Feb 5 00:00:11 dnsmasq[691]: forwarded dc.di.atlas.samsung.com to 127.0.0.1
Feb 5 00:00:11 dnsmasq[691]: reply dc.di.atlas.samsung.com is
Feb 5 00:00:11 dnsmasq[691]: reply elb-p-dc-dc-ew1-466189800.eu-west-1.elb.amazonaws.com is 18.203.114.239
Feb 5 00:00:11 dnsmasq[691]: reply elb-p-dc-dc-ew1-466189800.eu-west-1.elb.amazonaws.com is 18.202.38.88
Feb 5 00:00:11 dnsmasq[691]: reply elb-p-dc-dc-ew1-466189800.eu-west-1.elb.amazonaws.com is 34.247.94.9
Feb 5 00:00:11 dnsmasq[691]: reply elb-p-dc-dc-ew1-466189800.eu-west-1.elb.amazonaws.com is 34.246.34.49
Feb 5 00:00:11 dnsmasq[691]: reply elb-p-dc-dc-ew1-466189800.eu-west-1.elb.amazonaws.com is 34.248.20.105
Feb 5 00:00:11 dnsmasq[691]: reply elb-p-dc-dc-ew1-466189800.eu-west-1.elb.amazonaws.com is 34.240.106.134
Feb 5 00:00:11 dnsmasq[691]: reply elb-p-dc-dc-ew1-466189800.eu-west-1.elb.amazonaws.com is 54.171.51.46
Feb 5 00:00:11 dnsmasq[691]: reply elb-p-dc-dc-ew1-466189800.eu-west-1.elb.amazonaws.com is 34.250.106.242
Feb 5 00:00:28 dnsmasq[691]: query[A] gateway.icloud.com from 192.168.178.xx
Feb 5 00:00:28 dnsmasq[691]: forwarded gateway.icloud.com to 127.0.0.1
Feb 5 00:00:28 dnsmasq[691]: reply gateway.icloud.com is
Feb 5 00:00:28 dnsmasq[691]: reply gateway.fe.apple-dns.net is 17.248.146.9
Feb 5 00:00:28 dnsmasq[691]: reply gateway.fe.apple-dns.net is 17.248.146.244
Feb 5 00:00:28 dnsmasq[691]: reply gateway.fe.apple-dns.net is 17.248.146.39
Feb 5 00:00:28 dnsmasq[691]: reply gateway.fe.apple-dns.net is 17.248.146.84
Feb 5 00:00:28 dnsmasq[691]: reply gateway.fe.apple-dns.net is 17.248.146.113
Feb 5 00:00:28 dnsmasq[691]: reply gateway.fe.apple-dns.net is 17.248.146.146