Many A-records

[fih]

I have been receiving a lot of mails regarding this.

This is my comments regarding the ongoing discussion.

Unfortunatley i was not thinking when stating that a NIC should only have
one A-record since a NIC can have subinterfaces. (Sorry folks)

An IP should only have one A-record and services should be pointed out using
Cnames. Of cource if you have choosen to let http be the default service for
a domain you will have to add a A-record for the domain name but this will
be an exception to the rule. (I'm not sure this was ment to be (I could be
totally wrong)).

If webhosting companies uses "virtual name based hosting" they should use
one A-record and many Cnames.
If webhosting companies uses subinterfaces they should have one A-record per
subinterface.

If we have boght a SSL certificate that will protect www.www.com and one of
our customer want's to reach that service using their own DNS namespace
www.customer.com it will not work smooth since the certificate was made for
www.www.com.

Please continue the discussion.

br
fih




"fih" <frhak at hotmail.com> skrev i meddelandet
news:c4og3m$208u$1 at sf1.isc.org...
> Hello guys!
>
> I was once told that a network interface should have only one A-record and
a
> corresponding PTR record. Since you probably know many people likes to
tweak
> this and I'm doing my best to fight it.
>
> While fightning it i also gets alot of questions about why we can't have
> many A-records pointing to the same IP. Does any body know if there is a
RFC
> or Best practise DNS documentation that i can refer to or am I totally
> wrong??
>
> Also if my company likes to sell services based on DNS names and we have
> customers that can't see the external namespace we use for our services.
> They want me to add fake A-records in the customers namespace so our
> services will have different names depending who is asking. This i don't
> like
> at all and i allready know that i will get in trouble with  SSL
> certificates.
> In my world we should instead make our service zone available
> for the customer.
>
> In my world a Network interface should have one but only one A-record.
>
> Comments please!!!
>
>