Re: Solved - Re: A tale of two nameservers - resolution problems

2015-09-03 Thread Robert Moskowitz
On 09/03/2015 04:09 AM, Matus UHLAR - fantomas wrote: On 01.09.15 13:36, Robert Moskowitz wrote: On the Fedora-arm list I was told about systemd-timesyncd. Much better for these systems than chronyd which is suppose to be the replacement for ntpdate... chrony is replacement for ntpd (not n

Re: Solved - Re: A tale of two nameservers - resolution problems

2015-09-03 Thread Matus UHLAR - fantomas
On 01.09.15 13:36, Robert Moskowitz wrote: On the Fedora-arm list I was told about systemd-timesyncd. Much better for these systems than chronyd which is suppose to be the replacement for ntpdate... chrony is replacement for ntpd (not ntpdate!) on systems that are not always online. "has b

Final on - Re: A tale of two nameservers - resolution problems

2015-09-02 Thread Robert Moskowitz
I have learned a bit in the past time period. First, adding a 2nd DNS server, in this case my ISP's, got around this timing problem, becuase the 'right fix' is not available yet. The answer is to stop using old ntpd and use modern chronyd. But more than that, ver 2.1.1 which is available in

Solved - Re: A tale of two nameservers - resolution problems

2015-09-01 Thread Robert Moskowitz
On 09/01/2015 12:16 PM, Sam Wilson wrote: In article , Robert Moskowitz wrote: I will be looking more into this. Obvious when you get ones nose dragged into time wrong on boot. This is actually a broader problem on arm SoC booting. Your logs all have the wrong time for the boot messages

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread Sam Wilson
In article , Robert Moskowitz wrote: > I will be looking more into this. Obvious when you get ones nose > dragged into time wrong on boot. This is actually a broader problem on > arm SoC booting. Your logs all have the wrong time for the boot > messages until there is a network to get time

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread Sten Carlsen
On 01/09/15 17:46, Robert Moskowitz wrote: > > There will be a lot of arm IoT boxes in the next few years needing > their time on boot. Of course booting will not be that frequent, but > it will interesting to see how it plays out. And check devices like > the esp8266, as $6 IoT device. It al

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread Robert Moskowitz
On 09/01/2015 10:38 AM, Reindl Harald wrote: Am 01.09.2015 um 16:28 schrieb John Miller: On Tue, Sep 1, 2015 at 9:31 AM, Robert Moskowitz wrote: On 09/01/2015 09:20 AM, John Miller wrote: If you check pcap, logs, etc., is the server's following delegation for 0.centos.pool.ntp.org? Where

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread Robert Moskowitz
On 09/01/2015 10:28 AM, John Miller wrote: On Tue, Sep 1, 2015 at 9:31 AM, Robert Moskowitz wrote: On 09/01/2015 09:20 AM, John Miller wrote: If you check pcap, logs, etc., is the server's following delegation for 0.centos.pool.ntp.org? Where do outbound packets stop? I don't believe this

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread Robert Moskowitz
On 09/01/2015 09:36 AM, Reindl Harald wrote: Am 01.09.2015 um 15:31 schrieb Robert Moskowitz: On 09/01/2015 09:20 AM, John Miller wrote: If you check pcap, logs, etc., is the server's following delegation for 0.centos.pool.ntp.org? Where do outbound packets stop? I don't believe this and

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread Bob Harold
On Tue, Sep 1, 2015 at 10:38 AM, Reindl Harald wrote: > > Am 01.09.2015 um 16:28 schrieb John Miller: > >> On Tue, Sep 1, 2015 at 9:31 AM, Robert Moskowitz >> wrote: >> >>> >>> On 09/01/2015 09:20 AM, John Miller wrote: >>> If you check pcap, logs, etc., is the server's following deleg

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread Reindl Harald
Am 01.09.2015 um 16:28 schrieb John Miller: On Tue, Sep 1, 2015 at 9:31 AM, Robert Moskowitz wrote: On 09/01/2015 09:20 AM, John Miller wrote: If you check pcap, logs, etc., is the server's following delegation for 0.centos.pool.ntp.org? Where do outbound packets stop? I don't believe th

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread John Miller
On Tue, Sep 1, 2015 at 9:31 AM, Robert Moskowitz wrote: > > > On 09/01/2015 09:20 AM, John Miller wrote: >> >> If you check pcap, logs, etc., is the server's following delegation >> for 0.centos.pool.ntp.org? Where do outbound packets stop? > > > I don't believe this and I have some serious proble

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread Reindl Harald
Am 01.09.2015 um 15:31 schrieb Robert Moskowitz: On 09/01/2015 09:20 AM, John Miller wrote: If you check pcap, logs, etc., is the server's following delegation for 0.centos.pool.ntp.org? Where do outbound packets stop? I don't believe this and I have some serious problems. Part of my challe

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread Robert Moskowitz
On 09/01/2015 09:20 AM, John Miller wrote: If you check pcap, logs, etc., is the server's following delegation for 0.centos.pool.ntp.org? Where do outbound packets stop? I don't believe this and I have some serious problems. Part of my challenge is I am running the new server on an armv7 boa

Re: A tale of two nameservers - resolution problems

2015-09-01 Thread John Miller
If you check pcap, logs, etc., is the server's following delegation for 0.centos.pool.ntp.org? Where do outbound packets stop? John On Tue, Sep 1, 2015 at 9:09 AM, Robert Moskowitz wrote: > I have one nameserver running bind 9.8.2 and a new one running 9.9.4. > > Both can resolve www.ietf.org >

A tale of two nameservers - resolution problems

2015-09-01 Thread Robert Moskowitz
I have one nameserver running bind 9.8.2 and a new one running 9.9.4. Both can resolve www.ietf.org Only the 9.8.2 can resolve 0.centos.pool.ntp.org I literally rsynced all the of the conf and zone files from the old to the new, then changed all of the server name references. I have done thi