Quantcast
Channel: Directory Services Forum
Viewing all articles
Browse latest Browse all 2536

Found a bug in Server 2008 R2 DNS. it will NOT resolve a valid entry that all other DNS implementations do ust fine.

$
0
0

I have tested this against multiple DNS servers.  2008, 2003, 2000, several versions of Bind, fastpipe, etc.  They all work for this one particular domain until you query against a 2008 R2 Domain.

Attempt to resolve www.superfisheye.com on a 2008 R2 DNS server and we get back no value.  All other DNS systems work fine.

Here is how they have it setup.

www.superfisheye.com is a cname to superfisheye.com which is a cname to shopping.netsuite.com and this currently has an A record pointing to 167.216.129.13.

I've checked it against out 2008 R2 DNS that has our AD on it, I've also built two clean new installs of DNS and only updated the root hints to the latest.  It still fails.

I'd love to get a few others also to verify that it fails for them.

Thanks.


Viewing all articles
Browse latest Browse all 2536

Trending Articles