DNS not updating over multiple vlans

Since implementing multiple VLans we have found that DNS does not update properly. As soon as I put a copy of the DC's into a non-Vlan environment DNS updates straight away.

I am hoping that this is a simple case of a wrong setting on the switches? The switch model is HP J4819A ProCurve Switch 5308xl.   Version: E.10.04, ROM E.05.04
sol1973Asked:
Who is Participating?
 
sol1973Connect With a Mentor Author Commented:
This problem now resolved. The solution was to add IP helpers to the switches and after 24 hours the dns entries came flooding in. Thanks to Chris for helping. It was indeed routing and taking that on board helped some way to us finding the ip helpers as the issue.
0
 
Chris DentPowerShell DeveloperCommented:

What do you mean by doesn't update properly? Doesn't update at all?

Any firewalling between VLANs?

Chris
0
 
sol1973Author Commented:
Thank you for the quick response, its much appreciated.

There are a few records in DNS but they are by no means up to date, hundreds of missing entries. It would appear that since the vlans were introduced, no updates have happened. There are no firewalls between them.

Sol
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
Chris DentConnect With a Mentor PowerShell DeveloperCommented:

Does DHCP update DNS on the clients behalf? If so, does DHCP run on the same system?

Does the lack of update include entries from systems with static addressing (servers and such)? If so, are they posting DNSAPI errors in the Event Log?

I would suspect that this failure is more likely to be caused by failing network paths (routing) than any particular VLAN setting.

Chris
0
 
sol1973Author Commented:
Dhcp is fully utilised for all PCs and laptops. everything else has static addressing. Yes DHCP is on the same server.
The DNS api errors apply only to three servers that are running 2003 - all other servers are running 2000. I agree that routing seems to be the issue, which is why I am looking to a setting on the switches that host the VLans.
This conclusion was, as previously mentioned, reached due to taking a complete copy of the DCs and putting them in an identical situation but with out VLans. All works perfectly when in that situation.

Sol
0
 
sol1973Author Commented:
Do you have any other ideas Chris? I think I am now looking for specialized assistance with the switches, possibly one to fire back to HP. Unless of course there are any HP experts in the exchange?

Sol
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.