Registering DNS in a Workgroup

[sparkeh]

Ok here is the setup:

RM schoolshare network (peer-to-peer) with Storebox (Win2000 Server).

The Storebox is on its own domain (lets call it SB.net) and the machines are in a workgroup (lets call Workgroup).

 

What I want to do:

Use the Storebox as a DNS server so I can use certain network tools (such as Spiceworks)

 

Where I am up to:

So DHCP is working and clients pick up an IP, router address and can be pointed at the Storebox for DNS. Dynamic DNS is enabled.

DNS server is running and forwarders are setup, clients can be pointed to the Storebox for DNS and can access the internet.

 

Where I am stuck:

So, I want to register the clients machines in DNS so local lookups and can performed. I am not at all sure how to do this as I have always used DNS in a domain before.

 

DNS server has two forward lookup zones: local and SB.net (containing pointers to itself) and one reverse zone 1.2.3.x Subnet.

 

I have read that one way to achieve this, is to give each machine a DNS suffix that matches a DNS forward lookup zone but this doesn't seem to do anything.

 

So I need to create new zones...or well..I dunno really...help

[sparkeh]

Update: reverse lookup works?!

 

Just need to know how to setup forward lookup

[powdarrmonkey]

Have DHCP add forward records to DNS and enable the "even when clients think they know what they're doing" options.

[sparkeh]

DHCP is set update DNS.

 

I have tried adding a primary DNS suffix to a machine (using SB.net) but still it doesn't show up.

[sparkeh]

I managed to get the machines registered in DNS by adding a suffix to the NIC and ticking "Use this connection's DNS suffix in DNS registration"

[SimpleSi]

I have W2k3 servers and non-domain clients at all my schools so I'm very interested in what you are doing as I have issues with non-windows machine names not being resolvable (linux cachepilot)

 

So, I want to register the clients machines in DNS so local lookups and can performed

 

But why? does the windows workgroup automagical name resolution not work for you

 

Have DHCP add forward records to DNS and enable the "even when clients think they know what they're doing" options.

 

Agreeed - tick every box you can lay yours hands on and ignore any msgs that ask if you are mad

 

I managed to get the machines registered in DNS by adding a suffix to the NIC and ticking "Use this connection's DNS suffix in DNS registration"

 

Now - this looks interesting - which NIC - server or clients?

 

regards

 

Simon

[sparkeh]

But why? does the windows workgroup automagical name resolution not work for you

This mainly sprung up as I want to use Spiceworks on the network. It seems that you need a DNS server running with forward and reverse lookup to get the network scan running properly. Without it I was getting loads of DNS errors during the scan.

 

Now - this looks interesting - which NIC - server or clients?

 

Ok so what I did on the client NIC: go to Advanced TCP/IP settings, and under "DNS suffix for this connection" add the name of the forward lookup zone on the DNS server (in my case SB.net). Then I ticked "Use this connection's DNS suffix in DNS registration". This means that it registers in the correct place.

 

After releasing and renewing IP lease it shows up in DNS.

 

Actually I altered it a bit as DHCP can give out the DNS suffix - option 015 DNS domain name. Now I just have to tick the "Use this connection's DNS suffix in DNS registration" box for each machine. But this can be done by a script or something that alters it in the reg.