Effect of having a DNS suffix in the domain/workgroup settings?

I have no idea if this is causing any issues or not, but one of our 10 SQL servers is having performance issues. There are many things I can look for in perfmon, but one thing that stood out immediately is this.

All of our SQL servers are in the same workgroup. There is no domain or Windows DNS servers for various reasons. One the one that's poorly performing, if you go to the workgroup name settin and click the More... button there is a DNS suffix listed in the text box unlike the rest which having nothing in there.

My first question is "what is the effect of having something in or not in this field and could that possibly affect our experience/performance?"

My second question is:

"What is the difference between this setting here and the NIC properties settings which say either (A) "Append primary and connection specific DNS suffixes [append parent suffixes of the primary DNS suffix], or (B) Append these DNS suffixes (in order)"?

My last question is:

MrVaultAsked:
Who is Participating?
 
Darius GhassemConnect With a Mentor Commented:
One the append option appends the domain at the end of a DNS query

Another searches the list of domain names listed
0
 
Darius GhassemCommented:
If you aren't using DNS  then I would consider using host files to point the clients directly to the server's IP addresses which would speed the response time since currently you are just doing a broadcast to find the IP address of  the server.

http://technet.microsoft.com/en-us/library/cc778792(WS.10).aspx
0
 
MrVaultAuthor Commented:
Our servers don't talk to each other. Only the clients/customers point to our servers.

For the dns suffix in the computer name properties, what effect does it have by putting something there? I realize the NIC settings give it additional dns suffixes to use when searching by computer name (so it could search "pc1.mydomain.com" or pc1.myotherdomain.com.

But in workgroup environment, what benefit or hindrance could it be causing by appending "mydomain.com" on the end of the PC name?
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
Darius GhassemCommented:
Now really a benefit if not domain or internal DNS servers are being used.
0
 
MrVaultAuthor Commented:
thanks. I removed the setting but we can't reboot until early next week. so I'll report back then to see if it's fixed anything.
0
 
MrVaultAuthor Commented:
still waiting for an approved reboot. will update then.
0
 
MrVaultAuthor Commented:
The errors have gone away and it looks like we're still fine with the change in place. thanks everyone!
0
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.

All Courses

From novice to tech pro — start learning today.