Migrated DNS, Printer issues?

[TheHyperTechie]

Hi All,

 

I recently moved our DNS to our router/firewall via our ISP, but we're still using Active Directory with a domain controller, which we plan to decommission soon. The DNS migration and DHCP updates all went smoothly, and every device on our network now uses the new DNS address, which is great! However, there's an issue with our AD/domain-joined devices connecting to printers hosted on our domain controller using print management. Both the client devices and the printers have the new DNS address, but they're not connecting properly.

 

When I temporarily used the old DNS address on the printers, it worked. I've updated the DNS address on the print server, but I'm not sure what else might be causing this issue. Am I overlooking something obvious?

 

Thanks!

[Davit2005]

AD relies on DNS heavily otherwise you might get strange issues. Best use forwarders on your AD DNS to the routers then nearer the time to change shorten the dhcp lease and swap over the DNS for the clients then.

 

Alternatively you could add the AD DNS as the DNS server the router resolves against then point AD DNS to external but it will get messy if not careful.

Edited October 30, 2023 by Davit2005

[chaplic]

Unless your DNS service specifically supports the need of Active Directory (and Id suspect it doesn't) then this is not going to work and printers is the least of your problems.

 

It is not necessary to use Microsoft DNS to run windows clients but I'd guess 99% of companies do. clients>MS DNS> RouterDNS>Internet could be a route.

[TheHyperTechie]

Hi,

 

Thanks for your reply. I did setup some forwarders on the local DNS server to point to our new address but obviously it still seemed to have issues.

 

I think for now, I will revert the DNS address back to the original in our DHCP scope and wait until we have moved all devices away from our domain and go from there.