Port 53 - All Comments

re: DNSSEC in Windows 7

James — Fri, 27 Jan 2012 00:50:58 GMT

Is there any way to add a trust anchor to allow security-aware queries against the signed root zone?

re: Hello hello!

Oliver — Wed, 29 Jun 2011 10:56:46 GMT

I guess his work did not last for long

re: DNSSEC on Windows 7 DNS client

Chris — Thu, 15 Apr 2010 12:31:29 GMT

Alex C - RFC 4033 obseletes 3655.

re: DNSSEC on Windows 7 DNS client

Alex C — Mon, 18 Jan 2010 20:00:28 GMT

I'm not a microsoft fan boy, but do a little research. http://www.rfc-archive.org/getrfc.php?rfc=3655

re: DNSSEC on Windows 7 DNS client

Jay Momo — Mon, 09 Nov 2009 04:30:23 GMT

Looks like Microsoft wants to choke out GNU/Linux and Apple OSX systems from the network. There is not a chance that AD bit thing is standardized or publicly documented in any way. So, only Microsoft-authorized clients can use your Microsoft DNS/DHCP server, thus preventing any users from using any sort of non-Microsoft clients. Awesome.

re: Hello hello!

Larry — Thu, 05 Nov 2009 14:23:02 GMT

I use SBS 2008, --> Best Practices Analzer:

It reports an error:

The DNS Server service should listen on DNS port 53, but that port is owned by the process.

-------------------

I can't find any infommation on this error message. This is reporting back to the SBS console as an exception, and I see the read flag every time I sign on. How do I correct this ?

thx

re: DNSSEC in Windows 7

anonymous — Sun, 26 Jul 2009 22:23:57 GMT

Is it possible to set "allow-recursion" ACL like BIND to disallow recursive queries on source IPs that don't match the ACL?

re: Windows DNS and the Kaminsky bug

GW@DellCSS — Fri, 19 Jun 2009 21:18:11 GMT

what collection of commands do we have, analogous to DNSCMD /config /socketpoolsize <value>, that will work on our few, but dogged Win2000server customers? DNSCMD /config is an unknown command, and we have to do something about the ~5700 handle count being sucked away from user mem. It has become a significant call driver for us whenever we see server freezes... and reducing socket pool size by 1/2 cuts the expended handles in 1/2 as well, resulting in resolution.

re: Windows DNS and the Kaminsky bug

cheap propecia — Thu, 28 May 2009 09:36:53 GMT

If you have to do it, you might as well do it right

re: Windows DNS and the Kaminsky bug

John — Wed, 22 Apr 2009 09:50:50 GMT

Thanks! This is exactly what I was looking for, too bad MS didn't explain/post this as well...