The Church of Jesus Christ of Latter-day Saints

For Manual IP/Auto DNS, a half-way solution would be to use the router's IP address as the DNS address of your static IP configured device. I know it works on consumer routers. I've never tried it on a Meraki MX64, behind a managed domain.

russellhltn wrote:Unless I'm missing something, once you configure Windows for a static IP, you're forced to use a static DNS IP as well.

Yes, if you don't set a static IP, you have to use DHCP.
If you don't use DHCP, you must set the IP address, Subnet mask, Default gateway, and DNS servers manually.

I’m worried about it being a 3 day weekend and getting calls from Ward Clerks this Sunday if they are unable to get online as I will be out of town. :| Have you configured anything to have a static IP address? If not, then you likely have nothing to worry about. The only static IP in my stake is a ...

I'm an STS in my stake. I just got the email about changing the DNS for static IP devices, a few minutes ago.

I've been able to use the PowerPoint slides with vMix. Thank You!!!!!!!!!!!!!

Good to know, thank you.

I’m sure we will be using our AudioTechs until such time as someone gets fined, or someone’s cell phone conversation hijacks audio in the chapel. No sooner.

I would like a copy, please

WA6IJD wrote:Instead of filtering by topic or subject, why not use a table and add domains to it. Seems the way to go. What do other people think?

Thank You

That would be known as ‘whitelisting’. I’ve already been shot down over the idea.

Good point. All the more reason to set the filter level to at least moderate.