Please let Verizon support desk know this and get them to fix it, or at least tell customers the work around and that it is a known problem 

Verizon doesn’t use modems. Just routers. If you purchase a high end router like I use Netgear Nighthawk it will be around $400 however the rental for a G3100 is $13 a month with terrible wifi and other issues. So $156 a year times 2 is $312 so it may very well be in your best interest to get a non verizon router.

as the other poster stated your support is only up to the ONT on your home. But routers last for many years and their GUI is easy to understand to make changes. But the ones with external antennas since they reach much farther. And get AC/N or the new faster AX bands which are far superior. It can be cheaper in cost for a TP Link Archer or Asus as well as certain Netgear routers.

you will need to switch over to ethernet from MOCA WAN and you never stated what speed you are provisioned for so that may also be an issue.

The router model is G1100 and the problem only happens on 2.4GHz connection (5GHz and wired are fine).

During the reboot, I noticed all lights go off...followed by the globe turning solid red...followed by a white globe and a white wifi signal. 

Been having various problems with my internet connectivity. One thing I noticed is continual error message in my System Log. Prior to this, the log would show INFORMATION messages every hour. Now it is showing named DNS errors non-stop.

Apr 10 09:04:21 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:04:21 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:04:21 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:04:16 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:02:55 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:02:55 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:02:55 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:02:50 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:01:35 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:01:35 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:01:35 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:01:30 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 08:59:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 08:59:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 08:59:50 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 08:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 07:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 06:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 05:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 04:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 03:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 02:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 01:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 00:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 23:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 22:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 21:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 20:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 19:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 18:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 17:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 16:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 15:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 14:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 13:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 12:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 11:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds

Starting on April 11, 2020, my G1100 router has been logging continual error messages about lighttpd. Does anyone know how to check if a recent update has been pushed to the router? I have been seeing various issues in the past couple of days. Below is a snippet from my AdvancedLog.

Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:54 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:54 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:10 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:02:54 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:02:37 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:02:26 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:44 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:41 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 12:43:35 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587213815, active: 1
Apr 11 10:56:14 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 3658, external host , internal port 3658, internal host 192.168.1.172, timestamp: 1587207374, active: 1
Apr 11 09:02:28 2020 local7.info<190> miniupnpd[1741]: Removing port mapping protocol UDP, external port 3658, external host , internal port 3658, internal host 192.168.1.172
Apr 11 09:02:14 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 3658, external host , internal port 3658, internal host 192.168.1.172, timestamp: 1587200534, active: 1
Apr 11 04:16:17 2020 local7.info<190> miniupnpd[1741]: Removing port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157
Apr 11 04:15:50 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587183350, active: 1
Apr 11 03:53:52 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587182032, active: 1
Apr 11 02:31:44 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587177104, active: 1
Apr 11 01:31:44 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587173504, active: 1
Apr 11 00:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587169899, active: 1
Apr 10 23:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587166299, active: 1
Apr 10 22:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587162699, active: 1
Apr 10 21:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587159099, active: 1
Apr 10 20:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587155499, active: 1
Apr 10 19:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587151899, active: 1
Apr 10 18:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587148299, active: 1
Apr 10 17:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587144699, active: 1
Apr 10 16:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587141099, active: 1

I've seen this suggestion of visiting dslreports.com. Is this site run by Verizon? TBH, it seems weird that Verizon tech would monitor a 3rd party site more than their own forums that they pay to keep up for compute and storage.

I'm curious if anyone knows how to check when their router was last updated. These reboot messages started happening and are labeled with 02.02.00.16

