Any Windows 2008 Server admins on here?

  • Thread starter Hetzkes Ballet Teacher
  • Start date

Status
Not open for further replies.
H

Hetzkes Ballet Teacher

Guest
How the f** b** h*** do you get its p** DHCP server to update its w*** DNS server with client details (standalone server not AD)?

It just wont f* do it, the c*** t***. :evil:
 
Ask me in 2 months once I've done the fundamentals course.
 
Just do it manually man - ipconfig/registerdns

Or if DHCP server is 2008, go into the scope properties, click on DNS tab and make sure 'Enable DNS ...' and ' Always dynamically update' boxes are ticked

Why you giving a server a dynamic IP address anyhoo ?
 
Last edited:
Nah man, it's a DHCP *server* - it's giving IP addresses to clients. It's also supposed to update its internal DNS server with those names/IP addresses, so they can be referred to on the network.

But I've already done all of that (including defining an account for the DHCP server to authenticate itself to the DNS server with) and it just f***ing wont do it. I f***ing bastard hate f***ing twatting Microsoft.

EDIT: sorry, forgot to bastard asteriskify.
 
Last edited:
Nah man, it's a DHCP *server* - it's giving IP addresses to clients. It's also supposed to update its internal DNS server with those names/IP addresses, so they can be referred to on the network.

But I've already done all of that (including defining an account for the DHCP server to authenticate itself to the DNS server with) and it just f***ing wont do it. I f***ing bastard hate f***ing twatting Microsoft.

EDIT: sorry, forgot to bastard asteriskify.

DHCP client service started on the PC ? Owt in the event logs ?

You looked on your DNS server to make sure Dynamic Updates are allowed ? (Right click on the forward lookup zone, properties, general tab and make sure Dynamic Updates not set to 'None') Think this is only if FLZ is AD Integrated tho :confused:
 
Last edited:
Nah man, it's a DHCP *server* - it's giving IP addresses to clients. It's also supposed to update its internal DNS server with those names/IP addresses, so they can be referred to on the network.

But I've already done all of that (including defining an account for the DHCP server to authenticate itself to the DNS server with) and it just f***ing wont do it. I f***ing bastard hate f***ing twatting Microsoft.

EDIT: sorry, forgot to bastard asteriskify.

Have you tried switching it off then switching it back on?
 
DHCP client service started on the PC ? Owt in the event logs ?

You looked on your DNS server to make sure Dynamic Updates are allowed ? (Right click on the forward lookup zone, properties, general tab and make sure Dynamic Updates not set to 'None') Think this is only if FLZ is AD Integrated tho :confused:

Aye I've checked absolutely everything I can think of:

1) DHCP server (*) set to dynamically update DNS server (*), and is configured with an account for authentication.

2) DNS server (*) set to accept both secure and insecure dynamic updates.

3) DNS server (*) has primary zone "local" defined, which forwards unknown names to the ISP.

4) DHCP and DNS servers (*) are bound to the NICs they should be.

5) DHCP server sends "local" as the domain name to the clients (I want to address all clients as <HOSTNAME>.local - I'm not using NetBIOS/WINS, just DNS)

6) Clients (Win7 and Vista) all set correctly. They get their IPs, DNS server IP, gateway IP and domain name. Their DNS lookups work for sites on the internet.

(*) all on the same machine, a standalone WS 2008 R2 server.

BUT you just never see anything appearing in the DNS server's "local" zone under Forward Lookup Zones (except the server itself, which has registered itself there).

And nothing appears in any event logs to indicate that something didn't work, on either server or clients. Yet no client can resolve <HOSTNAME>.local for any other clients' host name, yet everything (ping, file sharing etc) works if you just use explicit IP addresses

And "ipconfig /registedns" on the clients doesn't seem to fail (no error in the event log), yet nothing changes - it still behaves exactly as above.

I'm completely baffled, and I've hardly got any wine left.
 
Check Scavenging is not set to 1 day in DNS.

Scavenging isn't currently enabled.

I think I must be missing something utterly obvious. Keeping in mind that there's no WINS or NetbIOS over TCP/IP (disabled on all NICs, server and clients) how can this happen (m1 is a client):


ping m1

Pinging M1 [192.168.101.100] with 32 bytes of data:
Reply from 192.168.101.100: bytes=32 time<1ms TTL=128
Reply from 192.168.101.100: bytes=32 time<1ms TTL=128
Reply from 192.168.101.100: bytes=32 time<1ms TTL=128
Reply from 192.168.101.100: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.101.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

ping m1.local
Pinging M1 [192.168.101.100] with 32 bytes of data:
Reply from 192.168.101.100: bytes=32 time<1ms TTL=128
Reply from 192.168.101.100: bytes=32 time<1ms TTL=128
Reply from 192.168.101.100: bytes=32 time<1ms TTL=128
Reply from 192.168.101.100: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.101.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

nslookup m1

Server: UnKnown
Address: 192.168.100.1

UnKnown can't find m1: Non-existent domain

nslookup m1.local

Server: UnKnown
Address: 192.168.100.1

UnKnown can't find m1.local: Non-existent domain


How can ping resolve the name, but not nslookup?
 
Last edited:
Hmm, you running IPv6?

What happens if you manually enter IP info into one of the clients? Does it then register?
 
Hmm, you running IPv6?

What happens if you manually enter IP info into one of the clients? Does it then register?

Nope, IPv6 is disabled everywhere. I'll try the manual IP thing.

I'm wondering if this is anything to do with the use of a single label domain name (".local") as mentioned here. I'm not using AD, but it would be absolutely typical of MS to balls that up generally.

This is for me house. I don't want to have to type a three label name (host. unnecessarymiddlebit.local) just because MS can't get anything right. :evil:
 
Easiest way is to do a packet trace from the client if theres nowt in the logs - 'Wireshark' is pretty good and free. Not hard to do and you'll find out exactly why it's happening.

In the meantime, temporarily disable firewalls on both client and server and give it another pop.
 
The problem was what I said in the last post - Windows just doesn't like single label internal domain names. Changed it from "local" to "house.local" and everything now works exactly as it should, nee bother.

15 hours of my life that took me to find, and it'll be another couple before I get everything else back the way it was (firewalls, etc). I absolutely f***ing hate Microsoft.

Thanks for the help though, kept me working on it when I was ready to give up.

One plus point I didn't expect though - it automatically configures domain search paths, so even without WINS I can still refer to machines just by their names, without the .house.local on the end.
 
Status
Not open for further replies.

Back
Top