Hot answers tagged

28

This is not going to be an IT tech answer, but hopefully useful nonetheless. Speaking from years of experience, you will not be able to convince your boss to do everything differently. The primary reason for this is that he is the boss while you are just his subordinate. You are in the wrong position to push fundamental changes. Can you live with the ...


23

Yes, the hostname really is case-insensitive, as specified in RFC 3986 § 3.2.2, because hostnames in general are case-insensitive in the DNS. This RFC also gives recommendations on how to avoid the problems you mentioned: Although host is case-insensitive, producers and normalizers should use lowercase for registered names and hexadecimal addresses ...


18

You need to focus on how it helps them, not on what you "want." we have coped for years without an issue And you don't want to start now! There have been a number of data breaches lately, including Target, Home Depot, and more. Home Depot spent $43,000,000 on its data breach in only one quarter. Target paid $10,000,000 in a settlement. An ...


11

If you can safely limit the supported clients of your service to systems supporting Server Name Indication, having only one IP address should be sufficient. See this article for a list of supported clients.


10

The first MX means that the IP addresses in the MX record(s) for the domain you're actually attaching the SPF record to should be accepted as valid. The second one means that IP addresses in the MX record(s) for the domain mail.mydomain.com should be accepted as valid. If this SPF record is for the domain mail.mydomain.com, then the second one is redundant. ...


10

Nope. The "Hide extensions for known file types" is a preference that you can set via Group Policy. And if it's only a preference, then the user can undo it. Basically, as long as the user has write/modify access to the file, they can rename it to whatever they wish. It's not a Group Policy thing, but an NTFS thing. The only way to really prevent a user from ...


9

The answer to "how PCI compliant" you are is Not Very (edited based on a comment). Your CC terminals might be okay if the tills themselves don't hold any data. Now to pick apart the "not worth it" list... We have coped for years without an issue This may well be true, but the problem is perception. This will be your biggest hurdle. Employees can be ...


7

Here are my thoughts: Management very rarely understands technology and its place in business. Most times, management has misconceptions about what technology is and how it affects business. Yes, it's true that mismanagement of technology often leads to wasteful spending, but proper management increases productivity dramatically. Waste generally happens ...


7

When you connect by IP address the SSH connection goes directly to your server but if you use the domain name it goes through Cloudflare defenses. My suggestion would be to either use direct.pollnote.com (I think CloudFlare creates it automaticaly but people often remove it) or add your own alias like ssh.pollnote.com and disable CloudFlare protection on it. ...


7

That COMPANY_NT is the NetBIOS name for your domain, which was configured when it was set up - it doesn't actually have any relation to NT legacy cruft, that's just the name that someone picked. Your domain will need to always have a NetBIOS name - you can't get rid of that.. but if you want, you can change the name with rendom so that it no longer says ...


6

You will likely run into the same problem with CNAME records. Your best long-term solution is to continue using NetSol as a registrar, but move your DNS services elsewhere, to somewhere without arbitrary limits like your current provider has. I'm a big proponent of AWS Route 53. It's easy to use, very reliable, cheap, easy to automate things via their API, ...


5

This is not possible at all. In order to grant permissions to domain users on a computer (including adding them to local groups), the computer needs to be joined to the domain.


5

I'm assuming you're meaning you have something of the form example.com and mobile.example.com ? There is nothing inherently wrong with these being served from different IPs for load balancing or other purposes. It's not going to be an intelligent distribution of traffic based on actual load - but if it meets your needs : then as a cheap and easy solution I ...


5

While there are tools that can rename a domain, it can be a complicated process. You have a couple options. 1. You can add an alternate UPN so that @domain.com is valid. 2. You can migrate to a new domain. I'd try the upn route first


5

There's no good reliable starting point for a WHOIS client. It's more or less an "illusion" that you can use whois without also specifying the whois server to query. I'll refer to my answer here http://serverfault.com/a/615848/183318 for the available means of finding the proper WHOIS server for a TLD. Only the method of querying IANA (WHOIS or http) is ...


