The I and C were transposed........ Wow........
Typos drive me insane! Glad you found it before you suffered a catastrophe.
@JasGot lots f issues around here as well. Lake Erie erosion worst I've seen and Lake Ontario flooding last 2 years
It's bad, have you suffered any loss personally? Or just local stuff? The public access parking area (about 1000 ft away) fell in about 4 weeks ago.....
Did you break out Wireshark yet to check each network segment for where it's failing to relay to?
Do devices get an address on the same network as the dhcp server?
I haven't because it is only some iphones. Like, 4 out of 100 iphones don't get dhcp addresses. every other brand device works fine.
I don't know what you mean by lost beach?
Our Unsalted Ocean has been behaving like an actual ocean this year.
Pretty sure I figured it out.
The domain in question had 2 MX records,
O365 has the higher priority, and there have never been any complaints of missing messages.
I'm assuming this spam made it to google, because I know some spammers specifically use the secondary, etc MX records in hopes of bypassing spam filters. So I'm assuming that's what was happening here.
Now that said - I did see a single Twitter email in the G Suite - so I'm guessing there was glitch at O365 once, and Twitter hit it and tried the secondary...
Often, spammers will send mail to a higher MX record on purpose. There are many reason they do this, Less protected routes to a gullible user is one of them.
Could be the timeout setting is quite long. 2 weeks used to be a common setting, so it could take some time if you didn't change that setting beforehand.
Excellent point. For years we have been making it a point to set the timeout to 900 seconds as soon as we new there was going to be a change in the future. Not all name servers honor it, but is sure has had a positive impact to the overall propagation time.
interesting - if there are open ports on the sonicwall - you could just use one of them as the interface, and have the switch be an untagged port for that specific VLAN, then the sonicwall won't care, or know it's a VLAN.
I can do that. I am not certain it is the sonicwall failing to deliver the DHCP though. The sonicwall connection monitor never shows a connection from the device (iphone). At this point, any changes I make to the UniFi gear has an impact. Nothing has fixed it, but it has an impact.
Then I read about Unifi Switch issues and version 4.0.69 here but even when I go back to 4.0.66, my problems still remain. I think Ubiquiti is experience a major problem with DHCP and VLAN scenarios and they have not figured it out yet.
Which we did.
Did it solve the issue?
Another thing to note is that the Unifi Switches with a Unifi Server Controller give a lot of troubles with VLAN configuration (I am not talking about EdgeSwitches but the Unifi Swtiches).
When you get a few minutes, can you elaborate? This sounds like we are experiencing. DHCP issues?
I just updated the firmware on all of the switches and found one loop. I'm hopeful things are better tomorrow.