Dns

[Pantlegz]

So, finally upgraded the network at work and everything is working good aside from anyone on the new portion(IP scheme) of the network is having strange dns issues. it's serving up addresses for them but 'shortcuts' that were put into the dns aren't working for them for instance: sharepoint wont resolve but sharepoint.FQDN will resolve and it's like this for everything. How does one go about fixing something like this? Sorry for the stupid help me do my job question but I'm lost...

 

[spidey07]

Tagged until I get to a puter.

 

[RebateMonger]

It'd likely help to add a DNS Suffix to the Scope Options (Option 15, DNS Domain Name) in your DHCP server or else configure the primary DNS Suffix on the client PCs:

(Assuming you are running Windows)

http://technet.microsoft.com/en-us/library/cc958929.aspx

http://technet.microsoft.com/en-us/library/cc786695(WS.10).aspx

 

[drebo]

What's providing DHCP for your "new portion"?

If it's not providing your FQDN as its domain name, then client computers don't have a default lookup domain. You need to make sure that the DHCP server is providing the correct DNS suffix. If they're statically assigned, you can set that within TCP/IP settings, too.

 

[Pantlegz]

What's providing DHCP for your "new portion"?

If it's not providing your FQDN as its domain name, then client computers don't have a default lookup domain. You need to make sure that the DHCP server is providing the correct DNS suffix. If they're statically assigned, you can set that within TCP/IP settings, too.

Awesome, this fixed it. I actually hadn't setup dhcp for the new portion for now there are only a few computers with the new ip addresses because I wanted to make sure everything was going to work wihtout issues before we switched everything over. Since I didn't have the option to setup a test network this is the next best thing.