single entry to hosted service
Dan Letkeman
I need to add an entry in our dns servers for a hosted service we
purchased. Do I just add a master zone and a single entry? Or is
there a better way to add a single entry to forward to a remote
server?
Thanks,
Dan.
Kevin Darcy
uses a name that's already populated in the Internet-facing DNS, why do
you need any special DNS configuration at all? Why can't you resolve
this like you resolve any other Internet name?
Assuming that you _do_ in fact need some special configuration, for some
reason, the zone types for (non-root) zones in BIND are: master, slave,
forward, and stub. Each of them has benefits and disadvantages, but I'll
defer that discussion until and unless it's determined that you need a
special DNS configuration at all...
- Kevin
Dan Letkeman
accounting service from a company that has asked us to put a dns entry
into our dns servers so that our internal machines only can resolve
there hosted service via dns. I guess they don't want to populate
there isp's dns servers with all of the dns entries for all of there
customers....
So with my limited knowledge of bind (using webmin to configure it) I
need to make an entry like this:
222.222.222.222 A hosted.accounting.com
In our internal DNS servers.
I don't have any "internet side" dns, just internal. I'm just a bit
unsure on what the best way to do this is, and I don't want to have to
append everyone's hosts file on there workstations. I have many
master zones for our internal systems, and I have created all of the
nessesary records. I have setup slave servers, and the whole bit.
So i'm wondering do I need to setup a master zone, and put in the
222.222.222.222 A hosted.accounting.com as an A record, and then have
the zone forward everything else? Reason being is because our users
will still need to access other sites from the accounting company's
domain.
Thanks,
Dan.
> _______________________________________________
> bind-users mailing list
> bind-...@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
Kevin Darcy
IP address, and have your clients use that name?
It would pretty ridiculous if a) the server code of the app actually
cares what name the client uses for accessing it, b) they mandate that
their (<-- note spelling of word) customers use a name in *the*vendor's*
domain to access the app, c) had a different name for each customer, but
d) couldn't be bothered adding the name for each customer to their own
domain. Essentially, they'd be forcing all of their customers to kludge
their DNS (or to use something even less manageable, like WINS or local
hosts-file entries).
- Kevin
Jeff Lightner
Your other zone files are still in place so you shouldn't need to forward anything else because you're saying this is internal to your network. If a user is sitting at his desk and types:
InternalSite1.excample.com to get to one of your internal websites then goes to hosted.accounting.com then tries to go to InternalSite2.example.com then their current stub server setting should use the same resolution setting (e.g. /etc/resolv.conf on UNIX/Linux) to get to InternalSite2 as it used to get to InternalSite1.
The above assumes all your workstations etc... always ask your DNS server for any lookup first which is the normal way of doing things.
222.222.222.222 A hosted.accounting.com
Thanks,
Dan.
Proud partner. Susan G. Komen for the Cure.
Please consider our environment before printing this e-mail or attachments.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------