I don't believe this and I/we have some serious problems.
When the system boots, the time is jan 1 1970. The first thing you want to run is ntp to set the time, but requires named running and resolving. But it is not resolving the ntp addr.
For the 'fun' of it, I used 'date' to set the time to now, and then no problem resolving 0.centos.pool.ntp.org. So there is something about that resolution that does not like the early date.
So I am caught in a time bind here!
More on this in a separate message.
On 09/01/2015 09:14 AM, Robert Moskowitz wrote:
My new test nameserver on the C7-arm code cannot resolve:
0.centos.pool.ntp.org
but has not trouble resolving:
www.ietf.org
My old nameserver on the C6 bind 9.8.2 resolves both with no problems. Both servers have identical conf and zone files (with the necessary SOA changes on the new server).
Either:
problems with the bind pre-alpha code
things have changed between 9.8 and 9.9 such that things are breaking (I have disabled dnssec, for example).
Ideas?
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev