DNS server issue server 2003 std

[janesssssy]

Today I have created a new DNS server & DC. Its goingin to one of our small offices connecting to our large office over a VPN.
So today I created it and and configured the DNS. As I'm installing Monday morning I shut the server down and packing up in the car.

However, next thing I know is the whole network - 100 odd computers couldn't connect to our exchange server that is in France.

I double checked some client systems and did a NSlookup and they all pointed to the existing server in our local office. I'm a little confused, and I may be in a little trouble...

Can someone tell me a definitive reason why this has happened?

 

[oddjob62]

So the clients are pointing to a DC that is still in the office, switched on, and is working fine? Any errors in the event logs?

Also you mention "small office" "large office" "france office" "whole network" "local office"... are these all different or the same? Maybe a quick diagram would help.

Did you literally DCpromo and add DNS on the new server?

How do they connect to this france server? Is there a VPN? Outlook Anywhere?

 

[janesssssy]

So the clients are pointing to a DC that is still in the office, switched on, and is working fine? Any errors in the event logs?

Also you mention "small office" "large office" "france office" "whole network" "local office"... are these all different or the same? Maybe a quick diagram would help.

Did you literally DCpromo and add DNS on the new server?

How do they connect to this france server? Is there a VPN? Outlook Anywhere?

I cant do a diagram as posting using my phone.

We have a 'main UK' office with several servers with 2 DC's and 1 DNS server.
The 'main UK' office connects to France over a VPN link. This is used for email.

We also have 4 satellite offices scattered in the UK. So... I have installed Server 2003 std in the 'main UK' office. Ran DC promo and made it a DC. then rebooted and added the DNS role.

I think this is the mistake I made. - Configured DNS using the different IP range! whilst the network cable was in! although all the clients in the 'main UK' office were still pointing to the existing DNS server. checked via ipconfig /all and NSlookup. This is where the confusion came from.

umm ho hum.

 

[Deleted member 77746]

Adding a DNS server won't change anything unless you have asked the clients to use that DNS server, which will require someone to modify the DHCP settings to act on this change.

I suggest you do a few policy checks / nslookup / ipconfigs on the machines that are having this issue.

Why did you add a new DNS server, was it needed? ...

 

[NiCkNaMe]

You haven't done anything funky like raising the functional level when you added the new DC?

A few more specifics is needed really... the only connectivity issue you state is with the exchange box in France... can clients see this box? What site did you configure this 'new' DC in?

Too much scope, not enough info

Don't stress - go back to basics. Grab a client machine that is not working and work out how far it can get, and what messages Outlook or whatever email client you are using gives.

 

[Nutbusta]

The DC would have registered itself as an authoratative naming server for the domain.
You should check that the DC doesnt have any records in the top level of the dns forward zone and remove it from the properties > name server tab.

Restarting the server when onsite will recreate the A & NS record and thus repopulate the NS tab.

You should also check sites and services is configured correctly including all the subnets. I'm guessing the combination is causing your problem.

Hope it helps. Let us know

 

[janesssssy]

Its all sorted now, it seems as though that the DNS records from the main DNS server went walkies. Although this had nothing to do with me just a coincidence!

My DNS server is working perfectly fine in the external office.

Thanks for your help people. much appreciated. Panic over.