Worrying network issues

talksr · December 10, 2015

Looks like the server took a DHCP based address originally, and that record still exists (Guessing that's what the other machine IP is?)

Put the proper IP back as a static record for that HOST. (Also check you aren't giving out the static range of IP addresses)

And then re-clear cache etc and try it

Steve

Ok, so let me just check....

I delete the A record stm-sr-002, then right click stm.internal and select New Host (A or AAAA) and in the settings do: ]

Name: stm-sr-002

FQDN: "stm.internal."

IP address: 10.75.44.11

Leave un-ticked:

Create associated pointer (PTR) record

Allow any authenticated user to update DNS records with the same owner name.

In response to your question, I did set a static reservation for this server, but it is very well possible that it did obtain a DHCP address when it was first installed on the network.

Steve21 · December 10, 2015

Ok, so let me just check....

I delete the A record stm-sr-002, then right click stm.internal and select New Host (A or AAAA) and in the settings do: ]
Name: stm-sr-002
FQDN: "stm.internal."
IP address: 10.75.44.11
Leave un-ticked:
Create associated pointer (PTR) record
Allow any authenticated user to update DNS records with the same owner name.

In response to your question, I did set a static reservation for this server, but it is very well possible that it did obtain a DHCP address when it was first installed on the network.

Tick PTR too, no idea why your reverse is empty as it shouldn't be

But yes, once that's in, clear your caches and try to do "ping server" again and see what IP comes up (try from client once both caches cleared)

Steve

talksr · December 10, 2015

Tick PTR too, no idea why your reverse is empty as it shouldn't be

But yes, once that's in, clear your caches and try to do "ping server" again and see what IP comes up (try from client once both caches cleared)

Steve

Ok,

I deleted it and re-added it, as below, but got an error:

I do find it odd that in that dialogue box, the FQDN has a full stop at the end. That just doesn't look right to me.

Should it not be: stm-sr-002.stm.internal, without the . at the end?

Edited December 10, 2015 by talksr

Steve21 · December 10, 2015

The . is normal. Always adds one mine is for example: "DOM.sch.uk."

The PTR bit do you have a reverse lookup zone created? If not that would give that error. But you could ignore that if you want but should still have them really as that's what converts an IP to a HOSTNAME

But if you try to ping the hostname does that ping now? (cache cleared on servers and client)

Steve

talksr · December 10, 2015

The . is normal. Always adds one mine is for example: "DOM.sch.uk."

The PTR bit do you have a reverse lookup zone created? If not that would give that error. But you could ignore that if you want but should still have them really as that's what converts an IP to a HOSTNAME

But if you try to ping the hostname does that ping now?

Steve

Ah ok, that is reassuring, no unfortunately no reverse, that is all blank. DNS is not my strength (as you may have noticed!).

Just clearing the cache now and will re-try.

talksr · December 10, 2015

The . is normal. Always adds one mine is for example: "DOM.sch.uk."

The PTR bit do you have a reverse lookup zone created? If not that would give that error. But you could ignore that if you want but should still have them really as that's what converts an IP to a HOSTNAME

But if you try to ping the hostname does that ping now? (cache cleared on servers and client)

Steve

I think we are in luck Steve, it is looking good.

talksr · December 10, 2015

It works! So the resolution was as you suggested,