Apr 11 13:08:49 2020 local1.info<142> System: System is now initialized. Reason undefined. Reboot count 9. Running firmware 02.02.00.16 (02.02.00.16_20190528_022627_9fe6379f_jenkins)
Apr 11 13:08:40 2020 uucp.debug<71> System: BHR4 restart event (soft). Reason: undefined
Apr 11 13:08:40 2020 local1.debug<143> System: BHR4 restart event (soft). Reason: undefined
Apr 11 13:08:40 2020 local0.debug<135> System: BHR4 restart event (soft). Reason: undefined
Apr 11 13:07:10 2020 local1.info<142> System: Performing software shutdown. Reason undefined. Running firmware 02.02.00.16 (02.02.00.16_20190528_022627_9fe6379f_jenkins)
Apr 11 13:07:09 2020 local1.info<142> cwmpclient[2026]: Reboot requested by ACS

To close the loop on this, I ended up moving my G3100 router to a more central location in my home (vs adding E3200 extender) and now the areas of my home that had a weak signal are good.  It was certainly a pain to relocate the ethernet and coax that connect from the ONT to the router but me and my 15' fishing tool got it done!

To close this thread, I ended up moving my G3100 router to a more central location in my home (vs adding E3100 extender) and now those areas of my home where the wifi signal was weak are good. It was certainly a pain to relocate the ethernet and coax that attach to the G3100 from the ONT, but me and my 15' fishing tool got it done!

---

 wrote:

I've seen this suggestion of visiting dslreports.com. Is this site run by Verizon?

---

It is not run by Verizon.

---

 wrote:

TBH, it seems weird that Verizon tech would monitor a 3rd party site more than their own forums that they pay to keep up for compute and storage.

---

That 3rd party site got started before Verizon's official forums and I have no idea of how much they monitor 3rd party site(s) vs their own.

While this is their own forum, please keep in mind this is mainly a another peer to peer forum.

Also at that other forum (DSLR) there is an ISP direct area (like Verizon Direct).

In plain straight english: You will be talking directly to Verizon Tech over there and post in that area private info.

By that, this info: Private info that is allowed to post in a direct area include but is not limited to: Full Phone Number, Account Number, Full real name of account owner and as need be your full real name if not the account owner.

Been having various problems with my internet connectivity. One thing I noticed is continual error message in my System Log. Prior to this, the log would show INFORMATION messages every hour. Now it is showing named DNS errors non-stop.

Apr 10 09:04:21 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:04:21 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:04:21 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:04:16 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:04:16 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:02:55 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:02:55 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:02:55 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:02:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:02:50 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:01:35 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:01:35 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:01:35 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone localrp/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone fios-router.home/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone Fios_Quantum_Gateway/IN/internal-clients: zone serial (2008122601) unchanged. zone may fail to transfer to slaves.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 09:01:30 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 09:01:30 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 08:59:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: not loaded due to errors.
Apr 10 08:59:50 2020 local1.err<139> named[1970]: zone 1.168.192.in-addr.arpa/IN/internal-clients: loading from master file localrev.zone failed: extra input text
Apr 10 08:59:50 2020 local1.err<139> named[1970]: dns_rdata_fromtext: localrev.zone:12: near 'Roku': extra input text
Apr 10 08:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 07:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 06:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 05:06:06 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 04:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 03:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 02:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 01:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 10 00:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 23:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 22:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 21:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 20:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 19:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 18:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 17:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 16:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 15:06:05 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 14:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 13:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 12:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds
Apr 9 11:06:04 2020 local0.info<134> dhcpcd[1733]: eth1: IPv4 renew in 3600 seconds, rebind in 6300 seconds, expire in 7200 seconds

