Hi Vivek,
On Fri, Mar 8, 2019 at 9:09 AM Vivek Aggarwal via FreeIPA-users
wrote:
>
> ok thanks but we're kind of new to DNS zone deployment . Though i will
> search on google but thought of getting any direct pointers from your end
> that how to configure/setup
There is the upstream
On to, 07 maalis 2019, Vivek Aggarwal via FreeIPA-users wrote:
Thanks you Alexander.
Since you represent Redhat team , i couldnt resist myself from asking
below two questions as well . it would be great if you can provide
guidance/suggestion on these too
1) We've a cloud environment , where
Thanks you Alexander.
Since you represent Redhat team , i couldnt resist myself from asking below two
questions as well . it would be great if you can provide guidance/suggestion on
these too
1) We've a cloud environment , where updating resolv.conf file for
accommodating our IDM DNS server
On ma, 04 maalis 2019, Vivek Aggarwal via FreeIPA-users wrote:
Thanks Alexander for such a nice explanation.
I've a follow-up thing to ask , i understood your point that if i'm
using primary domain and realm as "avtar.test" then .stg.avtar.test
and .testing.stg.avtar.test are two DNS zones
On su, 03 maalis 2019, Vivek Aggarwal via FreeIPA-users wrote:
btw, i've created a new machine with following settings , by abandoning the
".local" TLD
Hostname : testing-infra-01-dal1.testing.stg.avtar.test
realm_name: avtar.test
domain_name: avtar.test
But still getting the same error as
btw, i've created a new machine with following settings , by abandoning the
".local" TLD
Hostname : testing-infra-01-dal1.testing.stg.avtar.test
realm_name: avtar.test
domain_name: avtar.test
But still getting the same error as below
+++
ipapython.dnsutil: ERROR
Thanks John , its means a lot of help.
Just out of curiosity , how you're able to search & share the specific RFC so
quickly, is this something i also should also follow in terms of referring RFC
docs to get clarity ?
Is there any RFC's website/links which you can share & will be of help for
Your specific issue might not be because the .local TLD, but .local is a
special ‘reserved’ name for multicast DNS. You can use any other (including
fake) TLD that is not registered.
There are some other TLDs that are ’special’, like the one used for reverse-IP
records in APIPA. Best to avoid
In that case I don’t know how to help (but someone else might). As per
https://tools.ietf.org/html/rfc6762 .local isn’t supposed to be used the way
you are using it at this time, and it will conflict with pretty much any
standard system. I don’t know how to patch/override that without breaking
Yes its inheritance & it was done on purpose to generate TLS certificates as
per hostnames.
Hence kindly suggest how to configure IPA to accommodate this mDNS’s TLD.
___
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe
Did you select mDNS’s TLD .local on purpose? Or was this an inheritance.
> On 3 Mar 2019, at 14:49, Vivek Aggarwal via FreeIPA-users
> wrote:
>
> Our current implementation has multiple dots(.) names in the hostname
> ,details mentioned below & we're using below setting while configuring
11 matches
Mail list logo
