I could be the issue is thus (i have worked around it but its not clean enough for my liking)
i have a service that runs under SSL that is a global service that resolves locally - That is in dc A the IP is different to dc B however the service sits behind the same SSL certs that are non domain specific meaning that if i append a domain then you'll get a certificate mismatch. In all situations apart from kickstart this is fine as a local resolver can sort out the destination of the service based on the search domain, anaconda cant.
It seems a bit annoying i can manually specify a resolver to anaconda but not a search domain - its a non issue now, but an annoyance.
cheers
>
> On Fri, 2013-02-15 at 17:04 +0000, Tom Brown wrote:
>>> Actually, my kickstarts run with the DNS info provided by my DNCP
>>> server. The only thing that I've had to do is copy the
>>> created /etc/resolv.conf file into the newly-built tree so that it's
>>> available to the system for running "post" scripts.
>>
>> thanks for the reply - these are statically assigned kickstarts and DHCP is not involved - you can pass a DNS server to use as dns=1.2.3.4 but there appears to be no search=foo.com etc
>>
>> AFAIK
>
> The real question is how you identify the site-specific information in
> kickstart. Whatever key you use to do that should also be able to
> select a domain name or whatever other particular info needed, and then
> you can implement that in a "pre" script. Maybe something like:
>
> echo "search ${sitedomainname}.org" >> /etc/resolv.conf
>
> where $sitedomainname is the specific domain name for each site.
>
> --
> Ron Loftin reloftin@xxxxxxxxxxxx
>
> "God, root, what is difference ?" Piter from UserFriendly
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
