Date: Tue, 2 May 2023 14:07:47 -0400 From: Paul Procacci <pprocacci@gmail.com> To: Doug Denault <doug@safeport.com> Cc: questions@freebsd.org Subject: Re: ntpd error on a bridged network Message-ID: <CAFbbPujQRGJ_k1N8uxW5LMYyWb9od1O8M=WgaWCW3C1O2qervA@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.2305021300400.29936@bucksport.safeport.com> References: <alpine.BSF.2.00.2305021300400.29936@bucksport.safeport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000c171a005fab9d1a7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, May 2, 2023 at 1:02=E2=80=AFPM Doug Denault <doug@safeport.com> wro= te: > We replaced an old apple router with a Linksys Velop router. The apple > router was behind a Verizon router and we used DHCP from Verizon on the > apple device. To duplicate the setup we configured the Linksys in bridge > mode. > > ntpd starts with the error: > ntpd: error resolving pool 0.freebsd.pool.ntp.org: Name does not > resolve (8) > > however: > > host -t a 0.freebsd.pool.ntp.org > 0.freebsd.pool.ntp.org has address 174.53.169.69 > 0.freebsd.pool.ntp.org has address 192.241.155.186 > 0.freebsd.pool.ntp.org has address 38.229.53.9 > 0.freebsd.pool.ntp.org has address 38.229.57.9 > > ping -c 2 0.freebsd.pool.ntp.org > PING 0.freebsd.pool.ntp.org (94.237.120.208): 56 data bytes > 64 bytes from 94.237.120.208: icmp_seq=3D0 ttl=3D53 time=3D78.773 ms > 64 bytes from 94.237.120.208: icmp_seq=3D1 ttl=3D53 time=3D79.012 ms > > /etc/resolv.conf > # Generated by resolvconf > search boltsys.com > nameserver 192.168.2.1 > > Other than ntpd I see no DNS or connectivity issues. So far the time has > been holding at 2 seconds difference > from the servers not on the office LAN. > > > _____ > Douglas Denault > http://www.safeport.com > doug@safeport.com > Voice: 301-217-9220 > Fax: 301-217-9277 > > When you restart ntpd after the system has fully booted, does the same error occur? Just trying to isolate if it's a problem with ntpd specifically or perhaps ntpd starting before the network becomes available. What version of FreeBSD are you running? ~Paul --=20 __________________ :(){ :|:& };: --000000000000c171a005fab9d1a7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div><div dir=3D"ltr"><br></div><br><div class=3D"gma= il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, May 2, 2023 at 1:02= =E2=80=AFPM Doug Denault <<a href=3D"mailto:doug@safeport.com" target=3D= "_blank">doug@safeport.com</a>> wrote:<br></div><blockquote class=3D"gma= il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2= 04,204);padding-left:1ex">We replaced an old apple router with a Linksys Ve= lop router. The apple <br> router was behind a Verizon router and we used DHCP from Verizon on the <br= > apple device. To duplicate the setup we configured the Linksys in bridge <b= r> mode.<br> <br> ntpd starts with the error:<br> =C2=A0 =C2=A0 ntpd: error resolving pool <a href=3D"http://0.freebsd.pool.n= tp.org" rel=3D"noreferrer" target=3D"_blank">0.freebsd.pool.ntp.org</a>: Na= me does not resolve (8)<br> <br> however:<br> <br> =C2=A0 =C2=A0 host -t a <a href=3D"http://0.freebsd.pool.ntp.org" rel=3D"no= referrer" target=3D"_blank">0.freebsd.pool.ntp.org</a><br> =C2=A0 =C2=A0 <a href=3D"http://0.freebsd.pool.ntp.org" rel=3D"noreferrer" = target=3D"_blank">0.freebsd.pool.ntp.org</a> has address 174.53.169.69<br> =C2=A0 =C2=A0 <a href=3D"http://0.freebsd.pool.ntp.org" rel=3D"noreferrer" = target=3D"_blank">0.freebsd.pool.ntp.org</a> has address 192.241.155.186<br= > =C2=A0 =C2=A0 <a href=3D"http://0.freebsd.pool.ntp.org" rel=3D"noreferrer" = target=3D"_blank">0.freebsd.pool.ntp.org</a> has address 38.229.53.9<br> =C2=A0 =C2=A0 <a href=3D"http://0.freebsd.pool.ntp.org" rel=3D"noreferrer" = target=3D"_blank">0.freebsd.pool.ntp.org</a> has address 38.229.57.9<br> <br> =C2=A0 =C2=A0 ping -c 2 <a href=3D"http://0.freebsd.pool.ntp.org" rel=3D"no= referrer" target=3D"_blank">0.freebsd.pool.ntp.org</a><br> =C2=A0 =C2=A0 PING <a href=3D"http://0.freebsd.pool.ntp.org" rel=3D"norefer= rer" target=3D"_blank">0.freebsd.pool.ntp.org</a> (94.237.120.208): 56 data= bytes<br> =C2=A0 =C2=A0 64 bytes from <a href=3D"http://94.237.120.208" rel=3D"norefe= rrer" target=3D"_blank">94.237.120.208</a>: icmp_seq=3D0 ttl=3D53 time=3D78= .773 ms<br> =C2=A0 =C2=A0 64 bytes from <a href=3D"http://94.237.120.208" rel=3D"norefe= rrer" target=3D"_blank">94.237.120.208</a>: icmp_seq=3D1 ttl=3D53 time=3D79= .012 ms<br> <br> =C2=A0 =C2=A0 /etc/resolv.conf<br> =C2=A0 =C2=A0 # Generated by resolvconf<br> =C2=A0 =C2=A0 search <a href=3D"http://boltsys.com" rel=3D"noreferrer" targ= et=3D"_blank">boltsys.com</a><br> =C2=A0 =C2=A0 nameserver 192.168.2.1<br> <br> Other than ntpd I see no DNS or connectivity issues. So far the time has <b= r> been holding at 2 seconds difference<br> from the servers not on the office LAN.<br> <br> <br> _____<br> Douglas Denault<br> <a href=3D"http://www.safeport.com" rel=3D"noreferrer" target=3D"_blank">ht= tp://www.safeport.com</a><br> <a href=3D"mailto:doug@safeport.com" target=3D"_blank">doug@safeport.com</a= ><br> Voice: 301-217-9220<br> =C2=A0 =C2=A0Fax: 301-217-9277<br> <br> </blockquote></div><br>When you restart ntpd after the system has fully boo= ted, does the same error occur?<br><br></div><div>Just trying to isolate if= it's a problem with ntpd specifically or perhaps ntpd starting before = the network becomes available.<br><br></div><div>What version of FreeBSD ar= e you running?<br><br></div><div>~Paul<br><br></div></div><div><div><span>-= - </span><br><div dir=3D"ltr">__________________<br><br>:(){ :|:& };:</= div></div></div></div> --000000000000c171a005fab9d1a7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFbbPujQRGJ_k1N8uxW5LMYyWb9od1O8M=WgaWCW3C1O2qervA>