Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
15
Newest
 Critic
Impact
~5k people reached

May
6
comment DNS not resolving 3rd level sub domain
on what level do you want your change to happen? if you are only interested in the subdomain.example.com available to yourself (e.g. for testing), then /etc/hosts is a good solution (but see my answer). But if you want others to be able to access subdomain you need a separate entry on the official DNS server for your domain.
May
6
answered DNS not resolving 3rd level sub domain
May
6
comment DNS not resolving 3rd level sub domain
@Mechromancer: nslookup and dig andthe like are tools to query DNS-servers; since you don't use a DNS-server but /etc/hosts, you cannot use these tools; but running ping subdomain.sitename.domain.com on that machine should give you a clue whether things work as expected.
May
6
comment DNS not resolving 3rd level sub domain
@wurtel; /etc/hosts is DNS just fine; it is just not a server-based solution and only works locally (so the new subdomain name won't get known to machines that lack this change to /etc/hosts)
May
6
comment OpenLDAP will not start - Starting OpenLDAP: slapdrm: cannot remove `/var/lib/ldap/alock'
@alphamikevictor, the manpage says -f: ignore nonexistent files and arguments, never prompt; so it's really a "force success" rather than "force remove"
May
6
comment OpenLDAP will not start - Starting OpenLDAP: slapdrm: cannot remove `/var/lib/ldap/alock'
which version of Debian and OpenLDAP are you using (apt-cache show slapd | egrep "^Version:")
May
6
answered OpenLDAP will not start - Starting OpenLDAP: slapdrm: cannot remove `/var/lib/ldap/alock'
Apr
27
awarded  Critic
Apr
27
accepted migrate to new root-dn
Apr
27
awarded  Curious
Apr
1
comment migrate to new root-dn
i updated my question to answer your remarks (i'm using ldap for user auth; root-dn is hardcoded in all clients)
Apr
1
revised migrate to new root-dn
additional info: ldap is used for user-auth; root-dn is hardcoded in the clients
Mar
31
revised migrate to new root-dn
edited title
Mar
31
asked migrate to new root-dn
Feb
27
awarded  Quorum
Nov
29
awarded  Caucus
Sep
25
awarded  Popular Question
Dec
12
comment automatic MX entries for (almost) all hosts within a domain
the thing is, that while i understand the reasons why wildcards don't apply here (thanks for clarifying it, anyhow), it doesn't help answering my question. worse: most of the domains i administer have the same problem... so i figure that others might have this problem as well and there ought to be a simple solution for it
Dec
12
comment automatic MX entries for (almost) all hosts within a domain
RFCs have a very clear distinction between should and must (and while technically nobody ever *enforces an RFC, they still use these words and insist that they are different). in any case, this aspect of your answer isn't really related to my question anyhow... (so sorry for being anal)
Dec
12
comment Nginx welcome page returns
what do you mean by "it appears to happen every time... if I reboot the instance, it does not cause the overwriting". does it happen every time or does it not happen on reboot?