New answers tagged

0

This question is a little old, but this MSFT guide for creating a new "Domain Controller Authentication (Kerberos)" certificate template (to support Windows Hello) steps you nicely through creating a new template and superseding the previous DC certificate templates. (Skip the rest of the document when it starts discussing Enrollment Certificates.) ...


0

Without seeing your nginx configuration, the following is a best guess. location ~ "^/images/(?<year>[0-9]{4})/(?<month>[0-9]{2})/(?<day>[0-9]{2})/(?<filename>.+\.(jpg|png))$" { return 301 https://media.originsite.com/foldder/$year/$month/$day/$filename; } We capture specific parts of the URL path to variables, and then ...


0

For anyone else happening upon this question, in my case the cause was the removal of a DFS name server without transferring resolution. My namespace was domain based, so it still existed as a domain object, but DNS servers are not used to resolve it, instead dedicated DFS namespace servers need to be defined. So I installed the DFS console on a remaining ...


2

This automated config by Certbot isn't very suitable for your needs. Change HTTP to HTTPS redirection block to this one: server { listen 80; listen [::]:80; server .domain.com; return 301 https://$http_host$request_uri; } Make the following changes to your HTTPS block: use server .domain.com; instead of server domain.com; (this ...


0

Windows Event Forwarding will meet basic needs. https://docs.microsoft.com/en-us/windows/security/threat-protection/use-windows-event-forwarding-to-assist-in-intrusion-detection


1

They can have the same samAccountName. The User Principal Name (UPN) must be unique forest-wide. So you can't have multiple jsmith@domain.com, but you can have jsmith@sub1.domain.com and jsmith@sub2.domain.com.


0

Your zone-file donsen't has the correct record for www.sudia.com. Add this to your zone. E.g. by changing this file /var/named/fwd.sudia.com.db or via nsupdate: Method 1 (Update file /var/named/fwd.sudia.com.db, don't forget to update serial): @ IN A 136.243.197.164 Method 2 (nsupdate) e.g.: [root@ns1 ~]# nsupdate -k /etc/rndc.key > server ...


1

Yes, the IP can change (perhaps a CNAME record would be better?). Generally it will only change due to a platform health issue and not something you can inadvertently do within the portal. Not even a scale up will cause it.


0

I solved the problem, and wanted to clarify a few points: (1) digijay, I own both domain names, and have access to them on the domain host. The domain host is separate from the hosting/email server, that is why we are needing to use this redirect to stall the production of an email migration. (2) Michael Hampton, thank you for the tip. I was able to enable ...


0

As a workaround you can try to add index.html to your upstream request when your site get a / request: location / { rewrite ^/$ /index.html break; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-...


0

First, query the the root name servers: dig ns . Then, query one of the root name servers for the name servers of the TLD (for example .net): dig @m.root-servers.net. ns net. (Or you can skip the first step and just query dig ns net. Now, query one of these name servers for a domain name with the name servers you want: dig @m.gtld-servers.net. ns speedy.net. ...


1

You must not change NS records, you must add A record Name TTL Type Address you-domain 3600 A 111.222.333.444 For any hosting you can find examples of how to do this, for example: https://support.us.ovhcloud.com/hc/en-us/articles/360012042099-How-to-Connect-Your-VPS-to-Your-Domain-Name


1

In order to point the domain you have purchased to your VPS you need to create an A record pointing to your VPS's IP. There is no need to modify your nameserver records. According to the DNS specification, the authoritative nameservers are given by name, not IP. So that is why that error pops up. And unless you have very complex DNS needs, you shouldn't host ...


1

What you are looking for is the Domain Name System (DNS). When you purchase a domain through the usual provides (OVH, Hetzner, GoDaddy, ...) they will provide you with their DNS servers for free. So, in general: once you purchased a domain, you can just configure the DNS records through their web portal. Their documentation usually should contain details ...


Top 50 recent answers are included