Hey guys,
My company consists of roughly 25 computers. Should I bother setting up DNS on our server? We're going to be connecting to our branch office servers soon, and I was also wondering if this would play a role when uses try to connect to our server from the branch?
Thanks a bunch!
i think it's better to set up DNS on your server, it would be easier to access it.
How would DNS benifit us with such a small company?
How would DNS benifit us with such a small company?
If you don't use DNS you will have to give all pc's static IP's and programme the router with them too. Its just saves alot of configuration even for a small company like yoursevles. Its also alot more secure to use DNS. You should only really disable it if your running somthing like an internal web server.
Why do you think you should not use DNS:?:
If you don't use DNS you will have to give all pc's static IP's and programme the router with them too. Its just saves alot of configuration even for a small company like yoursevles. Its also alot more secure to use DNS. You should only really disable it if your running somthing like an internal web server.
Why do you think you should not use DNS:?:
Is this why our DHCP is acting up, maybe? Because we don't have DNS running?
Is this why our DHCP is acting up, maybe? Because we don't have DNS running?
Exactly right!:) You must enable DNS for DHCP to work correctly. It is only an advantage to enable DNS.
great.... okie doke. I'll do that either tomorrow or this weekend and I'll give you an update. ;)
I have another issue, which i'm assuming DNS will fix. I have a machine not showing up in our workgroup. I can ping it's IP and NETBOIS fine, but when I try to connect to it through Computers Near Me or by typing \\PCname it doesn't show up. any clue?
Yes DNS enabled should solve this. You won't be able to resolve the name to the ip address without DNS. Also check that the workgroup name on this machine is correct. You shouldn't really be using a workgroup with 25 machines it will start to cause problems. If possible you should create a domain.:)
The machines are on the same workgroup, yes.
You shouldn't really be using a workgroup with 25 machines it will start to cause problems. If possible you should create a domain.
That's one of the main reasons for our new network structure. We're in the process of switching over from peer-peer to client/server. I haven't gotten around to setting up the dc yet, as I can only do major events on Saturdays when noone is around, and I'm still transferring files from the old serv-computers.
My DHCP server keeps coming up with BAD_ADDRESS. I can delete them (over a hundred) and they just continue to come back, filling up the scope. Here's a bit of my log file...
16,07/09/06,16:53:49,Deleted,192.168.0.132,,xxxxxxxx,SERVER1\Administrator
16,07/09/06,16:53:49,Deleted,192.168.0.133,,xxxxxxxx,SERVER1\Administrator
16,07/09/06,16:53:49,Deleted,192.168.0.134,,xxxxxxxx,SERVER1\Administrator
16,07/09/06,16:53:49,Deleted,192.168.0.135,,xxxxxxxx,SERVER1\Administrator
16,07/09/06,16:53:49,Deleted,192.168.0.136,,xxxxxxxx,SERVER1\Administrator
31,07/09/06,16:53:50,DNS Update Failed,192.168.0.119,lagnew.,-1,
31,07/09/06,16:53:50,DNS Update Failed,192.168.0.129,itlaptop.,-1,
31,07/09/06,16:53:50,DNS Update Failed,192.168.0.137,zsummerfield.,-1,
31,07/09/06,16:53:51,DNS Update Failed,192.168.0.152,robert.,-1,
31,07/09/06,16:53:51,DNS Update Failed,192.168.0.163,b-holmes.,-1,
10,07/09/06,16:53:51,Assign,192.168.0.130,,30303A31333A37323A34383A37643A3634696E66313030303030,
13,07/09/06,16:53:51,Conflict,192.168.0.130,BAD_ADDRESS,,
31,07/09/06,16:53:52,DNS Update Failed,192.168.0.181,BOBBY.,-1,
31,07/09/06,16:53:52,DNS Update Failed,192.168.0.204,Win2k-Server-01.,-1, .......... 13,07/09/06,16:54:18,Conflict,192.168.0.69,BAD_ADDRESS,,
10,07/09/06,16:54:31,Assign,192.168.0.70,,30303A31333A37323A34383A37643A3634696E66313030303030,
13,07/09/06,16:54:31,Conflict,192.168.0.70,BAD_ADDRESS,,
16,07/09/06,16:54:32,Deleted,192.168.0.69,,xxxxxxxx,SERVER1\Administrator
16,07/09/06,16:54:32,Deleted,192.168.0.94,,xxxxxxxx,SERVER1\Administrator
16,07/09/06,16:54:32,Deleted,192.168.0.130,,xxxxxxxx,SERVER1\Administrator
16,07/09/06,16:54:32,Deleted,192.168.0.182,,xxxxxxxx,SERVER1\Administrator
16,07/09/06,16:54:32,Deleted,192.168.0.212,,xxxxxxxx,SERVER1\Administrator
10,07/09/06,16:54:44,Assign,192.168.0.69,,30303A31333A37323A34383A37643A3634696E66313030303030,
13,07/09/06,16:54:44,Conflict,192.168.0.69,BAD_ADDRESS,,
10,07/09/06,16:54:57,Assign,192.168.0.71,,30303A31333A37323A34383A37643A3634696E66313030303030,
13,07/09/06,16:54:57,Conflict,192.168.0.71,BAD_ADDRESS,,
10,07/09/06,16:55:10,Assign,192.168.0.72,,30303A31333A37323A34383A37643A3634696E66313030303030,
13,07/09/06,16:55:10,Conflict,192.168.0.72,BAD_ADDRESS,,
10,07/09/06,16:55:23,Assign,192.168.0.73,,30303A31333A37323A34383A37643A3634696E66313030303030,
13,07/09/06,16:55:23,Conflict,192.168.0.73,BAD_ADDRESS,,
10,07/09/06,16:55:36,Assign,192.168.0.74,,30303A31333A37323A34383A37643A3634696E66313030303030,
13,07/09/06,16:55:36,Conflict,192.168.0.74,BAD_ADDRESS,,
10,07/09/06,16:55:49,Assign,192.168.0.75,,30303A31333A37323A34383A37643A3634696E66313030303030,
13,07/09/06,16:55:49,Conflict,192.168.0.75,BAD_ADDRESS,,
10,07/09/06,16:56:02,Assign,192.168.0.76,,30303A31333A37323A34383A37643A3634696E66313030303030,
13,07/09/06,16:56:02,Conflict,192.168.0.76,BAD_ADDRESS,,
10,07/09/06,16:56:15,Assign,192.168.0.77,,30303A31333A37323A34383A37643A3634696E66313030303030,
I have no clue why I continue to get so many BAD_ADDRESS entries. We are switching over from a 13.240.x.x structure to 192.168.x.x. Most computers have two NICs in them, and the LAN was statically set on one of the cards. I've went around to most of the machines and disabled the static cards and left the other (or changed the other) to obtain from DHCP. Would this be part of the problem some how?
I'm also recieving NACK messages...
Have you enabled DNS yet?:?:
It sounds like it is part of the same problem. DHCP won't run properly without DNS. Sounds like ticking that dNS enabled box will be the answer to alot of your problems.
Well I have DNS setup on a test machine, and for now DHCP is pointing to that. I'm not sure if it's setup correctly or not, but I do know that without it none of the machines can access the internet. But none of the computers create their own record in the DNS zone... So I'm not sure what the problem is.
Well I have DNS setup on a test machine, and for now DHCP is pointing to that. I'm not sure if it's setup correctly or not, but I do know that without it none of the machines can access the internet. But none of the computers create their own record in the DNS zone... So I'm not sure what the problem is.
I think you should set up DNS on your DHCP server. Keep it as simple as possible. Set all machines to obtain DNS automatically. I think i would need to see the network topology i'm finding it hard to visualize how you have got your network set up.:rolleyes: Do you have a router that can deal with dhcp?
I attached a basic drawing of our network. I have DHCP disabled on the router. The modem is DSL.
I was going to setup DNS on our server after i got the test machine working, but it was late and I'm not sure i have it setup right anyways. :sad:
The server, switch and router have static IPs and the clients get their IP from the Server. Tell me if you need anything else...
Thanks a bunch by the way.
I attached a basic drawing of our network. I have DHCP disabled on the router. The modem is DSL.
I was going to setup DNS on our server after i got the test machine working, but it was late and I'm not sure i have it setup right anyways. :sad:
The server, switch and router have static IPs and the clients get their IP from the Server. Tell me if you need anything else...
Thanks a bunch by the way.
What does your server do?
Is it just a file server?
Will people from your branch office need to connect to it from outside of this network?
Is the server running windows 2003?
Is it going to be the dc?:?::?::?:
What OS are the pc's running?
What does your server do?
Is it just a file server?
Will people from your branch office need to connect to it from outside of this network?
Is the server running windows 2003?
Is it going to be the dc?:?::?::?:
What OS are the pc's running?
Hey again,
This is our only server and it functions/will function as our print, dhcp, file, dns and terminal licensing server and will be the only DC on our network. People will be connecting to the server from the branch office outside of the network, yes. The server is running Server 2003 standard x64. The PCs are running XP/2000 and one NT4.0 machine.
Thanks for the help
Here is a link to a website with with alot good info on how to setup your server. It might not be exactly what your after but should explain the setup of DNS on your server a bit better. Look in the Active Directory section.
http://www.visualwin.com/ .:)
Here is a link to a website with with alot good info on how to setup your server. It might not be exactly what your after but should explain the setup of DNS on your server a bit better. Look in the Active Directory section.
http://www.visualwin.com/ .:)
Just wondering, will DNS work right without AD?
Also, I'm having a problem with my forward lookup zone. When I type ipconfig /registerdns I can check the DNS server and a PTR record is created but not a host record.
Just wondering, will DNS work right without AD?
Yes DNS will run without AD that is just a guide on how to set it up in AD.:)
Yes DNS will run without AD that is just a guide on how to set it up in AD.:)
groovy, what about the forward lookup zone problem? any clue on that?
Also, I'm having a problem with my forward lookup zone. When I type ipconfig /registerdns I can check the DNS server and a PTR record is created but not a host record.
Is this any help:
:cool:
Is this any help:
:cool:
Oh ok, does the forward lookup zone not automatically update itself with the PTR records?
When we type ipconfig /register dns it creates a PTR record but not a Host record.
Oh ok, does the forward lookup zone not automatically update itself with the PTR records?
When we type ipconfig /register dns it creates a PTR record but not a Host record.
Correct.
so what about when someones IP lease is up.... do i have to go in manually and delete the host record and then create another one for the new ip?
so what about when someones IP lease is up.... do i have to go in manually and delete the host record and then create another one for the new ip?
No thats where DNS comes in again, it uses the computer name to resolve the ip. You shouldn't have to create another because the computer name remains the same.:!:
No thats where DNS comes in again, it uses the computer name to resolve the ip. You shouldn't have to create another because the computer name remains the same.:!:
Oh snap. ;)
well poop, I don't know what I'm doing wrong. I have DNS setup but when I change an IP and registerdns it fixes the ptr record but not the host (A) record. I tried new zone delegation but no dice... i figured i had to do that. Don't know why.
what would happen if someone didn't create a reverse lookup zone? how would host records be updated?
I'm also still having this problem:
all scopes for dhcp clients fluded with bad_address
entries.
My DHCP server is Win 2003 standard with only one network
interface enabled. And there is 5 conflict detection attempt
configured. All knowlege base articles that i found out
does not match my situation.
And very interesting that all this bad_address appears
with 6-bytes Unique Identifier, when all other clients
have MAC address as Unique Identifier.
Did anybody know what is the possible reason of such
behaviour?
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.
