What is the best practice for DNS on Server 2008

I have setup and installed two new servers and used one of the old servers. The new servers are both running Windows Server 2008. When I was on the phone with Microsoft I asked their advice on how I should run the DNS because both servers were taking forever to reboot (slow reboots usually mean DNS issue). They suggested to run the main server's local adapter DNS as 127.0.0.1 with no forwarders in the DNS server. Then they said to run the main servers IP # for the local adapter DNS for the other two servers. Doing this did not help or speed up things. I have attached a sheet of my network and all the settings and would like advice on what would be the best way to set the DNS both in the local adapter and the DNS server so my servers run faster. I run profiles so when the client logs off or reboot it takes forever!!! It is also taking about 6 hours for mail. Before we were getting the mail in less than 10 minutes. I know that the slow reboots and the 6 hours or more for mail are related to the DNS settings. I need to know what would be the best way to configure the DNS settings in the local adapters on all three servers and in the DNS Server settings on the two servers. I am not real up on DNS so all input would be greatly appreciated and please explain in detail so I understand what you are saying. If you could just change the settings on the attachment with the way that I should configure all DNS and send back to me that would be wonderful!
Domain-Settings.docx
LANengineerAsked:
Who is Participating?
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.

gmbaxterCommented:
On server 2 have you configured it as a DNS replica, or have you just manually created the records the same.

How much memory do you have in the servers? slow reboots and loading could be down to a low amount of ram.
0
DrDave242Commented:
Your DNS setup looks OK to me.  Server 1 is the only DC, right?  Is there a firewall running on Server 1?  If so, either disable it or make sure it allows DNS traffic through.  Also, at what point during the boot process do the servers seem to hang?
0
Chris DentPowerShell DeveloperCommented:

> It is also taking about 6 hours for mail

Inbound?

That's unlikely to be anything to do with internal DNS unless you're running a public DNS service there as well?

> I need to know what would be the best way to configure the DNS settings in
> the local adapters on all three servers and in the DNS Server settings on the two servers

I agree with DrDave242, your settings are fine.

Where in the reboot / startup process is it hanging?

Chris
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

LANengineerAuthor Commented:
gmbaxter:
These servers are both new with 8Gb of memory. The slowness has nothing to do with hardware. I did not manually put the DNS in the server two it just replicated.
0
LANengineerAuthor Commented:
DrDave:
Both server #1 and #2 are domain controllers. I have the windows firewall turned off on both servers. The servers are slow booting up once it hits the GUI / splash screen. The client workstations take forever to save settings and then to apply settings.
0
LANengineerAuthor Commented:
Chris:
It is taking forever on incoming and outgoing mail. The clients are saying that they are not always getting what people are sending them either.
0
LANengineerAuthor Commented:
When I setup the DHCP role it did not ask me about DNS. Should DNS be configured anywhere in the DHCP server?? When I do an ipconfig/all on the clients it shows the following DNS numbers:
127.0.0.1
192.168.0.10
192.168.0.8
0
Chris DentPowerShell DeveloperCommented:

127.0.0.1 is on clients?

You need to bump that one off the list, it's localhost, and clients themselves are rather unlikely to be running a DNS service.

Inbound mail should not be effected by your internal DNS in any way at all. Indeed it's a little concerning that it takes so long. Have you checked, with Message Tracking, for any delay between it being received on the mail system and being delivered to the mailbox?

> The clients are saying that they are not always getting what people are
> sending them either.

There are, of course, things that need to be checked here. None to do with internal DNS, and none which will effect logon times.

For outbound mail delivery to be reliable you need three things (this assumes you are not using a Smart Host / Relay):

1. A valid public server name. Exchange 2007? Check the FQDN value set on the Send Connector
2. A valid Host (A) record in your public DNS system mapping that name to the public IP address you use
3. A Domain Pointer (PTR) record in your public DNS (or more likely, in your ISPs public DNS) that maps the public IP address back to the name

If any of those three are missing you may have difficulty delivering mail.

For everything else...

Can you show us DCDiag, and give details of any errors / warnings logged in the Event Log on both your servers and your clients? Obviously something is wrong, but I don't feel it's clear what.

Chris
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
DrDave242Commented:
Since servers 1 and 2 are both DCs and DNS servers in the same site, each one should use the other as its preferred DNS server and itself as alternate.  (There's some debate on this, depending on whom you talk to, but this configuration has always given me good results.  It ensures that each DC will be able to contact a functional DNS server right away in the event of a reboot, as long as they're not both rebooted at the same time.)  Server 3 should point to both of them for redundancy, but the order is not really important.

As Chris said, 127.0.0.1 should definitely be removed from the DNS server list on the clients.  You can configure that within Scope Options (and/or possibly Server Options) in the DHCP console on server 1.
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
DNS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.