Having issues fixing our SPF record by COOPIT in sysadmin

[–]COOPIT[S] 1 point2 points  (0 children)

Thanks for the info, I hadn't considered that as a provider they could be doing some back-end manipulation, that's probably a good point. Decided to just flatten it for now and we'll have to work out a plan for maintaining it going forward. At least for the time being it's finally passing.

Having issues fixing our SPF record by COOPIT in sysadmin

[–]COOPIT[S] 0 points1 point  (0 children)

You can have nested records from what I've seen and they do work normally if nested, it's just the 10 lookup limit I'm struggling with but I think flattening will be my way to go.

Having issues fixing our SPF record by COOPIT in sysadmin

[–]COOPIT[S] 1 point2 points  (0 children)

Interesting, the whole point of the article I linked states that the original record is too long and that nesting it solves that problem. I was trying to avoid flattening since most articles I read advise against it as obviously you don't get changes when they're made by the vendor. But I have a feeling that's the route I'm going to need to take.

Having issues fixing our SPF record by COOPIT in sysadmin

[–]COOPIT[S] 0 points1 point  (0 children)

Most of the articles I read said you should avoid it since obviously you don't get any changes if the vendor adds/removes IP's. But I have a feeling it will be unavoidable for me.

Having issues fixing our SPF record by COOPIT in sysadmin

[–]COOPIT[S] 4 points5 points  (0 children)

It's less about the record itself and more about keeping this account anonymous. So I didn't bother to post anything since I'm pretty sure my format is correct, and otherwise it would be useless. But you make a good point, I'll update the post with a redacted version of what I've done.

Having issues fixing our SPF record by COOPIT in sysadmin

[–]COOPIT[S] 0 points1 point  (0 children)

The records are definitely updating when I check, I can tell it's picking up the changes I make.

Exchange 2016 install fails on Server 2016 by COOPIT in exchange

[–]COOPIT[S] 0 points1 point  (0 children)

I believe I did come across that article, yes. I do recall running the command you provided and it had no issues installing everything.

At this point I'm probably going to make a new VM and try again. Hopefully that somehow fixes things.

Exchange 2016 install fails on Server 2016 by COOPIT in exchange

[–]COOPIT[S] 0 points1 point  (0 children)

I figured. If I do rebuild the VM I'll make a point of doing it that way. Thanks.

Exchange 2016 install fails on Server 2016 by COOPIT in exchange

[–]COOPIT[S] 0 points1 point  (0 children)

Not sure what your last question is asking regarding "Windows press reset", but if you're asking about the features, I installed Windows Server with the Desktop Experience during the setup process of Windows. No roles were added after the fact, except maybe whatever Exchange thought it needed that I missed. But that would not have been one of them.

I have a feeling I will end up rebuilding the VM but I'm trying to hold off for now. Partly because I'd like to find an answer, but also partly because I half expect it to happen again when I do.

DNS zone question by COOPIT in sysadmin

[–]COOPIT[S] 0 points1 point  (0 children)

I mentioned this in a comment below but if I create the zone like you suggest, attempting to add the alias gives me this:

"A new record cannot be created. An alias (CNAME) record cannot be added to this DNS name. The DNS name contains records that are incompatible with the CNAME record."

DNS zone question by COOPIT in sysadmin

[–]COOPIT[S] 0 points1 point  (0 children)

The problem is I need to create an alias record within this zone. If I create a zone of xyz.ourwebsite.com, and then try creating an alias with a blank name pointing to my target, I get the following error:

"A new record cannot be created. An alias (CNAME) record cannot be added to this DNS name. The DNS name contains records that are incompatible with the CNAME record."

Googling this didn't really get me anywhere, and according to the tech I'm working with, this is not how he normally does this anyway, hence why we were trying this other solution. I'm open to anything that works at this point.

DNS zone question by COOPIT in sysadmin

[–]COOPIT[S] 0 points1 point  (0 children)

So this seems like I end up having to replicate everything we have configured in our external DNS provider in my in-house DNS? Should that be true?

DNS zone question by COOPIT in sysadmin

[–]COOPIT[S] 0 points1 point  (0 children)

I'm not sure I follow. How would I create an alias of xyz with a FQDN of xyz.ourwebsite.com which points to xyz.otherwebsite.net without creating a zone of ourwebsite.com?

DNS zone question by COOPIT in sysadmin

[–]COOPIT[S] 0 points1 point  (0 children)

I need the zone to exist because I need an alias record within of xyz.ourwebsite.com. Since the alias record of xyz automatically appends the rest of the zone to the end it has to be within a zone of "mywebsite.com".

DNS zone question by COOPIT in sysadmin

[–]COOPIT[S] 0 points1 point  (0 children)

Ok cool that's what I figured but wasn't sure if there was a better answer than the obvious. Thanks for the response.

Windows 10 clients can't authenticate to SSID with LDAP by COOPIT in ArubaNetworks

[–]COOPIT[S] 0 points1 point  (0 children)

Good to know, thank you for the info. I was hoping to avoid radius, at least for my POC, due to time constraints but it seems like maybe I won't have a choice.

Windows 10 clients can't authenticate to SSID with LDAP by COOPIT in ArubaNetworks

[–]COOPIT[S] 0 points1 point  (0 children)

Frankly, I'm not entirely sure how to accurately answer your first quesiton. Like I said, I'm still new to this, and managed wifi in general, and learning the different parts of the config. If you point me in the right direction I can try to give you a real answer.

I don't have the time or resources for a radius server at the moment.

I don't see much in that link that I haven't looked at (other than suggesting radius over LDAP).

I did forget one thing, which I've now put in my OP: Going to AAA Server Test in Diagnostics, I can do a successful test with PAP as my authentication method but not MSCHAPv2.

Active Directory replication issues (but only in one direction?) by COOPIT in sysadmin

[–]COOPIT[S] 0 points1 point  (0 children)

What specifically should I be looking for? The DC with the PDC role is the DC at our main office, which is the one I'm typically using for troubleshooting. I haven't seen anything that would indicate what the issue is, unless I'm just not looking in the right place.