Setting DNS up for domain & internet 2

[tsmithind]

I think all these problems are connected, but if they aren't. . .my bad. I work at a small engineering company with a network of 10 users with machine 192.168.0.10 being the one server running W2K Server. The clients are some W98 some W2K all logging into the same domain. I am not doing any Web hosting.

I want to get DNS working to do the local name resolution. But I also want to machines to go to the ISP for it's internet DNS. Right now on the clients the DNS entries point to the ISP's addresses, not our server.

The things that don't work: 1.) I get an error message in the Application Log on the server. . .It is a Userenv Event ID 1000 error: Windows cannot obtain the domain controller name for your computer network. Return value (59.)

2.) I want to use Computer Management in W2K Pro to manage other W2K machines, but when I click onto another machine in the browsing list in Computer Management it says "Computer \\Domain1.ABCD.DCBA.COM cannot be managed. The network path was not found." (I changed the path name just to keep it generic here.) Even though I have the proper permissions to manage the other computer, it brings that error up.

So I'd like to set DNS up on the clients to still browse the internet (which the Default Gateway points to router 192.168.0.1, not the server) and also get DNS to work so the above things work.

 

[FilthPig]

Here's what you do. You install DNS on the local server, allow dynamic updates in your forward and reverse lookup zones for your local domain. When you right-click the server and choose properties, there's a tab for forwarders. Enter your ISP's DNS server as a forwarder, and the DNS server will forward all requests that do not exist in it's local zone or cache to the forwarder. Configure your clients to point to your local DNS server. The ISP's DNS server will then perform the lookup, return the data to the local DNS server (which caches it for future lookups), and the local dns will give the data back to the client. Marc Creviere

 

[tsmithind]

Thanks! However when I go to the DNS Management Console it tells me, under Forwarders, that it is not available because this is a root server. How to I fix this?

 

[ZeRoMaX]

I have a similar setup. My question is that when I do nslookup I get the DNS of my server but not my ISP DNS is this suppose to happen?

 

[AlexIT]

tsmithind,

Go delete the root zone "." and then reboot. Now you can add a forwarder.

Zero,

nslookup on a client of the local DNS server will show the local DNS server.

Alex

 

[TechJones]

HI all new user here.
I had the same issue with my network I'm sure it must be common.
If you look at the forward lookup zone in DNS you will notice that there is a DOT folder(.)at the top of the tree. This tells the DNS server that it is a root server and does not need to use forwarders.
to cure the problem simply delete the dot folder and then go to your forwarders option and it shouldn't be grey'd out any more.
If it is still grey then come out of DNS and go backin in order for it to refresh.
let me know
Gary.

 

[tsmithind]

I had done the above (the DNS is dynamically updated and integrated with Active Directory, and the resolver points to the same computer)

Now I get error 4011 in my event log when booting. Evidently the _ldap _gc etc are "unable to to add or write an update in DNS or something."

 

[FilthPig]

Ok, in the DNS console, right-click on your forward lookup zone for your domain, select properties, and on the General Tab set Allow Dynamic updates to Yes. Marc Creviere

 

[tsmithind]

It's already checked to allow dynamic updates.

 

[donnie4564]

Remove DNS from the server.

Reinstall DNS
do not add any zones.
right click the DNS server from the DNS mmc console
choose properties
choose the forwarders tab
add the address to your ISP DNS server
This will create a DNS caching only server, For ten users I would keep it as simple as possible.

Install Wins on the W2K server, Add the address of the wins server to all client PC's.

 

[DanniBoy]

Hello, I am messing around with w2k server. I installed it and installed a DSN and an Active directory ect. Now I have another computer connected to a hub that is connected to the server. I have been trying to make that computer join the domain, but it tells me that the domain does not exists!!! Now, when i go to the network conection on both computers they can see each other!!! My "user" pc has XP on it. Now what I want to do is that when that computer is turned on, they have to put their password to join the domain. Also I just want my user pc to only be able to use the internet. Just like an ISP!!! Can someone help me out!! I have the book, "Teach Your Self WK2 Server" But am stuck!!! Thanks
Daniel

 

