Hi Charles, Thanks for explanations/questions. Knowing this, i will now see with the network admin to see thoses DNS problems,
Cheers, Francois. On 8/23/07, Charles Bacon <[EMAIL PROTECTED]> wrote: > > Is there an /etc/hosts setup on the server machine? Or is /etc/ > nsswitch.conf setup to use LDAP or NIS first, and those are returning > other results? Is the host multi-homed, or is the "hostname" only > known to the server machine, while everyone else thinks of it as > "otherDNS"? > > It sounds like a little bit of networking setup on the server machine > could take care of the clients who are directly on the server > machine. For all clients, the expected hostname will be done via a > reverse-lookup on the IP address they're connecting to. So it > shouldn't be too hard to get those clients getting the same IP as one > gets from a lookup on the FQDN. > > > Charles > > On Aug 23, 2007, at 4:36 AM, Francois Hornoy wrote: > > > > > > > Hello, > > > > I have a new DNS-related problem. Is there a documentation with > > all the DNS requirements. > > > > I have a server and a client. On both host and container > > certificate. I want to stage file between both machines. > > > > The problem is that, on the server, if i create the certificate > > with the return of "hostname" as the host FQDN, it fails on the > > client side, saying that it's not what it was expected (because > > this FQDN -> IP -> otherDNS). > > > > So i created it with the otherDNS as FQDN, but now it fails on the > > server side, saying that it's expected the "hostname" FQDN, and not > > the otherDNS. > > > > Thus, i'm a bit confused with all this, i would appreciate any > > explanations or pointer to documentation. Maybe the "hostname" of > > the server should be changed? Or maybe there is a way to make > > several host certificates acceptation? > > > > Best regards, > > Francois. > >