5

You should not install SQL Server on your Domain Controller. Yes Join the new server to the same domain as the clients. Why would you do otherwise?


5

This is probably nothing to worry about - this will occur when the original local profile folder doesn't unload or is otherwise corrupted. Basically, the first profile will be C:\Users\username If there's an issue with the username folder, it'll append the domain name: C:\Users\username.domain If there's an issue with the username.domain folder, it'll ...


5

There is a wealth of public information on how the DC Locator process works. Essentially it performs a series of DNS lookups and LDAP pings, and also attempts to stratify the results by selecting the closest domain controller. It's unusual for Windows DC Locator to continue to use a failed domain controller, unless the domain controller is passing the ...


4

Dealing with the WHOIS protocol is quite messy. At least for human digestion it's typically most practical to use a client that has been pre-configured in such a way that it can present a mostly consistent interface to the user. Doing so means having a very extensive configuration with not only information about which servers to use for particular queries ...


4

You have set your DocumentRoot to /var/www/internet/movil/ but you point the directory to /. Change it to say <Directory /var/www/internet/movil> Also mind to remove the trailing slashes in the paths. The entire vhost would look like this: <VirtualHost *:80> ServerAdmin webmaster@mores.es ServerName m.mores.es DocumentRoot ...


4

An HTTP request contains a header field named Host which contains the name of the virtual host that should answer. Apache reads this and maps the request to the appropriate vhost. http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol, specifically the Host: header...


4

There is no mechanism to indicate "priority" of authoritative DNS servers. You could theoretically swap out the nameserver records for your domain at the registrar, but due to various layers of DNS caching, that's not going to be an instantaneous change.


4

The DC/DNS server should use it's own ip address for primary DNS and should use 127.0.0.1 for secondary DNS (assuming a single DC/DNS server). The clients should use the DC/DNS server for DNS. You can configure the DNS server properties to use the Forwarders of your choice to resolve external DNS names.


4

No, there's nothing wrong with that. The primary advantage to that is that it bypasses the default location for new computers. That advantage (or another that I haven't thought of) may or may not be compelling to you, depending on what policies you have in place in various OUs.


4

You can do this by putting a reverse proxy before your servers and direct to the proper one when request for particular site is sent to that proxy. You can use mod_proxy of Apache: http://httpd.apache.org/docs/2.2/mod/mod_proxy.html Or you can try something more lightweight like ngnix.


4

This happens on shared hosting when someone tries to access a site with https and their site doesn't have a certificate configured. Someone goes to https://anothersite.com and https://yoursite.com loads instead because it's your certificate. BTW, your certificate is expired.


4

I don't think switching record types really addresses the core problem which is a limit to the number of records that your DNS service provider allows. Disregarding the question of whether using the use of CNAME records would be appropriate in your scenario, presumably such a switch would just mean that you would hit the same limit but now instead for how ...


3

The straightforward answer is no. There is no definitive way that I know of to update the Kerberos access token without logoff/logon or reboot. The SID of the new group needs to be added to the token and is only done at those events. You could try using klist purge as many articles on the web will suggest, but my efforts to attempt this did not work.


3

From how I read that, I think you may be confusing the delegation information administered through the registrar with some DNS hosting service provided by the same company. If you are switching to an entirely different set of nameservers it is important that you update the delegation information, not the data inside your zone hosted at their DNS service. ...


3

Open EAC (Exchange Admin Center). Select Mail Flow on the Left Panel Menu. Select Accepted Domains from the Top Menu. Click the + icon. Enter a name in Name, enter the fqdn of the subdomain in Accepted Domain. ("subdomain.example.com"). Select Authoritative domain. Select Save Don't forget to add/update an MX record for the subdomain. To confirm the ...



Only top voted, non community-wiki answers of a minimum length are eligible