RE: Overriding a single record with dynamic-dns

Thanks for your answers ...  I am currently dumping the dynamic zone regularly ( dig axfr ) ,  rewriting the different records i need and making it a static master zone on a specific server. I guess if i have to upgrade the current implementation ( is that proper english  ? ) i will be using a s

frequent queries to root servers

Hi All, I assumed that the root servers are only queried a few times a week (corresponding to the number of top level domains). The logs show a different picture, Queries to the root servers are quite frequent. What am I missing? I have attached a dnstop screen (local network traffic was fil

RE: frequent queries to root servers

Well, when I queried the name livetileedge.dsx.mp.microsoft.com, I got a CNAME chain where all of the links in the chain had TTLs of 300 seconds or less: livetileedge.dsx.mp.microsoft.com. 43 IN CNAME livetileedge.dsx.mp.microsoft.com.akadns.net. livetileedge.dsx.mp.microsoft.com.akadns.net. 30

Re: frequent queries to root servers

Am 27.01.2016 um 00:36 schrieb Darcy Kevin (FCA): Well, when I queried the name livetileedge.dsx.mp.microsoft.com, I got a CNAME chain where all of the links in the chain had TTLs of 300 seconds or less: livetileedge.dsx.mp.microsoft.com. 43 IN CNAME livetileedge.dsx.mp.microsoft.com.akadns

Re: frequent queries to root servers

Am 27.01.2016 um 00:46 schrieb Reindl Harald: Am 27.01.2016 um 00:36 schrieb Darcy Kevin (FCA): Well, when I queried the name livetileedge.dsx.mp.microsoft.com, I got a CNAME chain where all of the links in the chain had TTLs of 300 seconds or less: livetileedge.dsx.mp.microsoft.com. 43 IN CN

Re: frequent queries to root servers

HONTVÁRI Levente wrote: > I assumed that the root servers are only queried a few times a week > (corresponding to the number of top level domains). The logs show a > different picture, Queries to the root servers are quite frequent. What am I > missing? > > I have attached a dnstop screen (local n

Name resolution failure on a caching server -- many '; pending-answer' records in the cache

Dear All, I run a caching server on a section of the departmental LAN. Occasionally network congestion results in timeouts & name resolution failures. Lookups performed on name servers outside my LAN section fail with NXDOMAIN. Querying my name server for items not in its cache gets the same