From: Jens Knoell <jens@surefoot.com>
To: campbell@accelinc.com
Cc: linux-admin@vger.kernel.org
Subject: Re: DNS question
Date: Tue, 10 May 2005 09:37:24 -0600 [thread overview]
Message-ID: <200505100937.24885.jens@surefoot.com> (raw)
In-Reply-To: <20050510152302.GB24684@helium.inexs.com>
Forgot...
On Tuesday 10 May 2005 09:23, Chuck Campbell <CC> wrote:
> On Tue, May 10, 2005 at 09:14:50AM -0600, Jens Knoell wrote:
> > That provider is probably giving you a load of BS. I've seen providers
> > who actually "need" the DNS resolvers on their servers, but in each case
> > it's just a matter of total utter BS on their side. The only thing you
> > need to do is point the www entry to the providers webserver.
>
> Who (in my current situation) needs to point the www entry? I assume you
> mean my current provider needs to change something to point web resolution
> to a different address? What (so I can speak intelligently with them)
> needs to be changed?
In the current situation, you would have to. Either with a CNAME entry, or
with an A entry.
> > Alternatively if you'd rather play along and transfer the domains
> > nameservice to them, you can still add an MX entry pointing elsewhere if
> > they don't provide email services.
>
> I can't add an MX for email, the (new) provider would have to do that,
> correct?
If you have the authority to make DNS changes to your domain, you could do
that.
J
next prev parent reply other threads:[~2005-05-10 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 15:01 DNS question Chuck Campbell
2005-05-10 15:14 ` Jens Knoell
2005-05-10 15:23 ` Chuck Campbell
2005-05-10 15:33 ` Jens Knoell
2005-05-10 15:37 ` Jens Knoell [this message]
2005-05-11 1:31 ` David Ziggy Lubowa
2005-05-10 15:20 ` Nick Mitchell
2005-05-10 15:26 ` Chuck Campbell
2005-05-10 15:39 ` Nick Mitchell
2005-05-10 15:24 ` Richard Nairn
2005-05-11 7:25 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200505100937.24885.jens@surefoot.com \
--to=jens@surefoot.com \
--cc=campbell@accelinc.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).