[donnie4564]

If any 2000 computer cannot find a 2000 domain, then the first place to start is DNS. When the computer boots it looks for dhcp unless you have static address assigned. It then uses the address to find the DNS server, which will tell it where the domain controller is.

Start at the client pc type ipconfig /all at a command prompt, verify the address to the dns server

ping the dns address to verify the dns server can be reached.

ping the host name of the dns server to verify the dns server can be reached using name resolution.

nslookup on the dns server can tell you if the dns server is registered with itself. At the nslookup prompt type the hostname of the domain controller. The DC has to be registered with the DNS server or clients cannot locate the DC.

The DNS server must have it's own address in the dns address in tcp/ip properties on the dns tab.

 

[C5Thunder]

DNS is a requirement for a Win2K Domain. For small businesses, i will list the ideal setup:

1- Install DNS on a Win2K server and enable dynamic updates.
2- Create a forward lookup zone. The domain name of the zone must match you Win2K AD domain name (i.e. company.com or company.local)
3- Make sure that you didnt create the DOT '.' forward zone. This can be done by mistake if you put a DOT '.' after the .com or .local when creating your zones (i.e. company.com. , this is wrong)
4- Create a reverse lookup zone.
5- Point your Win2K domain controller to your DNS server. If you installed dns before upgrading to Active Directory you should have no issues. If not then reboot your Domain Controller (even if the DC is your DNS server). rebooting will cause Active Directory to register the FSMOs information in dns, which is required for clients to locate a domain for logon, among other things.
6- Right-click on your dns server in the DNS MMC and add your ISPs DNS addresses under the Forwaders Tab. Note that most menus and options can be done by right clicking on stuff under Win2K, especially when using the MMC.
7- Point all of your clients and other servers to your internal DNS (just like you did with the Domain Controller). The easiest thing to do with clients is utilize DHCP.
8- You can install WINS for backward compatibility (apps, win98, etc.) but try not to use it unless neccessary.

 

[DanniBoy]

What am I suppose to put in my reverse lookup zone? Also I have not installed my domain controler, actualy I started all over, and am not instaling it because of this:"Point your Win2K domain controller to your DNS server. If you installed dns before upgrading to Active Directory you should have no issues." So am trying to install the dns first. but on step 4, I dont know what network ID to put. Is that any number or where do I find it.
Thanks
DanniBoy

 

[C5Thunder]

Your IP address range is broken down by class/subnet. It is divide into a 'Network' portion and a 'Node' portion. The node portion is the different IPs you assign to your servers/users. The Network portion is what comes before the node in your IP address scheme.

Follow this example for step 4:

If you are using 192.168.1.x (Class C)for your network, then the first 3 octets will be your network ID (i.e. 192.168.1) and the last octet (which is the x) is your IP range.

All you need to fill out is the Network ID portion. dont worry about the rest. If you are using a Class B network ID (i.e. 172.16.x.x) then only enter (172.16) and leave the 3rd space empty. So, in summary:

10.x.x.x (Class A)= 10 (Network ID)
172.16.x.x (Class B)= 172.16 (Network ID)
192.168.1.x (Class C)= 192.168.1 (Network ID)

and so on...

 

[Ouch]

i have a similar problem my dns seems to work but i am trying to connect a computer on another subnet to my domain and it comes up with the 'cannot find domain' error.

can anyone help?

 

[itsfisko]

Ok I get the Forwarders bit and have pointed this to my ISP plus I have set up DHCP. This all works fine, My question is what do I do at the client ( I have XP pro clients)I have set them up to get their IP address from Dhcp but what do I do with the DNS? or do I just leave this? Some lead, some follow....I just Hope!

 

[GrnEyedLdy]

Your DHCP scope should be configures to give out the address of your Internal DNS server. Then if your clients try to resolve a request that is not local, the forwarders start to do their job.

Hope this helps

Patty

 

[itsfisko]

Thanks Patty, I guessed as much but just wanted to be sure that I had got the clients configed OK ta itsfisko Some lead, some follow....I just Hope!