Remove the old DNS A record (which must have been created when the second server was on DHCP, and then re-create the A record with PTR option ticked.

Thank you very much for your help and that of all of the other contributors.

Steve21 · December 10, 2015

I'd suggest you do two things too, check what range your DHCP is giving out, and make a small amount of room at the start for static allocations if you don't

And fix your reverse lookup zones.

If you try nslookup serverIP it'll still fail as there's nothing to resolve it to

But at least that's sorted

Steve

mikkydoos · December 10, 2015

Hi, yes there does seem to be one (DNS>STM-SR-001>Forward Lookup Zones>stm.internal):
stm-sr-002 Host (A) 10.75.44.72 04/08/2015

However, there are inconsistencies with it.
The IP address or "data" field shows 10.75.44.72 but that is wrong. The IP is 10.75.44.11
This is a statically assigned address, however the Timestamp does not say this like it does on the frdc.
[ATTACH=CONFIG]33840[/ATTACH]

1. It could be that when you first set the server up, you named it, but it was on DHCP and that A record was created.

2. @psydii is right, there could be another host with the same name

3. Is the new server named the same as an old one. If so, is the old machine still running - get rid or rename if so

In any case,

Delete that record. - Check for it in the Forward AND reverse lookups - delete both

Go to -002, ipconfig /release, ipconfig /renew, ipconfig /flushdns, ipconfig /registerdns

Find the new record.

Set it to static.

That should do it.

mikkydoos · December 10, 2015

I'd also strongly recommend this too.

On your DC (command prompt)

dcdiag /test:dns

That will tell you if there's a problem

talksr · December 10, 2015

I'd suggest you do two things too, check what range your DHCP is giving out, and make a small amount of room at the start for static allocations if you don't

And fix your reverse lookup zones.

If you try nslookup serverIP it'll still fail as there's nothing to resolve it to

But at least that's sorted

Steve

Steve, aka DNS God, you are again correct.

nslookup continues to fail and yes I would quite like to address the reverse, will need to do a little reading up on it as this is a live server and I don't want to mess anything up.

With regards DHCP, I had already thought about that one, I set the scope as .20-219, this gave me a few 1-19 for servers, tills, printers etc, and then 220-255 for anything else.

talksr · December 10, 2015

1. It could be that when you first set the server up, you named it, but it was on DHCP and that A record was created.

2. @psydii is right, there could be another host with the same name

3. Is the new server named the same as an old one. If so, is the old machine still running - get rid or rename if so

In any case,

Delete that record. - Check for it in the Forward AND reverse lookups - delete both

Go to -002, ipconfig /release, ipconfig /renew, ipconfig /flushdns, ipconfig /registerdns

Find the new record.

Set it to static.

That should do it.

Your number one suggestion was exactly what it was! Thanks for the suggestion.

mikkydoos · December 10, 2015

Still run dcdiag on your dc.

If it doesn't pass the test, you still have a problem m8

talksr · December 10, 2015

Still run dcdiag on your dc.

If it doesn't pass the test, you still have a problem m8

Its looking good....

C:\Users\Administrator>dcdiag /test:dns

Directory Server Diagnosis

Performing initial setup:
Trying to find home server...
Home Server = stm-sr-001
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\STM-SR-001
Starting test: Connectivity
......................... STM-SR-001 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\STM-SR-001

Starting test: DNS

DNS Tests are running and not hung. Please wait a few minutes...
......................... STM-SR-001 passed test DNS

Running partition tests on : ForestDnsZones

Running partition tests on : DomainDnsZones

Running partition tests on : Schema

Running partition tests on : Configuration

Running partition tests on : stm

Running enterprise tests on : stm.internal
Starting test: DNS
......................... stm.internal passed test DNS

C:\Users\Administrator>

mikkydoos · December 10, 2015

You might want to do a

c:> dcdiag

That will check your AD (and DNS) replication too

talksr · December 10, 2015

You might want to do a

c:> dcdiag

That will check your AD (and DNS) replication too

Thanks, it looks good with this report too:

C:\Users\Administrator>dcdiag

Directory Server Diagnosis

Performing initial setup:

Trying to find home server...

Home Server = stm-sr-001

* Identified AD Forest.

Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\STM-SR-001

Starting test: Connectivity

......................... STM-SR-001 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\STM-SR-001

Starting test: Advertising

......................... STM-SR-001 passed test Advertising

Starting test: FrsEvent

......................... STM-SR-001 passed test FrsEvent

Starting test: DFSREvent

There are warning or error events within the last 24 hours after the

SYSVOL has been shared. Failing SYSVOL replication problems may cause

Group Policy problems.

......................... STM-SR-001 failed test DFSREvent

Starting test: SysVolCheck

......................... STM-SR-001 passed test SysVolCheck

Starting test: KccEvent

......................... STM-SR-001 passed test KccEvent

Starting test: KnowsOfRoleHolders

......................... STM-SR-001 passed test KnowsOfRoleHolders

Starting test: MachineAccount

......................... STM-SR-001 passed test MachineAccount

Starting test: NCSecDesc

......................... STM-SR-001 passed test NCSecDesc

Starting test: NetLogons

......................... STM-SR-001 passed test NetLogons

Starting test: ObjectsReplicated

......................... STM-SR-001 passed test ObjectsReplicated

Starting test: Replications

......................... STM-SR-001 passed test Replications

Starting test: RidManager

......................... STM-SR-001 passed test RidManager

Starting test: Services

......................... STM-SR-001 passed test Services

Starting test: SystemLog

An error event occurred. EventID: 0x0000272C

Time Generated: 12/10/2015 14:41:36

Event String:

DCOM was unable to communicate with the computer 172.30.178.53 using

any of the configured protocols; requested by PID 1c60 (C:\Windows\system32

\dcdiag.exe).

An error event occurred. EventID: 0x0000272C

Time Generated: 12/10/2015 14:42:02

Event String:

DCOM was unable to communicate with the computer 172.30.178.54 using

any of the configured protocols; requested by PID 1c60 (C:\Windows\system32

\dcdiag.exe).

......................... STM-SR-001 failed test SystemLog

Starting test: VerifyReferences

......................... STM-SR-001 passed test VerifyReferences

Running partition tests on : ForestDnsZones

Starting test: CheckSDRefDom

......................... ForestDnsZones passed test CheckSDRefDom