My MS DNS servers won't resolve .biz records

I am running DNS internally on Windows 2008 (Enterprise Server) SP2.  It resolves .com, .net - but *not* .biz records.  Anyone know why this would be?  How to fix?  Thanks!
LVL 2
amigan_99Network EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jian An LimSolutions ArchitectCommented:
well,
can you do a nslookup on this *.biz domain?
confirm you have root forwarder in dns, or else set root forwarder to 8.8.8.8


http://support.microsoft.com/kb/2001154
0
bbaoIT ConsultantCommented:
ever tried using different DNS servers? such as Google's public DNS servers 8.8.8.8 and 4.4.4.4??
0
pwindellCommented:
My MS DNS servers won't resolve .biz records


"Yours" is not supposed to.  Your forwarder does.  Others have already asked about your Forwarders,...but I didn't feel anyone made it clear that your own DNS is not the one that is supposed to resolve that,...it is only supposed to resolve names on your own internal LAN.  I didn't want to take it for granted that you already knew that.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

amigan_99Network EngineerAuthor Commented:
Thanks for the replies.  I have no conditional forwarders for .com or .net yet through recursion any host in those TLDs will resolve fine.  MS DNS just seems to figure it out.  But if I run nslookup, server <internal MS DNS>, the result is not known for anything in the .biz.  I suppose I could put in a conditional forwarder for .biz TLD and point that to goog's 8.8.8.8 and just be done with it.  But I want to understand why the .com and .net work fine but .biz does not.

On a related note is there a way to look at logging on the DNS server and where you could actually see the recursive process?  I supposed I could throw wire shark on there and see the traffic that way.  But any native logging I could crank up and view?  
0
amigan_99Network EngineerAuthor Commented:
limjianan: Thanks for that tech note "Unchecking the checkbox for “use root hints if no forwarders are available” in the Windows Server 2008 DNS Manager snap-in, DNSMGMT.MSC, actually enables the use of root hints." I will look at this later this morning!
0
pwindellCommented:
There is no need at all for "conditional" forwarders.

You either use regular normal forwarders,...or you don't.

If you use a forwarder it will resolve any domain of any kind what-so-ever when there is no zone in your own DNS for that particular domain.

If you do not use any forwarders (which is acceptable) then your DNS will automatically default to use Root Hints,...meaning it will use the Root Servers as forwarders.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pwindellCommented:
It is normal for that root hints check box to stay checked.  It is normal, expected, and proper, to default to using Root Hints if you don't configure your DNS with a Forwarder.   If you use a Forwarder the checkbox becomes irrelevant since it will not use Root Hints if a Forwarder is present.
0
amigan_99Network EngineerAuthor Commented:
I was just being blind not seeing the forwarder record config (although I could see the conditional forwarders.)  I added in goog DNS as general forwarders and now everything is resolving.  Not sure why .com and .net worked fine with just the root hints but not the .net.  But at least we're workin'.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.