[c-nsp] OT: NTP windows servers

Chuck Church chuckchurch at gmail.com
Thu Mar 26 14:10:12 EDT 2015


I guess I assumed windows using DNS correctly was wrong.  There is a way to flush dns (I think it’s ipconfig /flushdns) but it really shouldn’t be necessary.

 

Chuck

 

From: Scott Voll [mailto:svoll.voip at gmail.com] 
Sent: Thursday, March 26, 2015 11:33 AM
To: Chuck Church
Cc: Eric Louie; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] OT: NTP windows servers

 

TTL is 1 hour......... this lasted over 2 weeks before we changed from FQDN to IP.  which corrected the problem.

 

On Thu, Mar 26, 2015 at 8:20 AM, Chuck Church <chuckchurch at gmail.com <mailto:chuckchurch at gmail.com> > wrote:

What was the TTL of the DNS entry?  I'm assuming windows DNS respects TTLs
and re-polls when it expires?

Chuck

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net <mailto:cisco-nsp-bounces at puck.nether.net> ] On Behalf Of
Scott Voll

Sent: Thursday, March 26, 2015 10:44 AM
To: Eric Louie
Cc: cisco-nsp at puck.nether.net <mailto:cisco-nsp at puck.nether.net> 
Subject: Re: [c-nsp] OT: NTP windows servers

we ended up changing the NTP FQDN to the IP and restarted services and it
fixed it.  It's like the FQDN only gets resolved once and never again.  So
after changing it to the IP I'm guessing I could change back to the FQDN.
 we were just hoping that changing the DNS was going to fix it.

Scott

On Wed, Mar 25, 2015 at 4:50 PM, Eric Louie <elouie at techintegrity.com <mailto:elouie at techintegrity.com> >
wrote:

> restarting the NTP service might fix the problem, although if I'm
> reading this right, you restarted the Windows Servers after changing the
NTP source.
>
> I'm assuming that you changed the C:\Program Files
> (x86)\NTP\etc\ntp.conf file to use the new address AND removed the old
> one.  Directions from there are to stop and start the NTP service.
>
>
>
> On Mon, Mar 16, 2015 at 12:54 PM, Scott Voll <svoll.voip at gmail.com <mailto:svoll.voip at gmail.com> > wrote:
>
>> I am migrating NTP from one router to another (and changing IP
addresses).
>>
>> All our servers were pointing to the old router for NTP.
>>
>> I have changed the NTP source on those servers to the new one.
>> restarted and if I log an ACL for NTP, I'm still seeing the servers
>> connect to the old router.  Any ideas on how to fix that?  I'm not a
windows server guy.
>>
>> TIA
>>
>> Scott
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net <mailto:cisco-nsp at puck.nether.net> 
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>
>
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net <mailto:cisco-nsp at puck.nether.net> 
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

 



More information about the cisco-nsp mailing list