Tag Info

Hot answers tagged

84

Once upon a time I had an opportunity to decide on a naming scheme. So I went round and asked my developers, who after all were the people who had to work with these names on a day-to-day basis, whether they preferred functional names (that is, names which represent, in some encoded form, the purpose of the machine) or mnemonic names (that is, names drawn ...


80

This largely comes down to whether your servers are pets or livestock. Pets get individual names. They're distinct from each other, and we care about those differences. When one gets sick, we usually try to nurse it back to health. Traditionally, servers have been pets. Livestock get numbers. They're mostly identical, and what differences there are, we ...


60

Do not use an invented TLD. If ICANN were to delegate it, you would be in big trouble. Same thing if you merge with another organization which happens to use the same dummy TLD. That's why globally unique domain names are preferred. The standard, RFC 2606 reserves names for examples, documentation, testing, but nothing for general use, and for good reasons: ...


44

The short answer is to your specific question of listing CNAMEs is that you can't without permission to do zone transfers (see How to list all CNAME records for a given domain?). That said, you can use dig to list the other records by doing: dig +nocmd yourdomain.com any +multiline +noall +answer


28

Try: dig -tAXFR mycompany.com This may or may not work. Many DNS servers will deny a DNS Zone Transfer like this. For more information, see How the AXFR protocol works


28

Use a subdomain of your company's registered domain for internal machines whose names you do not want available on the Internet. (Then, of course, only host those names on your internal DNS servers.) Here are some examples for the fictitious Example Corporation. Internet-facing servers: www.example.com mail.example.com dns1.example.com Internal ...


22

Do not use .local. Do not use .anythingyoujustmadeup either. Don't even use the reserved TLDs. Use a real domain or sub domain and just don't allow it to be visible to the outside world. The main reason for this is when you work for company A that uses .local (or example.com) and they buy company B that also uses .local (or example.com). Not a lot of fun ...


21

You really would be better off setting up a pair of nameservers if you can. I've never really seen a situation where you couldn't replace a cumbersome hosts file situation with a couple of DNS servers (Really, they are easy to setup and run). However, to answer your question, you can use something like either puppet or cfengine to keep these in sync. ...


18

There's another advantage of using an internal subdomain: cleverly using search suffixes and only hostnames instead of FQDN, you can build configuration files that work both in development, QA and production. For example, you always use "database = dbserv1" in your configuration file. On the development server, you set the search suffix to ...


17

Keep track of the time you spend updating /etc/hosts files, deploying the changes and keeping them in sync.


16

This has been covered here before... My recommendation is a combination of functional names and mnemonic names... If you're writing an application and it needs to address ccts-logserver1, use that name throughout, but make that a CNAME or an alias. The real hostname can be whatever you want: a fruit or vegetable, greek mythology or Seinfeld character... ...


15

For the record: you can also do this with BIND, but it's a litte more involved. You need to configure bind as the authoritative nameserver for the specific resource record you want to override. For example, if you wanted to redirect gamestats2.gs.nintendowifi.net to your own host, you would need this in your named.conf: zone ...


15

ipconfig /all will show you the location of your DHCP server. There's a line item that says "DHCP Server" If you want to use ninja skills, you can use the command ipconfig /all | find /i "DHCP Server"


15

Woah. Why would you even do that? I really don't understand. Inventing tld's is wrong on extremely many levels. You could just put all the computers in your company's domain (foo.yourcompany.org) or, if you are in a playful mood, use a special dubdomain like (foo.lan.yourcompany.org). Are you doing it because you think, that typing multiple subdomain is ...


14

The first thing you should know is that Active Directory and DNS are so intertwined that they're almost one. For all intents and purposes, you should forget the idea of having an Active Directory domain which doesn't have a primary DNS server for Windows clients. I won't say it's "impossible", but I will strongly advise you that it's a path with only pain. ...


12

When you outsource to another company, especially one that is doing it for free, you might consider what they are getting out of it. Google is in the information business, and they are getting another aspect of your (or your user's) traffic pattern. If I were at a university that used google's name service, I would be raising privacy issues pretty darned ...


12

First and foremost, make sure you own the domain.tld you plan on using (mit.edu). Even if this never connects to the internet, that's not the point. There are huge benefits to having a hierarchy of dns that at least somewhat matches the org. I've only seen this done when there is someone/people to manage that department in terms of IT support. This is in ...


11

In today's world, I do not recommend creating new zones with arbitrary top level domains, as these might make it into "official dns" at any point in time. I personally would favor the subdomain delegation scenario, as it seems to be fitting what you try to do. (Consolidate but give control to engineering) Maybe you can even find a web-front-end for MS DNS ...


11

Don't use .local. Especially if you've got any Apple clients.


11

It is generally considered a good practice to serve localhost, 0.0.127.in-addr.arpa and the RFC-1918 reverse zones on your internal DNS system to prevent sending queries from them out to the internet. It saves time (you get replies for those queries quickly), bandwidth (no requests leaving your network for zones that shouldn't exist), and relieves the load ...


11

There isn't really a "supported" method of recovering passwords in Windows Server 2003. If there's no critical data on the machine or in the newly-created domain it would be easiest just to level the box and start over. Edit: I don't mean to sound trite, but if you just setup the machine leveling it and starting over isn't going to be too hard. Why go ...


9

Well, if it's a linked set of virtual servers, obviously it's .matrix.


9

Do not use an invented TLD. If ICANN were to delegate it, you would be in big trouble. Same thing if you merge with another organization which happens to use the same dummy TLD. That's why globally unique domain names are preferred. The standard, RFC 2606 reserves names for examples, documentation, testing, but nothing for general use, and for good reasons: ...


8

You can also use host DNS lookup utility with -l switch: host -l domain.com Of course you need DNS zone transfer rights for this to work.


8

How about creating a DNS entry for "expenses.mycompany.com" that sends to a webserver with a redirect rule of expenses.mycompany.com -> mycompany.com/expenses? As long as clients have a DNS suffix of "mycompany.com" set they will convert "expenses" into expenses.mycompany.com, and hit that webserver. It means a few extra DNS entries, and some virtual hosts ...


8

+1 for MikeyB's answer. As an extension, how would you convince a corporation that they need anything else? (How to justify the need for a new rack or switch, etc.?) Compare the alternatives, and provide a cost/benefit analysis for each option. It really doesn't take that long to setup a reliable DNS solution. Beyond the test necessary to update ...


7

You've configured the client to lookup against your internal DNS for its primary, and an external DNS server as a secondary? You have a race condition; if the internal DNS happens to be too slow to respond, then the client gets an unusable response from the public DNS server. ping is using the cached response from the lookup against the external DNS ...


7

While not exactly what you're after, why not use a URL shortener on your internal servers? Then you can setup a virtual host on your server that hosts the URL shortener, and do something like: http://go/expenses http://go/tracker The URL shortener would rewrite that to your necessary internal URL. There is an example of a .NET URL Shortener here. The ...


7

There's actually a lot going on here, but much of it may be irrelevant to your situation. First, using DNS master/slave relationships allows easy replication across heterogeneous server types. I know I've synced a primary OS X Server (BIND?) server with Windows DNS. This also allows you to specify that a secondary DNS system may retrieve from different ...


7

The master/slave configuration (also known as “zone transfers,” AXFR or IXFR) is the standard configuration used by most DNS servers. For that reason alone, it’s what I’d recommend, even though it’s complicated. Although I recommend it for interoperability, and because it’s easy for other admins to understand, that doesn’t mean it’s technically the best way ...



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