Starting on April 11, 2020, my G1100 router has been logging continual error messages about lighttpd. Does anyone know how to check if a recent update has been pushed to the router? I have been seeing various issues in the past couple of days. Below is a snippet from my AdvancedLog.

Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:04:07 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:54 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:54 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:49 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:03:10 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:02:54 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:02:37 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:02:26 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:44 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:41 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:01:30 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:48 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 13:00:45 2020 user.err<11> lighttpd[1483]: (connections.c.1746) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
Apr 11 12:43:35 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587213815, active: 1
Apr 11 10:56:14 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 3658, external host , internal port 3658, internal host 192.168.1.172, timestamp: 1587207374, active: 1
Apr 11 09:02:28 2020 local7.info<190> miniupnpd[1741]: Removing port mapping protocol UDP, external port 3658, external host , internal port 3658, internal host 192.168.1.172
Apr 11 09:02:14 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 3658, external host , internal port 3658, internal host 192.168.1.172, timestamp: 1587200534, active: 1
Apr 11 04:16:17 2020 local7.info<190> miniupnpd[1741]: Removing port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157
Apr 11 04:15:50 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587183350, active: 1
Apr 11 03:53:52 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587182032, active: 1
Apr 11 02:31:44 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587177104, active: 1
Apr 11 01:31:44 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587173504, active: 1
Apr 11 00:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587169899, active: 1
Apr 10 23:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587166299, active: 1
Apr 10 22:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587162699, active: 1
Apr 10 21:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587159099, active: 1
Apr 10 20:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587155499, active: 1
Apr 10 19:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587151899, active: 1
Apr 10 18:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587148299, active: 1
Apr 10 17:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587144699, active: 1
Apr 10 16:31:39 2020 local7.info<190> miniupnpd[1741]: Adding port mapping protocol UDP, external port 5353, external host , internal port 5353, internal host 192.168.1.157, timestamp: 1587141099, active: 1

Verizon Fios placed an account that I canceled within 30days money-back period.  I ordered internet-only (self-installed) with no contact on about March 2018, I cancel the same day because I could not get it to work.  They sent out a tech w/o my request since I cancel.  When I started to receive billing notices, I contacted them several times to remind them that I cancel.  Over the phone and via there chat support app, they assured me that it was resolved to give a month to update.  I moved, and for a while did not hear anything.  Now, I am looking at my credit report to prepare to buy a house in the future and notice that they have a collection against me in my credit report.  I did some research online and found that a lot of former customers have similar or same issues with Verizon Fios.

I plan to call today to try and resolve, but if they don't help, what can I do?  The collection charge is $99.

Hi Bronzerock,

As this is a peer to peer support forum, you will need to contact Verizon directly for assistance. We have sent you a private message with contact information for a dedicated specialist who is able to help with a resolution of your issue.

I have a fios router with wifi disabled on both 2.4 and 5g.  That unit is in the basement.  From there I have a hardwired connection to my google router on the main floor.  I also have a point upstairs in 1 bedroom.  Everything works fine but throughout the day and especially from the bedroom farthest from the point, i keep losing the wifi signal, any internet app just spins on my phone.  Its incredibly frustrating.  The bedroom I work out of is only about 50 feet from the point in the upstairs bedroom.  How can the connection be so unstable?  I've tried doing speed tests, the ones that complete say it is lightning fast.  And the other times I get the can't connect to internet.  

I guess my question is do I need to do anything else to the FIOS router?  I've heard things like setup a bridge, use as an access point.  Please help.  I'm so **bleep** off after spending money for this.  Can't return it as its past the deadline for a return.  My old router worked actually worked better.

As the other poster explained, http://www.dslreports.com is not a verizon mirror site but independent of verizon. They have verizon direct to get quick response to folks that cannot seem to get assists elsewhere.

verizon direct is real verizon social media personnel. Many folks will state that for some reason the verizon direct people over there actually know what they are doing and accomplish much. Some folks say go to twitter which I have found is not much help at all basically lip service. Go to twitter and judge for yourself.

the other benefit of using dsl reports is you can give advice and comments without it being considered offensive here on the official forum. 

when on the few occasions I had to call verizon support at 1-800-VERIZON I had a quick resolution (this was five years ago) and the young lady was great and I have not had any issues with my gigabyte internet only service. Fios when it functions as it should is an outstanding product. Support today well it’s not that great and verizon has some issues.

This site may be of assistance 

https://www.reddit.com/r/GoogleWiFi/comments/8p2k7a/best_setup_for_verizon_fios_quantum_gateway/

it should give you options. Please note there are two google mesh devices. One is from google with no verizon fios alterations or additions, and of course the other is verizon branded and has been purported to have a myriad of issues. Hopefully the above link will assist you.