DNS problems

[stevemoore]

Don't know what's happened here. Old machines on the network resolve names no problem. Just added a new server and it's not resolving. I think we may be running on cached information only and that DNS may not even be running (or installed!) anymore. You'll have guessed that I know next to nothing about this area - anyone got any help for a complete idiot!

 

[GiaBetiu]

Eheee,... who can help you without to know the DNS structure used there.
How many zones? How many servers? How are they connected? etc. Gia Betiu
m.betiu@chello.nl
Computer Eng. CNE 4, CNE 5, soon MCSE2k

 

[PeteH2]

GiaBetiu is right, this could be a bit sticky, but lets start from the start.

Somewhere, soemthing should(!) be running a DNS server. If you have a DHCP serving IP addresses, it could be the same server. Within the DNS server, there will be a DNS table showing primary and secondary DNS servers. It *sounds* as if this is not being updated.

I could very easily be wrong, but at least it's given you a sensible place to start.

HTH


Pete...

 

[stevemoore]

Right! I've got DHCP running on one server and WINS running on another.

 

[SgtB]

Well, you need to find out if DNS is running on any of your servers. Check our services on all your servers to see if the DNS server service is there and/or started. If thatdoes not work, then you can go to one of your old workstations (NT I presume) and run ipconfig /all form the command prompt. This will give you DNS info. Look for the IP of the DNS server that is specified on the lcient machine. Now locate your DNS server.

Now....is the DNS server up to date? How is DHCP configured? Does it point clients to a DNS server? Does it give the domain name?
Also everytime you add a server to your network you'll need to add it manually to your DNS server. If you don't then clients won't be able to resolve its name. You also need to specify the DNS server on the new server, or it won't know where to ifnd a DNS server.

If interested, check out these books. Very easy to read. Straight nad to the point.
First pick:

http://www.amazon.com/exec/obidos/A...7208383/sr=2-2/ref=sr_2_2/104-3309950-3251916

or:

http://www.amazon.com/exec/obidos/t...f=sr_1_1/104-3309950-3251916?v=glance&s=books

The last is a win2k DNS book, but a lot of the theory is still all the same.
________________________________________
Check out

http://www.security-forums.com

 

[SgtB]

Well, you need to find out if DNS is running on any of your servers. Check our services on all your servers to see if the DNS server service is there and/or started. If thatdoes not work, then you can go to one of your old workstations (NT I presume) and run ipconfig /all form the command prompt. This will give you DNS info. Look for the IP of the DNS server that is specified on the lcient machine. Now locate your DNS server.

Now....is the DNS server up to date? How is DHCP configured? Does it point clients to a DNS server? Does it give the domain name?
Also everytime you add a server to your network you'll need to add it manually to your DNS server. If you don't then clients won't be able to resolve its name. You also need to specify the DNS server on the new server, or it won't know where to ifnd a DNS server.

If interested, check out these books. Very easy to read. Straight nad to the point.
First pick:

http://www.amazon.com/exec/obidos/A...7208383/sr=2-2/ref=sr_2_2/104-3309950-3251916

or:

http://www.amazon.com/exec/obidos/t...f=sr_1_1/104-3309950-3251916?v=glance&s=books

The last is a win2k DNS book, but a lot of the theory is still all the same.

Hope this helps!
________________________________________
Check out

http://www.security-forums.com

 

[SgtB]

Double post!?!? Sorry bout that!
________________________________________
Check out

http://www.security-forums.com